GNOME Bugzilla – Bug 514253
crash in Tasks: tog bort brev
Last modified: 2008-02-04 17:26:55 UTC
Version: 2.10 What were you doing when the application crashed? tog bort brev 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-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 120291328 vsize: 120291328 resident: 51744768 share: 30085120 rss: 51744768 rss_rlim: 4294967295 CPU usage: start_time: 1202121505 rtime: 361 utime: 338 stime: 23 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 -1209076000 (LWP 3131)] [New Thread -1264596080 (LWP 3195)] [New Thread -1233126512 (LWP 3154)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188026
Thread 1 (Thread -1209076000 (LWP 3131))
----------- .xsession-errors (62 sec old) --------------------- localuser:sverr being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2798 CalDAV Eplugin starting up ... ** (evolution:3131): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3131): 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 Treating Boolean option HPOption_Tray3 as PickOne Treating Boolean option HPOption_Tray4 as PickOne Treating Boolean option HPOption_Tray5 as PickOne --------------------------------------------------
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 ***