GNOME Bugzilla – Bug 591606
Everything whick is linked against libgio-2.0 cores dump
Last modified: 2009-12-04 03:32:33 UTC
Steps to reproduce: Since in Ubuntu launchpad no solution or any attention has been given to this bug, my last chance to this issue being resolved is posting here. Here is the bug report: https://bugs.launchpad.net/ubuntu/+bug/402693 Recently I've updated to latest kernel 2.6.28-14-generic i686 in my Jaunty Jackalope 9.04 32-bit system. I use kde4 4.3 RC and in the latest days I've been suffering of massive core dumping due to 'segmentation fault' my applications that depend on Gnome libs. My thunderbird can't even save an attachment, it just cores dump I've tried gedit from console, it cores dump even before starting! Here is the backtrace of gdb on gedit behavior: [CODE] (gdb) bt
+ Trace 216904
Take a look at this: "\230Q�\b\002" What I really need to trace this really really really anoying bug is to find the damn file (or gconf entry) where indicates to the gnome file browser extension the latest directory saved... The fact is that whenever I enteer my use home dir, it crashes. That's the real reason why firefox,thunderbird,gedit,etc crashes. But in some apps that lucky has another directory saved as default place works just fine (ex. shutter has latest dir to /tmp). Also another interesting point is that java's file browser extension works ok on my users home dir. What an anooying bug! Please help! Thanks anyway for any help. I really want to help you fix this bug. Raine Stack trace: Other information:
Same behaviour here, with Jaunty 9.04, kernel 2.6.28-15 server and Kde 4.3. Gtk apps crash with segfault when trying to save and browse among folders. Gedit won't even start. All of them works with gksudo or switching to su. The problem could be related to an un-completed upgrade of the gtk libraries... maybe two or more versions mixed. Someone thinks of a a forced dist-upgrade. I'd try to go back, but I don't know how...
If you look at the trace I've posted in first comment, you'll see that the content of filename is quite unfortunate. Since this could be causing the bug itself it would be interesting that gnome dev could help me here to track where the file browser is loading _by_default_ this value. I could edit the config file responsible to load this default value and edit it to workaround this bug. In fact if I find this default config file that preloads this value it would be easy to reproduce this bug. Please dev team help me here to find this config value or gnome register input that preloads this filename! I'm still suffering from this nasty bug and it's quite annoying since I have to use opera's file browser to attach things on my emails, instead using thunderbird. Please help here! Raine
Created attachment 141684 [details] compressed tar.gz containing needed files Contains: mime.cache and strace dump
At least, I've found it! I'll describe how to reproduce it on my Ubuntu 9.04 32-bit (fully updated to latest version). The problem is in the file '$HOME/.local/share/mime/mime.cache' (I think it's corrupted. I've attached above this post a strace dump file and a corrupted mime.cache file as a tar.gz directory). Steps to reproduce it: 1) Backup your '.local/' dir $ mv $HOME/.local/ $HOME/.local_bkp/ 2) Create a NEW '.local/' dir $ mkdir $HOME/.local/; mkdir $HOME/.local/share; mkdir $HOME/.local/share/mime/ 3) Copy corrupted 'mime.cache' attached in this post to the NEW dir. $ cp bug_591606/mime.cache $HOME/.local/share/mime/ 4) Launch program linked against libgio (i.e. nautilus) $ nautilus 5) Enjoy your Segmentation Fault ;) Steps to workaround: 1) Move '$HOME/.local/share/mime/mime.cache' file to a temporary dir just to backup it $ mv $HOME/.local/share/mime/mime.cache $HOME/<temporary_dir> 2) Launch nautilus to test it $ nautilus That's all folks! PD: Anyway, can anybody confirm this bug? Please! Raine
Yes, it works! Now, we should understand how the bug came out...:)
Now the next step is that gnome people or even Ubuntu CONFIRMS this bug. But I don't know if they are still on holidays, but no one answered yet :_( Raine
Raine: thanks for all the detective work. I can confirm this bug on Jaunty 32bit. I can also confirm that it's not a problem on Karmic 64bit. I'll look into this deeper. Sorry for the delay.
I also verified that the bug is gone on my friend's Karmic 32bit laptop. Can you please upgrade to Karmic and let me know if this is still a problem for you? cheers.
Hi! I have now installed a fresh new Karmic 64-bit. And didn't have any problem related to this bug so far in a fresh installation. Also tested the attached 'mime.cache' file in my Karmic 64-bit and no problem at all! I think thius bug can be closed ;) Thanks for the support! Regards, Raine
cheers