GNOME Bugzilla – Bug 574262
crash in Evolution Mail: Only start the Evolution...
Last modified: 2009-03-06 03:54:30 UTC
What were you doing when the application crashed? Only start the Evolution-Mail 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: Neu Memory status: size: 103477248 vsize: 103477248 resident: 26034176 share: 18444288 rss: 26034176 rss_rlim: 4294967295 CPU usage: start_time: 1236258295 rtime: 156 utime: 140 stime: 16 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb65976d0 (LWP 4154)] [New Thread 0xb32ecb90 (LWP 4219)] [New Thread 0xb3b11b90 (LWP 4212)] [New Thread 0xb4d4cb90 (LWP 4190)] 0xb7f0b424 in __kernel_vsyscall ()
+ Trace 213186
Thread 1 (Thread 0xb65976d0 (LWP 4154))
----------- .xsession-errors (9 sec old) --------------------- (gnome-settings-daemon:4020): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed <stdin>:130:14: warning: missing terminating ' character Initializing nautilus-open-terminal extension Initializing gnome-mount extension Initializing nautilus-share extension ** (nautilus:4035): WARNING **: Didn't get any signs from mapping-daemon (nautilus:4035): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4154): DEBUG: mailto URL command: evolution %s ** (evolution:4154): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***