GNOME Bugzilla – Bug 481784
crash in Workspace Switcher: movin the cube workspace
Last modified: 2007-10-02 19:38:07 UTC
Version: 2.18.0 What were you doing when the application crashed? movin the cube workspace Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 35053568 vsize: 35053568 resident: 8368128 share: 6512640 rss: 8368128 rss_rlim: 4294967295 CPU usage: start_time: 1191244966 rtime: 204 utime: 186 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (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 -1208396064 (LWP 3078)] (no debugging symbols found) 0x00b8f402 in __kernel_vsyscall ()
+ Trace 166548
Thread 1 (Thread -1208396064 (LWP 3078))
----------- .xsession-errors (507 sec old) --------------------- ** WARNING **: dock_set_uposition: current screen size 1280x800 smaller than window position specified in config file, resetting to x=640 y=400 ** WARNING **: dock_set_uposition: current screen size 1280x800 smaller than window position specified in config file, resetting to x=640 y=400 ** WARNING **: dock_set_uposition: current screen size 1280x800 smaller than window position specified in config file, resetting to x=640 y=400 ** WARNING **: dock_set_uposition: current screen size 1280x800 smaller than window position specified in config file, resetting to x=640 y=400 (gnome-panel:3011): 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 we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 420713 ***