GNOME Bugzilla – Bug 443535
crash in Main Menu: réglage main menu
Last modified: 2007-06-03 13:29:17 UTC
Version: 0.11.3 What were you doing when the application crashed? réglage 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 47370240 vsize: 47370240 resident: 22675456 share: 13557760 rss: 22675456 rss_rlim: 4294967295 CPU usage: start_time: 1180874520 rtime: 155 utime: 138 stime: 17 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 -1208502592 (LWP 26942)] (no debugging symbols found) 0x00958402 in __kernel_vsyscall ()
+ Trace 137788
Thread 1 (Thread -1208502592 (LWP 26942))
----------- .xsession-errors --------------------- localuser:Pierre being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2698 Loading "installonlyn" plugin Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x3000003 non valide indiquée pour 0x3000342 (Garder la ). Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x2800003 non valide indiquée pour 0x2800271 (Garder la ). compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 "/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 ***