GNOME Bugzilla – Bug 504581
crash in Power Manager: nothing I just woke the ...
Last modified: 2008-02-10 19:56:15 UTC
What were you doing when the application crashed? nothing I just woke the box up from a screen saver Distribution: Unknown Gnome Release: 2.20.1 2007-12-09 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 6.2-RELEASE-p9 FreeBSD 6.2-RELEASE-p9 #0: Thu Nov 29 04:07:33 UTC 2007 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Inverted Icon Theme: Tango-Blue-Materia Memory status: size: 32124 vsize: 32124 resident: 17720 share: 31398332 rss: 17720 rss_rlim: 4430 CPU usage: start_time: 0 rtime: 133 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/gnome-power-manager' (no debugging symbols found)...[New LWP 100091] [Switching to LWP 100091] 0x2908f6cd in wait4 () from /lib/libc.so.6
+ Trace 182393
Thread 1 (LWP 100091)
Output of custom script "gnome-power-bugreport.sh": Distro version: Kernel version: 6.2-RELEASE-p9 g-p-m version: 2.20.0 HAL version: 0.5.8 System manufacturer: missing System version: missing System product: missing AC adapter present: no Battery present: no Laptop panel present: no CPU scaling present: no Battery Information: GNOME Power Manager Process Information: HAL Process Information: ----------- .xsession-errors (1178 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 420419 ***