GNOME Bugzilla – Bug 508042
crash in Tasks: just started evolution u...
Last modified: 2008-01-10 22:39:04 UTC
Version: 2.10 What were you doing when the application crashed? just started evolution up Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 123047936 vsize: 123047936 resident: 34664448 share: 26427392 rss: 34664448 rss_rlim: 4294967295 CPU usage: start_time: 1199796302 rtime: 106 utime: 94 stime: 12 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209149728 (LWP 32025)] [New Thread -1250956400 (LWP 32063)] [New Thread -1261446256 (LWP 32061)] [New Thread -1240466544 (LWP 32059)] [New Thread -1228489840 (LWP 32049)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184511
Thread 1 (Thread -1209149728 (LWP 32025))
----------- .xsession-errors (7 sec old) --------------------- (evolution:3111): camel-imap-provider-WARNING **: No information for message 587 camel-Message: -- camel-Message: -- camel-Message: -- CalDAV Eplugin starting up ... (evolution:3111): Gdk-CRITICAL **: gdk_window_raise: assertion `GDK_IS_WINDOW (window)' failed restoring draft flag 'text/plain' restoring draft flag 'text/plain' CalDAV Eplugin starting up ... ** (evolution:32025): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:32025): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
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 431459 ***