GNOME Bugzilla – Bug 492542
crash in Tasks: starting app
Last modified: 2007-11-02 02:40:12 UTC
Version: 2.10 What were you doing when the application crashed? starting app 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: 131883008 vsize: 131883008 resident: 39309312 share: 30662656 rss: 39309312 rss_rlim: 4294967295 CPU usage: start_time: 1193965399 rtime: 169 utime: 154 stime: 15 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 -1208727840 (LWP 22626)] [New Thread -1238369392 (LWP 22632)] [New Thread -1226183792 (LWP 22629)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174490
Thread 1 (Thread -1208727840 (LWP 22626))
----------- .xsession-errors (13 sec old) --------------------- (l)user is reading mail (l)user is reading mail (l)user is reading mail (l)user is reading mail Init sylpheed-claws plugin Init gaim plugin Init thunderbird plugin Init evolution plugin closing closing CalDAV Eplugin starting up ... ** (evolution:22626): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:22626): 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 ***