[SOLVED] segfault with jumanji, surf and xxxterm browsers

[grahameblackwood]

Hi All

Having used these three browsers regularly for many months, three days ago they all failed to start. The only message when trying to start them from xterm is 'segmentation fault' but the messages log shows something on the following lines:

Dec 16 07:42:16 localhost klogd: jumanji[4643]: segfault at 0 ip b6b0a174 sp b335f150 error 4 in libwebkit-1.0.so.2.18.0[b6481000+10f0000]

Other browsers work fine: konqueror, opera, firefox and, oddly, so do jumanji, surf and xxxterm if I use a different login name on my computer and start them from there.

Does anyone else experience this and is there a cure?

Regards

G

[menotu]

I don't use any of the browsers mentioned so unsure what accurate advice I can offer.........but.......

Are there any references in Synaptics History showing info (i.e. Application/Dependency updates ) regarding those browsers?

Are there any "hidden folders" for those browsers listed  under /home/you/ ??

If there are, you could rename those specific folder(s) and log out and back in again, and then try starting one of them.

Actually, I would try renaming just one folder and see how that works, and then try another and so on.

[grahameblackwood]

Thanks for your suggestions Menotu

There is a file ~/.xxxterm.conf but it hasn't changed since March 2012. There are also directories  ~/.surf ~/.xxxterm and ~/.config/jumanji. Removing them and invoking each one in turn from with xterm still results in a segmentation fault. Both surf and xxxterm create the directories again. Re-booting in between hasn't made any difference either.

Whatever happened with these browsers happened on the same day and the only commonality between them seems to be the "error 4" in relation to libwebkit.

Also it seems really curious that I can use these browsers fine under other logins on this computer.

I mainly use E17 but tried the browsers with KDE. However, the result is the same, segmentation fault.

Cheers

G

[grahameblackwood]

Hi All

I loaded Midori from the repo and it segfaults just like surf, jumanji and xxxterm (but, oddly, not for the other user logins on this computer).
Also loaded Arora and it works fine. Not sure if it uses libwebkit though.

Cheers

G

[daniel]

What is the messages of

Code: [Select]

locate webkit?

Make a diff of your files in your home, and of the files from your other users...

[grahameblackwood]

Hi Daniel

Oh, thanks very much. That got it - ie your 'locate webkit' suggestion. It revealed that my user login (but not the other user logins on this computer) has a ~/.local/share/webkit directory and in it there is a directory 'icondatabase' with a file in it named 'WebpageIcons.db' that appeared at the same time that jumanji failed to load (and when the /var/log/messages file showed the 'segfault' report).

Changing the name of the /icondatabase directory to /trash_icondatabase solved this problem and jumanji, surf, xxxterm all work for my user login.

I wonder what ~/.local/share/webkit/icondatabase/WebpageIcons.db is supposed to do and where it came from? It certainly wasn't a help.

Thanks again!

G

[grahameblackwood]

How do I mark this 'SOLVED'?

Cheers

G

OK, found it - modify

g

[grahameblackwood]

Hi All

Just an update.

I checked all the user logins on this computer and they all have '~/.local/share/webkit/icondatabase/WebpageIcons.db' . All I can imagine is that this file became corrupted on my user login, preventing jumanji, surf and xxxterm working. If the file is removed, it is re-created next time the browsers read a website. The browsers I use all work fine now and so does midori.

Without Daniel's suggestion I wouldn't have found the way to a solution in a month of Sundays since I was googling for 'libwebkit' and 'segfault'. The word 'webkit' was definitely beyond my ken, so thanks again Daniel.

Cheers

G

[daniel]

You are welcome, grahameblackwood