GNOME Bugzilla – Bug 445550
crash in Tasks: Opening a new message.
Last modified: 2007-07-02 19:17:26 UTC
What were you doing when the application crashed? Opening a new message. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 146411520 vsize: 146411520 resident: 42115072 share: 21504000 rss: 42115072 rss_rlim: 4294967295 CPU usage: start_time: 1181314198 rtime: 2976 utime: 2852 stime: 124 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208662304 (LWP 6484)] [New Thread -1281180784 (LWP 16592)] [New Thread -1291670640 (LWP 16591)] [New Thread -1233839216 (LWP 16458)] [New Thread -1306940528 (LWP 16456)] [New Thread -1236542576 (LWP 6504)] (no debugging symbols found) 0x00c89402 in __kernel_vsyscall ()
+ Trace 139406
Thread 3 (Thread -1291670640 (LWP 16591))
----------- .xsession-errors (4535 sec old) --------------------- (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:8454): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properti ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
I installed the following debug packages and here is the stack trace. evolution-data-server-debuginfo evolution-debuginfo glib-debuginfo gnome-vfs2-debuginfo gtk+-debuginfo gtk2-debuginfo gtkhtml2-debuginfo gtkhtml3-debuginfo libgnome-debuginfo libgnomeui-debuginfo Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 125124608 vsize: 125124608 resident: 42823680 share: 26202112 rss: 42823680 rss_rlim: 4294967295 CPU usage: start_time: 1182976594 rtime: 1626 utime: 1540 stime: 86 cutime:153 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208375584 (LWP 4655)] [New Thread -1317291120 (LWP 5138)] [New Thread -1291138160 (LWP 4917)] [New Thread -1225774192 (LWP 4885)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00bf5402 in __kernel_vsyscall ()
+ Trace 144221
Thread 2 (Thread -1317291120 (LWP 5138))
----------- .xsession-errors --------------------- warning: the debug information found in "/usr/lib/debug//usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so.debug" does not match "/usr/lib/evolution-data-server-1.2/camel-providers/lib warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-publish-calendar.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-publish-cal warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise-features.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-not warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-sa-junk-plugin.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-sa-junk-plugi --------------------------------------------------
Thanks, jfernandez. 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 445309 ***