GNOME Bugzilla – Bug 446269
crash in Evolution Mail: hope this provides more ...
Last modified: 2007-06-11 09:09:32 UTC
What were you doing when the application crashed? hope this provides more information then the last report. Evolution crashes on startup Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-1-686 #1 SMP Sat May 26 16:14:59 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Brushed Icon Theme: OSX Memory status: size: 114937856 vsize: 114937856 resident: 29827072 share: 16920576 rss: 29827072 rss_rlim: 4294967295 CPU usage: start_time: 1181550223 rtime: 221 utime: 194 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233249696 (LWP 9881)] [New Thread -1307575408 (LWP 9910)] [New Thread -1299186800 (LWP 9909)] [New Thread -1284633712 (LWP 9908)] [New Thread -1249981552 (LWP 9900)] [New Thread -1267856496 (LWP 9899)] [New Thread -1293022320 (LWP 9897)] [New Thread -1276245104 (LWP 9895)] [New Thread -1259467888 (LWP 9893)] [New Thread -1241592944 (LWP 9891)] 0xb7736b11 in ?? () from /lib/libpthread.so.0
+ Trace 139977
Thread 8 (Thread -1276245104 (LWP 9895))
----------- .xsession-errors (204 sec old) --------------------- sh: disown: not found sh: disown: not found (synaptic:8988): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:8988): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed The program 'gdesklets-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadGC (invalid GC parameter)'. (Details: serial 144297 error_code 13 request_code 60 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) --------------------------------------------------
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 371529 ***