Description of problem: Running openbox without redhat-menus installed causes the the application menu to popup error dialogs... Probably it would be better if openbox required redhat-menus?
Not sure about this, I was under the impression that redhat-menus is dead. All bugs I filed against it never got any attention and the source code is not available to the public. So before we make openbox depend on it, we should figure out what's up with redhat-menus. Just my 2 ¢.
Well not sure about deadline or its exact status but various *-menus packages pull it in so I was assuming it is still the basis of traditional Fedora desktop menus: For F17: $ repoquery -q --whatrequires redhat-menus | wc -l 34 and 25 for F18. This includes highlevel packages like control-center, gnome-desktop, kdelibs, and lxmenu-data, mate-desktop, and xfdesktop. So I don't think it is quite dead yet. :) While I agree it is unfortunate the project is not on fedorahosted say and perhaps not a high priority for the Desktop team, I can't see how it prevents openbox from using it (well I think it actually needs it for its menus to work?).
(In reply to comment #2) > Well not sure about deadline or its exact status but various > *-menus packages pull it in so I was assuming it is still > the basis of traditional Fedora desktop menus: > > For F17: > > $ repoquery -q --whatrequires redhat-menus | wc -l > 34 > > and 25 for F18. > > This includes highlevel packages like control-center, gnome-desktop, > kdelibs, and lxmenu-data, mate-desktop, and xfdesktop. I know, two of these are mine: xfdesktop and lxmenu-data. While working in xfdesktop if found a couple of bugs, e.g. menus from redhat-menus include stuff from gnome-menus - while it should be the exact opposite. > So I don't think it is quite dead yet. :) But it smells funny. ;) I think we should rename it to system-menus (just like redhat-config-* became system-config-*) and move it to fedorahosted. I'll discuss this with the desktop team. But this shouldn't be a blocker for this bug, I am going to work on it. The only question that comes to my mind: Does this justify an update for the stable releases?
openbox-3.5.0-8.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openbox-3.5.0-8.fc18
Speak up if you want this update for a stable release, otherwise it will be closed automatically when the update for F18 gets pushed.
Package openbox-3.5.0-8.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openbox-3.5.0-8.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15070/openbox-3.5.0-8.fc18 then log in and leave karma (feedback).
Thanks! system-menus sounds like a good idea. +1
Somehow bodhi forgot to close this one.
openbox-3.5.0-9.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/openbox-3.5.0-9.fc17
openbox-3.5.0-9.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.