GNOME Bugzilla – Bug 467562
crash in System Log:
Last modified: 2007-08-17 12:41:55 UTC
Version: 2.18.1 What were you doing when the application crashed? 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 37715968 vsize: 37715968 resident: 19902464 share: 15532032 rss: 19902464 rss_rlim: 4294967295 CPU usage: start_time: 1187328033 rtime: 178 utime: 165 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208797472 (LWP 3185)] (no debugging symbols found) 0x0035f402 in __kernel_vsyscall ()
+ Trace 155844
Thread 1 (Thread -1208797472 (LWP 3185))
----------- .xsession-errors (4024 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/symbiote.dezzas-place.com:/tmp/.ICE-unix/2947 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:3068): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3068): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3068): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:3068): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed --------------------------------------------------
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 451179 ***