GNOME Bugzilla – Bug 424276
crash in Email: quit the application
Last modified: 2007-03-30 21:03:10 UTC
What were you doing when the application crashed? quit the application Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3025.fc7 #1 SMP Wed Mar 28 20:33:47 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299902 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 266010624 vsize: 266010624 resident: 27197440 share: 18665472 rss: 27197440 rss_rlim: 4294967295 CPU usage: start_time: 1175201609 rtime: 570 utime: 465 stime: 105 cutime:2 cstime: 5 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 -1208207648 (LWP 3021)] [New Thread -1316037744 (LWP 3044)] (no debugging symbols found) 0x008e8402 in __kernel_vsyscall ()
+ Trace 123341
Thread 1 (Thread -1208207648 (LWP 3021))
----------- .xsession-errors (14 sec old) --------------------- kdeinit: Got EXT_EXEC 'khelpcenter' from launcher. Could not load library! Trying exec.... DCOP: register 'khelpcenter' -> number of clients is now 3 DCOP: register 'anonymous-3270' -> number of clients is now 4 Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x4a00007 non valido per 0x4a0024d (Question -). Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x4a00007 non valido per 0x4a00329 (Build Sear). DCOP: unregister 'anonymous-3270' kdeinit: PID 3270 terminated. kdeinit: Got EXEC_NEW 'kio_help' from launcher. kdeinit: Got EXEC_NEW 'kio_help' from launcher. DCOP: register 'khc_indexbuilder-3279' -> number of clients is now 4 DCOP: 'khc_indexbuilder-3279' now known as 'khc_indexbuilder' process 3021: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details. Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection. D-Bus not built with -rdynamic so unable to print a backtrace --------------------------------------------------
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 419885 ***