GNOME Bugzilla – Bug 414871
crash in Power Manager: Launching "power statist...
Last modified: 2007-03-05 11:39:27 UTC
What were you doing when the application crashed? Launching "power statistics" from the "system tools" menu. I just compiled GNOME with Garnome under Ubuntu Edgy. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.17.92 2007-03-04 (GARNOME) BugBuddy Version: 2.17.4 System: Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 21049344 vsize: 21049344 resident: 7172096 share: 5259264 rss: 7172096 rss_rlim: 4294967295 CPU usage: start_time: 1173093330 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/ubun/garnome/bin/gnome-power-manager' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225746768 (LWP 11811)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 115979
Thread 1 (Thread -1225746768 (LWP 11811))
----------- .xsession-errors (738 sec old) --------------------- Adding file /media/hde8/EMULEtemp/020.part.met to shares Shutting down aMule... aMule dialog destroyed Now, exiting main app... aMule OnExit: Terminating core. Saving PartFile 1 of 37 Saving PartFile 2 of 37 Saving PartFile 3 of 37 Saving PartFile 4 of 37 Saving PartFile 5 of 37 Saving PartFile 6 of 37 Saving PartFile 7 of 37 Saving PartFile 8 of 37 Saving All PartFiles Saved. aMule shutdown completed. ** (gnome-session:9857): WARNING **: Couldn't connect to PowerManager Process /usr/bin/gnome-power-manager exited with status 1 ** (gnome-session:9857): WARNING **: Couldn't connect to PowerManager Process /usr/bin/gnome-power-manager exited with status 1 Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! [DEBUG]: All done. Ciao! --------------------------------------------------
*** This bug has been marked as a duplicate of 412345 ***