GNOME Bugzilla – Bug 574997
crash in Evolution Mail and Calendar:
Last modified: 2009-03-12 08:21:05 UTC
What were you doing when the application crashed? 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 Mon Dec 15 18:15:07 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: SphereCrystal Memory status: size: 101244928 vsize: 101244928 resident: 41025536 share: 20393984 rss: 41025536 rss_rlim: 4294967295 CPU usage: start_time: 1236804291 rtime: 410 utime: 373 stime: 37 cutime:2 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 0xb65fe6d0 (LWP 20859)] [New Thread 0xb31c3b90 (LWP 20983)] [New Thread 0xb4afeb90 (LWP 20976)] [New Thread 0xb52ffb90 (LWP 20889)] 0xb7f6c424 in __kernel_vsyscall ()
+ Trace 213391
Thread 2 (Thread 0xb31c3b90 (LWP 20983))
----------- .xsession-errors (23 sec old) --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (firefox-bin:19580): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution:14183): e-utils-WARNING **: Lock destroy: failed to unlink file '/home/mikkel/.evolution/.running'! (firefox-bin:19580): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:20859): DEBUG: mailto URL command: evolution %s ** (evolution:20859): DEBUG: mailto URL program: evolution (evolution:20859): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3 BBDB spinning up... --------------------------------------------------
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 ***