GNOME Bugzilla – Bug 474687
crash in Tasks:
Last modified: 2007-09-24 17:50:09 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks-DarkNice Icon Theme: Fedora Memory status: size: 113164288 vsize: 113164288 resident: 37687296 share: 31121408 rss: 37687296 rss_rlim: 4294967295 CPU usage: start_time: 1189176515 rtime: 55 utime: 50 stime: 5 cutime:1 cstime: 4 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 -1208547616 (LWP 29208)] [New Thread -1270629488 (LWP 29251)] [New Thread -1223611504 (LWP 29229)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161204
Thread 1 (Thread -1208547616 (LWP 29208))
----------- .xsession-errors (17 sec old) --------------------- compiz (core) - Warn: pixmap 0x1c00894 can't be bound to texture compiz (core) - Info: Couldn't bind redirected window 0x1 to texture compiz (core) - Warn: pixmap 0x1c00894 can't be bound to texture compiz (core) - Info: Couldn't bind redirected window 0x1 to texture compiz (core) - Warn: pixmap 0x1c00894 can't be bound to texture compiz (core) - Info: Couldn't bind redirected window 0x1 to texture CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:29208): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:29208): 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 ***