Created attachment 532768 [details] My sorted full package list. rpm -qa | sort Description of problem: A installed alacarte menu editor. I ran it, and then I got the following error message: Traceback (most recent call last): File "/usr/bin/alacarte", line 22, in <module> from Alacarte.MainWindow import MainWindow File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 19, in <module> import gtk, gmenu, gobject, gio ImportError: No module named gmenu I use Xfce, don't install Gnome or KDE. Please see my installed packages! Version-Release number of selected component (if applicable): alacarte-0.13.2-3.fc16.noarch Additional info: Please see my package list.
sorry about this. Alacarte currently does not work. It needs to be adapted to api changes in gnome-menus.
There are about 50 duplicate bug reports for this error (e.g. bug #757585). The abrt bug reporter doesn't seem to be very smart about identifying duplicates if the backtraces come from Python. I'll try to mark them all as dupes of this one.
A work-around using gnome-menus from Fedora15 can be found at http://blog.mclaughlinsoftware.com/2011/11/24/gnome-menu-editing-fix/
(In reply to comment #2) > There are about 50 duplicate bug reports for this error (e.g. bug #757585). > I'll try to mark them all as dupes of this one. Why this one, when there's bug #734442 which is much older and has more activity?
(In reply to comment #4) > (In reply to comment #2) > > There are about 50 duplicate bug reports for this error (e.g. bug #757585). > > I'll try to mark them all as dupes of this one. > > Why this one, when there's bug #734442 which is much older and has more > activity? I didn't happen to notice that bug (there are so many alacarte bugs, and I was doing a quick scan of the list), but the other you mention is probably better. Also you'll notice that I haven't actually got around to marking the duplicates, so feel free to do so. :)
(In reply to comment #5) > Also you'll notice that I haven't actually got around to marking the > duplicates, so feel free to do so. :) I don't seem to have sufficient permissions to change the status of bugs, so I can't.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.