GNOME Bugzilla – Bug 515586
crash in Tasks:
Last modified: 2008-02-10 19:26:00 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 126738432 vsize: 126738432 resident: 44584960 share: 37036032 rss: 44584960 rss_rlim: 4294967295 CPU usage: start_time: 1202654583 rtime: 159 utime: 149 stime: 10 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 -1208391968 (LWP 3600)] [New Thread -1273664624 (LWP 3714)] [New Thread -1253057648 (LWP 3700)] [New Thread -1242567792 (LWP 3607)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188734
Thread 1 (Thread -1208391968 (LWP 3600))
----------- .xsession-errors (879 sec old) --------------------- alarm-queue.c:585 (load_alarms_for_today) - From Sun Feb 10 15:42:47 2008 to Sun Feb 10 15:42:47 2008 alarm-queue.c:522 (load_alarms) alarm-queue.c:55 (amule:3591): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (amule:3591): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (amule:3591): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed CalDAV Eplugin starting up ... ** (evolution:3600): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3600): 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 ***