GNOME Bugzilla – Bug 506137
crash in Battery Charge Monitor:
Last modified: 2008-01-08 20:16:22 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 25346048 vsize: 25346048 resident: 10428416 share: 8331264 rss: 10428416 rss_rlim: 4294967295 CPU usage: start_time: 1198873889 rtime: 10 utime: 8 stime: 2 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 -1208510752 (LWP 4250)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183377
Thread 1 (Thread -1208510752 (LWP 4250))
----------- .xsession-errors (623 sec old) --------------------- localuser:dscheuer being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3324 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:3451): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3451): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3451): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3451): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed closing closing closing --------------------------------------------------
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 ***