GNOME Bugzilla – Bug 552337
crash in Evolution Mail and Calendar: entering pw for gnome ke...
Last modified: 2009-01-20 04:00:32 UTC
What were you doing when the application crashed? entering pw for gnome keyring Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (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: Clearlooks Icon Theme: gnome Memory status: size: 100388864 vsize: 100388864 resident: 24494080 share: 17674240 rss: 24494080 rss_rlim: 4294967295 CPU usage: start_time: 1221481390 rtime: 58 utime: 52 stime: 6 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb6624720 (LWP 10509)] [New Thread 0xb4dffb90 (LWP 10624)] [New Thread 0xb45feb90 (LWP 10546)] [New Thread 0xb575fb90 (LWP 10543)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 206791
Thread 1 (Thread 0xb6624720 (LWP 10509))
----------- .xsession-errors (41 sec old) --------------------- closing ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:10509): DEBUG: mailto URL command: evolution %s ** (evolution:10509): DEBUG: mailto URL program: evolution --------------------------------------------------
There are no gnome-keyring or Evolution calls at all in that trace.
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 523463 ***