GNOME Bugzilla – Bug 572375
crash in Evolution Mail and Calendar: dismissing the gnome key...
Last modified: 2009-02-20 03:38:11 UTC
What were you doing when the application crashed? dismissing the gnome keyring password window (clicking on 'deny' Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 103821312 vsize: 103821312 resident: 27119616 share: 17948672 rss: 27119616 rss_rlim: 4294967295 CPU usage: start_time: 1235026642 rtime: 74 utime: 66 stime: 8 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb66646d0 (LWP 8040)] [New Thread 0xb3dfdb90 (LWP 8124)] [New Thread 0xb45feb90 (LWP 8074)] [New Thread 0xb57cdb90 (LWP 8071)] 0xb7fd3424 in __kernel_vsyscall ()
+ Trace 212679
Thread 1 (Thread 0xb66646d0 (LWP 8040))
----------- .xsession-errors --------------------- [FDLProc] canHandle() [FDLProc] canHandle() ***MEMORY-ERROR***: firestarter[7606]: GSlice: assertion failed: sinfo->n_allocated > 0 [FDLProc] canHandle() [FDLProc] canHandle() [FDLProc] canHandle() CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:8040): DEBUG: mailto URL command: evolution %s ** (evolution:8040): DEBUG: mailto URL program: evolution (evolution:8040): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: Access Denied) (evolution:8040): e-data-server-ui-WARNING **: Unable to create password in keyring (Keyring reports: Access Denied) --------------------------------------------------
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 ***