GNOME Bugzilla – Bug 485194
crash in Evolution Mail: opening evolution
Last modified: 2007-10-11 18:21:15 UTC
What were you doing when the application crashed? opening evolution 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: Glossy Icon Theme: SphereCrystal Memory status: size: 474849280 vsize: 474849280 resident: 31580160 share: 19144704 rss: 31580160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191963504 rtime: 84 utime: 70 stime: 14 cutime:1 cstime: 4 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 0x2ad3b3048860 (LWP 5792)] [New Thread 0x44007950 (LWP 5851)] [New Thread 0x43806950 (LWP 5850)] [New Thread 0x41802950 (LWP 5846)] [New Thread 0x43005950 (LWP 5845)] [New Thread 0x42804950 (LWP 5824)] [New Thread 0x42003950 (LWP 5823)] [New Thread 0x41001950 (LWP 5820)] [New Thread 0x40800950 (LWP 5817)] (no debugging symbols found) 0x00002ad3ab13dc7f in waitpid () from /lib/libpthread.so.0
+ Trace 169121
Thread 1 (Thread 0x2ad3b3048860 (LWP 5792))
----------- .xsession-errors (6 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 ***