GNOME Bugzilla – Bug 430774
crash in Main Menu: J'étais occupé avec l'ap...
Last modified: 2007-04-18 00:19:43 UTC
Version: 0.11.3 What were you doing when the application crashed? J'étais occupé avec l'application "main menu" 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.3079.fc7 #1 SMP Mon Apr 16 20:28:25 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 67018752 vsize: 67018752 resident: 25804800 share: 15179776 rss: 25804800 rss_rlim: 4294967295 CPU usage: start_time: 1176846674 rtime: 881 utime: 758 stime: 123 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 -1208310080 (LWP 3636)] (no debugging symbols found) 0x00e5d402 in __kernel_vsyscall ()
+ Trace 128598
Thread 1 (Thread -1208310080 (LWP 3636))
----------- .xsession-errors --------------------- File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 593, in setup raise Errors.RepoError, ('Cannot open/read repomd.xml file for repository: %s' % self) RepoError: Cannot open/read repomd.xml file for repository: livna Local variables in innermost frame: self: livna cache: 0 e: failure: repodata/repomd.xml from livna: [Errno 256] No more mirrors to try. mediafunc: None Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x65 non valide indiquée pour 0xe066b9 (). 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 ***