GNOME Bugzilla – Bug 505023
crash in Tasks:
Last modified: 2007-12-22 14:06:31 UTC
Version: 2.10 What were you doing when the application crashed? 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: 115929088 vsize: 115929088 resident: 35692544 share: 29265920 rss: 35692544 rss_rlim: 4294967295 CPU usage: start_time: 1198320240 rtime: 58 utime: 52 stime: 6 cutime:0 cstime: 0 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 -1208596768 (LWP 3345)] [New Thread -1273525360 (LWP 3357)] [New Thread -1220138096 (LWP 3349)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182630
Thread 1 (Thread -1208596768 (LWP 3345))
----------- .xsession-errors --------------------- There seems to be an instance of aMule already running If this is not the case, you may have to remove the file ~/.aMule/muleLock, to allow aMule to run. Attempting to raise current running instance. (amule:3329): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (amule:3329): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (amule:3329): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed CalDAV Eplugin starting up ... ** (evolution:3345): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3345): 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 ***