GNOME Bugzilla – Bug 517421
crash in Tasks:
Last modified: 2008-02-19 16:53:09 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 187813888 vsize: 187813888 resident: 61423616 share: 53284864 rss: 61423616 rss_rlim: 4294967295 CPU usage: start_time: 1203420303 rtime: 79 utime: 62 stime: 17 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 -1208387872 (LWP 3797)] [New Thread -1298150512 (LWP 3812)] [New Thread -1255072880 (LWP 3807)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189718
Thread 1 (Thread -1208387872 (LWP 3797))
----------- .xsession-errors --------------------- localuser:MR being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3279 compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. /usr/bin/system-control-network:187: GtkDeprecationWarning: gtk.timeout_remove is deprecated, use gobject.source_remove instead gtk.timeout_remove(self.tag) compiz: pixmap 0x120105c can't be bound to texture compiz: pixmap 0x1201113 can't be bound to texture CalDAV Eplugin starting up ... ** (evolution:3797): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3797): 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 364700 ***