GNOME Bugzilla – Bug 491922
crash in Main Menu: Main Menu新建分隔符的下移操作。
Last modified: 2007-11-03 15:27:45 UTC
Version: 0.11.3 What were you doing when the application crashed? Main Menu新建分隔符的下移操作。 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 398782464 vsize: 398782464 resident: 32616448 share: 16351232 rss: 32616448 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193793265 rtime: 217 utime: 197 stime: 20 cutime:20 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/alacarte' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496267088 (LWP 3083)] (no debugging symbols found) 0x00000030b6c0d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 174055
Thread 1 (Thread 46912496267088 (LWP 3083))
----------- .xsession-errors --------------------- (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) (gtk-window-decorator:2727): Wnck-WARNING **: Unhandled action type (nil) "/usr/bin/alacarte": not in executable format: File format not recognized --------------------------------------------------
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. Please update your Fedora installation. *** This bug has been marked as a duplicate of 430074 ***