Re: Menu errors [fixed]
- To: Debian Users List <firstname.lastname@example.org>
- Subject: Re: Menu errors [fixed]
- From: Adrian Bridgett <email@example.com>
- Date: Tue, 30 Sep 1997 22:10:23 +0000
- Message-id: <19970930221023.55565@wyvern>
- Reply-to: firstname.lastname@example.org
- In-reply-to: <Pine.LNX.3.95q.970929013006.8576Aemail@example.com>; from Will Lowe on Mon, Sep 29, 1997 at 01:31:02AM -0400
- References: <19970929000038.00510@kite> <Pine.LNX.3.95q.970929013006.8576Afirstname.lastname@example.org>
On Sep 29, Will Lowe wrote
> On Mon, 29 Sep 1997, Joey Hess wrote:
> > You seem to have a number of executable menu files. Look in /usr/lib/menu
> > and /etc/menu - remove the executable permissions of any files there that
> > are executable (and file bugs on the packages that placed them there.)
> Ah, yes. It was /var/lib/menu/fvwm95 ... a simple "sudo chmod -x fvwm95"
> seems to have been the fix, and I've filed a bug against fvwm95.
Why does this cause a problem - surely update-menus only needs read
permission on the files - any other permissions are just "extra".
I aggree the permissions shouldn't be there, and that a bug report should
be filed against fvwm95, but I've been bitten by the same "feature" :-(
NB: This "feature" was still present in menu 1.5-2.
email: email@example.com | Artificial intelligence - the
http://www.poboxes.com/adrian.bridgett | art of making computers act
PGP key available on public key servers | like those in the movies
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .