GNOME Bugzilla – Bug 559869
crash in Evolution Mail and Calendar:
Last modified: 2008-11-08 13:28:02 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Water Vapor Icon Theme: TuxnTosh Memory status: size: 169463808 vsize: 169463808 resident: 40587264 share: 20074496 rss: 40587264 rss_rlim: 4294967295 CPU usage: start_time: 1226145330 rtime: 530 utime: 489 stime: 41 cutime:3 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb662f6d0 (LWP 5757)] [New Thread 0xaefc3b90 (LWP 6269)] [New Thread 0xb1bffb90 (LWP 5796)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 209459
Thread 1 (Thread 0xb662f6d0 (LWP 5757))
----------- .xsession-errors (13 sec old) --------------------- CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:5757): DEBUG: mailto URL command: evolution %s ** (evolution:5757): DEBUG: mailto URL program: evolution ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/wlan0' ** Message: <info> You are now connected to the wireless network 'MiCassaNet'. ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/wlan0' ** Message: <info> You are now connected to the wireless network 'MiCassaNet'. e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results) e-data-server-ui-Message: Key file does not have group 'Passwords-Mail' --------------------------------------------------
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 338921 ***