GNOME Bugzilla – Bug 515241
crash in Battery Charge Monitor:
Last modified: 2008-02-09 18:40:54 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 23908352 vsize: 23908352 resident: 7344128 share: 6320128 rss: 7344128 rss_rlim: 4294967295 CPU usage: start_time: 1202492368 rtime: 3 utime: 3 stime: 0 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 -1208953120 (LWP 3483)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188555
Thread 1 (Thread -1208953120 (LWP 3483))
----------- .xsession-errors (115 sec old) --------------------- alarm-queue.c:1998 (alarm_queue_add_async) - 0x85aa3d0 alarm-queue.c:585 (load_alarms_for_today) - From Fri Feb 8 17:39:restoring session (gnome-panel:3235): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3235): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3235): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3235): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed --- Hash table keys for warning below: --> file:///home/ruib (nautilus:3513): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --------------------------------------------------
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 446097 ***