GNOME Bugzilla – Bug 492405
crash in Battery Charge Monitor: sleeping
Last modified: 2007-11-17 13:21:57 UTC
What were you doing when the application crashed? sleeping Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 36495360 vsize: 36495360 resident: 15388672 share: 13561856 rss: 15388672 rss_rlim: 4294967295 CPU usage: start_time: 1193427077 rtime: 424 utime: 351 stime: 73 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/battstat-applet-2' (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 -1208251872 (LWP 3156)] (no debugging symbols found) 0x0086a402 in __kernel_vsyscall ()
+ Trace 174390
Thread 1 (Thread -1208251872 (LWP 3156))
----------- .xsession-errors (103746 sec old) --------------------- -V, --version Print gnash's version number and exit keys: CTRL-Q, CTRL-W, ESC Quit/Exit CTRL-P Toggle Pause CTRL-R Restart the movie CTRL-[ or kp- Step back one frame CTRL-] or kp+ Step forward one frame CTRL-B Toggle background color Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446097 ***