GNOME Bugzilla – Bug 503708
crash in Battery Charge Monitor:
Last modified: 2007-12-17 22:06:05 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 25370624 vsize: 25370624 resident: 10551296 share: 8388608 rss: 10551296 rss_rlim: 4294967295 CPU usage: start_time: 1197019545 rtime: 13 utime: 10 stime: 3 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 -1208826144 (LWP 7999)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 181928
Thread 1 (Thread -1208826144 (LWP 7999))
----------- .xsession-errors (169 sec old) --------------------- Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF --------------------------------------------------
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 ***