GNOME Bugzilla – Bug 431448
crash in Main Menu: selecting menu items (sy...
Last modified: 2007-04-20 00:53:22 UTC
Version: 0.11.3 What were you doing when the application crashed? selecting menu items (system > Admin > User and Groups) Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3088.fc7 #1 SMP Wed Apr 18 15:12:44 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 69693440 vsize: 69693440 resident: 30998528 share: 15560704 rss: 30998528 rss_rlim: 4294967295 CPU usage: start_time: 1177011002 rtime: 5129 utime: 4631 stime: 498 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/alacarte' (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 -1208092992 (LWP 2922)] (no debugging symbols found) 0x00238402 in __kernel_vsyscall ()
+ Trace 129097
Thread 1 (Thread -1208092992 (LWP 2922))
----------- .xsession-errors --------------------- Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 error getting update info: Cannot find a valid baseurl for repo: extras-development ** (gnome-panel:2785): WARNING **: Error loading menu layout from "/home/user/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace ** (gnome-panel:2785): WARNING **: Error loading menu layout from "/home/user/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3400003 (Main Menu); these messages lack timestamps and therefore suck. "/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 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 430074 ***