GNOME Bugzilla – Bug 586972
Crash in icon_list_from_theme at gtkwindow.c
Last modified: 2013-10-13 21:29:05 UTC
Version: 2.28.x What were you doing when the application crashed? Had been reading mail in various subfolders. Decided to collapse the folder list by clicking twice on the icon to the left of "On This Computer" Distribution: Slackware Slackware 12.2.0 Gnome Release: 2.27.3 2009-06-16 (GARNOME) BugBuddy Version: 2.27.1 System: Linux 2.6.30 #36 SMP PREEMPT Wed Jun 10 11:08:08 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10699001 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 295395328 vsize: 295395328 resident: 79265792 share: 30269440 rss: 79265792 rss_rlim: 18446744073709551615 CPU usage: start_time: 1245941522 rtime: 11356 utime: 10248 stime: 1108 cutime:70 cstime: 35 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.27/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb6107700 (LWP 15362)] [New Thread 0xb3bceb90 (LWP 15531)] [New Thread 0xb1cffb90 (LWP 15529)] [New Thread 0xac8a5b90 (LWP 15402)] [New Thread 0xb14ffb90 (LWP 15399)] [New Thread 0xafcefb90 (LWP 15398)] [New Thread 0xb04ffb90 (LWP 15393)] [New Thread 0xb0cffb90 (LWP 15392)] [New Thread 0xb4652b90 (LWP 15382)] [New Thread 0xb4e52b90 (LWP 15380)] 0xb6fdc171 in waitpid () from /lib/libpthread.so.0
+ Trace 216187
Thread 1 (Thread 0xb6107700 (LWP 15362))
---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_notify: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed ** Gtk **: gtk_widget_get_screen: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed ** Gtk **: gtk_icon_theme_get_icon_sizes: assertion `GTK_IS_ICON_THEME (icon_theme)' failed ----------- .xsession-errors (366145662 sec old) --------------------- iceauth: creating new authority file /home/ronis/.ICEauthority --------------------------------------------------
looks like gtk+ bug
Akhil has right, this looks like a gtk+ thing. Just before moving to them, could you write here your gtk+ nd glib version you compile, and try to catch where does the first GLib or Gtk+ console warning comes from, please? You can do that for example by these steps: 1) close evolution or get the PID of a running one 2) either: gdb evolution --ex "b g_logv" --ex r or: gdb -pid=PID --ex "b g_logv" --ex c 3) when gdb will stop (and it will stop on any warnings printed to the console through this function, thus take care of it) then just invoke gdb command "bt" (I guess the backtrace for an active thread should be enough to see where it happened) and paste the result here. Thanks in advance.
Unfortunately, I don't know what versions I had when the bug arose. For what it's worth, I'm currently running glib-2.21.3 and gtk+-2.17.2, although I had been using gtk+2.17.[34] until a gnumeric cell formatting issue forced me to revert. In general, I'm within 1 day of a release of gtk/glib, so that probably meant that I was running glib-2.21.2 and gtk+-2.17.2. Following Milan's suggestion I attached gdb and set the breakpoint. Here's what I see: Breakpoint 1, IA__g_logv (log_domain=0xb5a6fc55 "libexchangemapi", log_level=G_LOG_LEVEL_MESSAGE, format=0xb5a711a9 "%s: %s: lock(connect_lock)", args1=0xafcff0fc "Ø\002§µ`\032§µ\v") at gmessages.c:396 396 gboolean was_fatal = (log_level & G_LOG_FLAG_FATAL) != 0; (gdb) bt
+ Trace 216463
and so on
oh, these come from libexchangemapi, see > IA__g_logv (log_domain=0xb5a6fc55 "libexchangemapi", try those with log_domain either GLib-anything or Gtk. Pity the libexchangemapi is so chatty here.
*** Bug 592460 has been marked as a duplicate of this bug. ***
*** Bug 597810 has been marked as a duplicate of this bug. ***
*** Bug 597916 has been marked as a duplicate of this bug. ***
*** Bug 599040 has been marked as a duplicate of this bug. ***
*** Bug 599328 has been marked as a duplicate of this bug. ***
*** Bug 599626 has been marked as a duplicate of this bug. ***
*** Bug 600108 has been marked as a duplicate of this bug. ***
*** Bug 600677 has been marked as a duplicate of this bug. ***
*** Bug 601690 has been marked as a duplicate of this bug. ***
*** Bug 602115 has been marked as a duplicate of this bug. ***
*** Bug 602290 has been marked as a duplicate of this bug. ***
*** Bug 602722 has been marked as a duplicate of this bug. ***
*** Bug 602849 has been marked as a duplicate of this bug. ***
mapi bug.
*** Bug 603603 has been marked as a duplicate of this bug. ***
*** Bug 604121 has been marked as a duplicate of this bug. ***
(In reply to comment #18) > mapi bug. Why do you think that?
*** Bug 606270 has been marked as a duplicate of this bug. ***
*** Bug 606952 has been marked as a duplicate of this bug. ***
*** Bug 607528 has been marked as a duplicate of this bug. ***
*** Bug 611878 has been marked as a duplicate of this bug. ***
*** Bug 612252 has been marked as a duplicate of this bug. ***
*** Bug 613314 has been marked as a duplicate of this bug. ***
*** Bug 618808 has been marked as a duplicate of this bug. ***
*** Bug 619646 has been marked as a duplicate of this bug. ***
I do not believe it's MAPI related, as for example stack trace in bug #619646 has no MAPI thread at all. Thus I'm moving this back to evolution (maybe should be in gtk?).
*** Bug 621555 has been marked as a duplicate of this bug. ***
Of the duplicate stack traces I've looked at I don't see any Evolution calls at all, so I'm forced to call this a GTK+ bug. Bug #599040 has a good trace with GTK+ debug symbols: trace #218451 Hopefully this has already been fixed.
(In reply to comment #32) > Bug #599040 has a good trace with GTK+ debug symbols: trace #218451 *sigh* Expected the trace reference to linkify. It's here: https://bugzilla.gnome.org/page.cgi?id=trace.html&trace_id=218451
Going by the huge number of duplicate bug reports then nothing for three years looks like this got fixed a while ago. Closing bug.