GNOME Bugzilla – Bug 409960
crash in Keyboard: I started it from the me...
Last modified: 2007-02-20 17:21:04 UTC
Version: 2.17.91 What were you doing when the application crashed? I started it from the menu Distribution: Frugalware 0.6rc1 (Terminus) Gnome Release: 2.17.91 2007-02-17 (Frugalware) BugBuddy Version: 2.17.3 System: Linux 2.6.20-fw1 #1 SMP PREEMPT Mon Feb 5 01:42:52 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled Memory status: size: 37093376 vsize: 0 resident: 37093376 share: 0 rss: 21999616 rss_rlim: 0 CPU usage: start_time: 1171967291 rtime: 0 utime: 16 stime: 0 cutime:14 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (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 -1239562512 (LWP 16288)] (no debugging symbols found) 0xb7f28410 in __kernel_vsyscall ()
+ Trace 112267
Thread 1 (Thread -1239562512 (LWP 16288))
----------- .xsession-errors (4197 sec old) --------------------- (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (gnome-panel:3431): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Here's the debug trace (I've omitted the xsession-errors section as it contains nothing relevant, only messages from a banshee plugin): Distribution: Frugalware 0.6rc1 (Terminus) Gnome Release: 2.17.91 2007-02-17 (Frugalware) BugBuddy Version: 2.17.3 System: Linux 2.6.20-fw1 #1 SMP PREEMPT Mon Feb 5 01:42:52 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled Memory status: size: 37089280 vsize: 0 resident: 37089280 share: 0 rss: 21999616 rss_rlim: 0 CPU usage: start_time: 1171991471 rtime: 0 utime: 17 stime: 0 cutime:15 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239197968 (LWP 5435)] 0xb7f81410 in __kernel_vsyscall ()
+ Trace 112352
Thread 1 (Thread -1239197968 (LWP 5435))
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 398631 ***