GNOME Bugzilla – Bug 628216
libgtk 2.21.6 random segfault with many gdk functions
Last modified: 2010-09-15 12:53:59 UTC
Since the move to libgtk 2.21.6 in ubuntu maverick, some applications like nautilus tend to crash segfault randomly. gdb show the segfaults happen on many gdk functions. Here are two differents backtraces for a same segfault happening in differents conditions. http://pastebin.com/pue90cRC http://pastebin.com/SjVsJN90 There are other segfaults that concern some other gdk functions but they are hard to reproduce because of the previous one. Downgrading to libgtk 2.21.5 solve theses segfault. The strange thing is that if you previously compiled nautilus with libgtk 2.21.5 even if you update libgtk-2.0 to 2.21.6 then the problem is solved. Maybe this come from some missing headers in 2.21.6. I don't have any clue but this is what i've observed and what the backtraces tend to say. This bug may concern some other gtk apps than nautilus, some apps using advanced drawing gdk functions. It's a critical bug because nautilus is barely usable and even to get a window you have to pray for it to avoid the random crash at launch and after. Just change a theme and nautilus crash / restart. It happens very very often.
This is the first backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff57aa036 in IA__gdk_gc_set_rgb_fg_color (gc=0xffffffffe4154160, color=0x7fffffffab00) at /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c:1328 1328 /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c: Aucun fichier ou dossier de ce type. in /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c (gdb) bt
+ Trace 223459
This is the second one: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff57aa036 in IA__gdk_gc_set_rgb_fg_color (gc=0xffffffffe4009330, color=0x7fffffffcef0) at /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c:1328 1328 /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c: Aucun fichier ou dossier de ce type. in /build/buildd/gtk+2.0-2.21.6/gdk/gdkgc.c (gdb) bt
+ Trace 223461
same applies for 2.21.7 Still unconfirmed ? it's really not hard to confirm this bug just launch nautilus a few time and you ve got this bug confirmed.
seems fixed with vanilla nautilus 2.31.92. Maybe some compil DEPRECATED flags changed. or maybe something else.