Red Hat Bugzilla – Bug 70843
sawfish menus do not work at all (simple fix)
Last modified: 2007-04-18 12:45:15 EDT
Description of Problem:
In sawfish as present in limbo 2, menus do not work at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start sawfish
2. attempt to invoke a menu
no menu appears
a menu should appear
The problem is that the "gui" directory in the rep-gtk installation appears in
/usr/libexec/rep/i386-redhat-linux-gnu instead of
/usr/libexec/rep/i386-redhat-linux. (Or, the problem is that the former
directory is not in dl-load-path.)
Moving the gui directory from /usr/libexec/rep/i386-redhat-linux-gnu to
/usr/libexec/rep/i386-redhat-linux solves the problem.
I've set the severity of this bug to "high" because it renders sawfish largely
unusable and has a trivial fix.
Gratuitous commment: I've been using sawfish (or sawmill) since before it was
RedHat's default and will continue to use it now that it is (sadly) no longer
the default. I'm glad it's still present in the distribution. I hope it stays.
It offers functionality (through its lisp interface) that no other modern
window manager can provide.
I apologize for the noise on this bug. I accidentally selected the wrong
component when I posted the bug thus causing botched assignments. I hope I've
fixed it by selecting "Assign but to owner of selected component".
Oops. On the version of bugzilla I use (2.16), when a poster changes an
assignee, the status reverts back to NEW rather than going straight to assigned.
If I don't see anything happen on this, I'll kill it and repost. Again, sorry
for the noise here. I just tend to be very anal during beta periods so that I
can enjoy releases that work perfectly for all my needs. :-)
Have you tried rep-gtk-0.16.0.90-4 from Rawhide?
With these versions from rawhide:
this problem is corrected. The dependencies are such that you can upgrade
rep-gtk and librep without upgrading sawfish and then get a partially paralyzed
sawfish, but I suppose there's not much that can be done about that. Upgrading
all three packages does solve this problem without introducing any new ones that
I've found so far. Thanks. Presumably this will be in the next beta, release,