GNOME Bugzilla – Bug 419215
crash in Power Manager: updating from the on lin...
Last modified: 2007-03-20 21:15:41 UTC
What were you doing when the application crashed? updating from the on line update tool. If it is any help the file system is reiserfs. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.18.0 2007-03-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:37:35 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 86433792 vsize: 86433792 resident: 7483392 share: 6455296 rss: 7483392 rss_rlim: 4294967295 CPU usage: start_time: 1174093366 rtime: 82 utime: 45 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) 0x00e4a402 in _start () from /lib/ld-linux.so.2
+ Trace 119312
----------- .xsession-errors (6247 sec old) --------------------- GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized ** (gnome-system-monitor:4127): WARNING **: SELinux was found but is not enabled. GTK Accessibility Module initialized ** (gnome-system-monitor:4167): WARNING **: SELinux was found but is not enabled. GTK Accessibility Module initialized ** (gnome-system-monitor:4183): WARNING **: SELinux was found but is not enabled. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** This bug has been marked as a duplicate of 420419 ***