GNOME Bugzilla – Bug 485574
crash in Evolution: Just executed Send/Recei...
Last modified: 2007-10-11 18:21:49 UTC
What were you doing when the application crashed? Just executed Send/Receive Mail Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 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: 466407424 vsize: 466407424 resident: 33054720 share: 18632704 rss: 33054720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192064323 rtime: 134 utime: 119 stime: 15 cutime:1 cstime: 4 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 0x2b17c16aa860 (LWP 5111)] [New Thread 0x42804950 (LWP 5163)] [New Thread 0x42003950 (LWP 5162)] [New Thread 0x41802950 (LWP 5157)] [New Thread 0x41001950 (LWP 5137)] [New Thread 0x40800950 (LWP 5136)] (no debugging symbols found) 0x00002b17b979fc7f in waitpid () from /lib/libpthread.so.0
+ Trace 169380
Thread 1 (Thread 0x2b17c16aa860 (LWP 5111))
----------- .xsession-errors (29 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 --------------------------------------------------
This only happens on Evolution use after initial boot. subsequent running of Evolution does not exhibit this error.. FYI..
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 ***