GNOME Bugzilla – Bug 532138
Evolution crashed : clicked on attachment button during memo creation
Last modified: 2009-08-28 05:37:12 UTC
Evolution 2.22.1 Distribution: openSUSE 11.0 (i586) Beta1 Gnome Release: 2.22.1 2008-04-14 (SUSE) BugBuddy Version: 2.22.0 System: Linux 2.6.25-rc9-17-pae #1 SMP 2008-04-15 22:54:53 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Industrial Memory status: size: 130199552 vsize: 130199552 resident: 10420224 share: 20983808 rss: 31404032 rss_rlim: 1791457280 CPU usage: start_time: 1210242729 rtime: 346 utime: 314 stime: 32 cutime:2 cstime: 28 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb643a720 (LWP 10460)] [New Thread 0xb136bb90 (LWP 10766)] [New Thread 0xb1d45b90 (LWP 10765)] [New Thread 0xb2587b90 (LWP 10472)] 0xffffe430 in __kernel_vsyscall ()
+ Trace 197211
Thread 3 (Thread 0xb1d45b90 (LWP 10765))
----------- .xsession-errors (5321 sec old) --------------------- (gnome-screenshot:32254): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed (gnome-screenshot:32254): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed (gnome-screenshot:2242): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names' (gnome-screenshot:2242): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed (gnome-screenshot:2242): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed (gedit:8907): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names' (gedit:8907): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed (gedit:8907): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed --------------------------------------------------
Could be related to bug #537555 I guess.
*** This bug has been marked as a duplicate of bug 537555 ***