GNOME Bugzilla – Bug 413927
crash in Power Statistics: haldaemon didn't start o...
Last modified: 2007-03-04 12:11:56 UTC
What were you doing when the application crashed? haldaemon didn't start on bootup; I did a "service haldaemon start", then ran gnome-power-manager. Then tried to run power history. It ran OK for about a minute, not logging any data, then crashed. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc) BugBuddy Version: 2.17.3 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: Enforcing Accessibility: Enabled Memory status: size: 51535872 vsize: 0 resident: 51535872 share: 0 rss: 12840960 rss_rlim: 0 CPU usage: start_time: 1172857213 rtime: 0 utime: 111 stime: 0 cutime:95 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-power-statistics' (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 -1208473888 (LWP 3075)] (no debugging symbols found) 0x00592402 in __kernel_vsyscall ()
+ Trace 115245
Thread 1 (Thread -1208473888 (LWP 3075))
----------- .xsession-errors --------------------- Failed to read private dictionary. This problem might be a problem of Anthy. GTK Accessibility Module initialized Bonobo accessibility support initialized Saving to syslog: Could not connect to GNOME Power Manager. Perhaps the program is not running or you are using an old version?Bonobo accessibility support initialized GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
*** Bug 414066 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 412345 ***