GNOME Bugzilla – Bug 439473
crash in Anjuta IDE: opening font selection d...
Last modified: 2009-08-15 18:40:50 UTC
Version: 2.1.3 What were you doing when the application crashed? opening font selection dialog from preferences->gtkSourceView Distribution: SUSE LINUX 10.1 (i586) Gnome Release: 2.18.1 2007-05-17 (JHBuild) BugBuddy Version: 2.18.1 System: Linux 2.6.16.13-4-smp #1 SMP Wed May 3 04:53:23 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Industrial Memory status: size: 361078784 vsize: 361078784 resident: 112488448 share: 101232640 rss: 112488448 rss_rlim: 4294967295 CPU usage: start_time: 1179508593 rtime: 241 utime: 205 stime: 36 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/k0543388/gnome2/bin/anjuta' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227094352 (LWP 32669)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 134842
Thread 1 (Thread -1227094352 (LWP 32669))
----------- .xsession-errors (135 sec old) --------------------- (gnome-ui-properties:32668): Gtk-WARNING **: Icon cache '/opt/kde3/share/icons/suseadds/icon-theme.cache' is invalid bad string content (gnome-ui-properties:32668): Gtk-WARNING **: Icon cache '/opt/kde3/share/icons/suseadds/icon-theme.cache' is invalid bad string content (gnome-ui-properties:32668): Gtk-WARNING **: Icon cache '/opt/kde3/share/icons/suseadds/icon-theme.cache' is invalid bad string content (gnome-ui-properties:32668): Gtk-WARNING **: Icon cache '/opt/kde3/share/icons/suseadds/icon-theme.cache' is invalid --------------------------------------------------
Thanks for your report! It is a bit weird because I can't see anything wrong for the trace in anjuta's code. The crash happens deep in Gtk+! Have you tried if the fontselection dialog works correctly in gedit? Thanks!
The font selection dialog in gedit works fine. The problem is, it was a custom build of gnome 2.18, and I may have screwed up something, somewhere, especially given that half of it was built inside opensuse's poluted environment, while another half was built after RTFM'ing on how to clean it! Do you think this may have caused the problem? I may recompile everything from scratch....
Yes, this could have caused the problem. In fact, we use a GtkFontChooserButton meaning that the whole font selection dialog is entirely handled by GTK+. Of course it's possible that we screwed up memory but I doubt that. Would be great if you could test with a clean build and/or use packages from opensuse (should be available for 2.18). Thanks!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 431255 ***
Corrected version
Closing all old bugs. Apologies for the spam.