GNOME Bugzilla – Bug 484387
crash in Evolution:
Last modified: 2007-10-07 18:50:33 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 466112512 vsize: 466112512 resident: 32698368 share: 18628608 rss: 32698368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191759328 rtime: 110 utime: 93 stime: 17 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (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 0x2adbac1b7860 (LWP 5059)] [New Thread 0x42804950 (LWP 5112)] [New Thread 0x42003950 (LWP 5111)] [New Thread 0x41802950 (LWP 5107)] [New Thread 0x41001950 (LWP 5087)] [New Thread 0x40800950 (LWP 5086)] (no debugging symbols found) 0x00002adba42acc7f in waitpid () from /lib/libpthread.so.0
+ Trace 168525
Thread 1 (Thread 0x2adbac1b7860 (LWP 5059))
----------- .xsession-errors (34 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 evolution-shell-Message: Killing old version of evolution-data-server... libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***