GNOME Bugzilla – Bug 518108
crash in Tasks: Didn't even notice an ap...
Last modified: 2008-02-23 13:15:30 UTC
Version: 2.10 What were you doing when the application crashed? Didn't even notice an app had 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: Clearlooks Icon Theme: Fedora Memory status: size: 114692096 vsize: 114692096 resident: 34598912 share: 28377088 rss: 34598912 rss_rlim: 4294967295 CPU usage: start_time: 1203704925 rtime: 49 utime: 40 stime: 9 cutime:0 cstime: 2 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 -1209137440 (LWP 3347)] [New Thread -1242567792 (LWP 3371)] [New Thread -1219990640 (LWP 3368)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190122
Thread 1 (Thread -1209137440 (LWP 3347))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3150 Error: permissions error in pam_timestamp_check ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name CalDAV Eplugin starting up ... ** (evolution:3347): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3347): 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 ***