GNOME Bugzilla – Bug 453887
crash in Tasks: lkfbh
Last modified: 2007-07-11 18:40:02 UTC
What were you doing when the application crashed? lkfbh Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 92508160 vsize: 92508160 resident: 22286336 share: 13918208 rss: 22286336 rss_rlim: 4294967295 CPU usage: start_time: 1183621040 rtime: 165 utime: 137 stime: 28 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 -1208592672 (LWP 4643)] (no debugging symbols found) 0x00865402 in __kernel_vsyscall ()
+ Trace 145845
Thread 1 (Thread -1208592672 (LWP 4643))
----------- .xsession-errors (9613 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost:/tmp/.ICE-unix/2602 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory Loading "installonlyn" plugin --- Hash table keys for warning below: --> file:///root (nautilus:2891): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --------------------------------------------------
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 425129 ***