GNOME Bugzilla – Bug 410564
crash in Power Management: ran power management app...
Last modified: 2007-03-20 21:21:30 UTC
What were you doing when the application crashed? ran power management application. it crashed immediately. Distribution: Fedora release 6.90 (Rawhide) Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc) BugBuddy Version: 2.17.3 System: Linux 2.6.20-1.2936.fc7 #1 SMP Tue Feb 20 18:43:55 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled Memory status: size: 40144896 vsize: 0 resident: 40144896 share: 0 rss: 13930496 rss_rlim: 0 CPU usage: start_time: 1172096315 rtime: 0 utime: 183 stime: 0 cutime:104 cstime: 0 timeout: 79 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-power-preferences' (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 -1208133920 (LWP 4794)] (no debugging symbols found) 0x00a73402 in __kernel_vsyscall ()
+ Trace 112707
Thread 1 (Thread -1208133920 (LWP 4794))
----------- .xsession-errors (10 sec old) --------------------- GTK Accessibility Module initialized Bonobo accessibility support initialized Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5400003 specified for 0x5400304 (Keep Resol). GTK Accessibility Module initialized Bonobo accessibility support initialized Saving to syslog: Either HAL or DBUS are not working!Saving to syslog: HAL does not support power management!GTK Accessibility Module initialized GTK Accessibility Module initialized ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** ERROR **: file dbus-gproxy.c: line 658 (unassociate_proxies): assertion failed: (priv->associated) aborting... GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? 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 ***