GNOME Bugzilla – Bug 415563
crash in Power Manager: Resuming from power save...
Last modified: 2007-03-20 21:19:29 UTC
What were you doing when the application crashed? Resuming from power save mode for the monitor. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 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: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 52121600 vsize: 52121600 resident: 10502144 share: 7159808 rss: 10502144 rss_rlim: 4294967295 CPU usage: start_time: 1173234617 rtime: 108 utime: 8 stime: 100 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) 0x0060e402 in _start () from /lib/ld-linux.so.2
+ Trace 116499
----------- .xsession-errors (1442 sec old) --------------------- (gnome-terminal:2871): Vte-WARNING **: Can not find appropiate font for character U+ac00. (gnome-terminal:2871): Vte-WARNING **: Can not find appropiate font for character U+ac01. (gnome-terminal:2871): Vte-WARNING **: Can not find appropiate font for character U+ac04. (gnome-terminal:2871): Vte-WARNING **: Can not find appropiate font for character U+ac08. (gnome-terminal:2871): Vte-WARNING **: Can not find appropiate font for character U+ac10. --------------------------------------------------
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 ***