GNOME Bugzilla – Bug 497798
crash in Tasks:
Last modified: 2007-11-18 13:26:27 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 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: 140226560 vsize: 140226560 resident: 39272448 share: 32628736 rss: 39272448 rss_rlim: 4294967295 CPU usage: start_time: 1195359051 rtime: 100 utime: 91 stime: 9 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 -1208891680 (LWP 30034)] [New Thread -1299186800 (LWP 30086)] [New Thread -1242395760 (LWP 30076)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178444
Thread 1 (Thread -1208891680 (LWP 30034))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". CalDAV Eplugin starting up ... Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ** (evolution:30034): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:30034): 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 Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
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 ***