Re: bo-unstable 'menu' seems to affect at least xlock programs

[joost@rulcmc.leidenuniv.nl (joost witteveen)]

> On Tue, Jan 20, 1998 at 09:38:09PM -0500, Dirk Eddelbuettel wrote:
> > 
> >   David>  The bo-unstable menu program seems to cause some nasties with
> >   David> regards to at least the xlock programs, possibly with others as well
> >   David> (I didnt check, I just reinstalled from the regular bo).
> > 
> > Could you provide more details? With which version of xlockmore does it
> > clash, on from bo or a more recent one? Is it simply a matter of who owns
> > /usr/lib/menu/xlock ? That appears to have been fixed in the last menu
> > package.

/usr/lib/menu/xlockmore was never owned by the menu package, and can thus 
not be fixed by the menu package. Nor can providing a 
/usr/lib/menu/default/xlockmore file cause problems when another package
(xlockmore) provides /usr/lib/menu/xlockmore. But this guy's problem
seems to be that he doesn't have a recent xlock version:

> I do not know the menu system all that well, but what seems to change
> between the stable menu and the bo-unstable menu is that the unstable
> one has no 'default/xlockmore'.  I think this is a problem with the
> menu package, not xlockmore.

OK, so basically, your problem is that you don't have the xlockmore
entries in your window-manager menu any more? Probably that will fix
itself when you install a more recent version of xlockmore, version
4.05-1 or higer will probably do. That will install /usr/lib/menu/xlockmore
and solve your problems. (As xlockmore now provides a menufile, I
removed the one in the menu package.).

Thanks




-- 
joost witteveen, joostje@debian.org

Potentially offensive files, part 5: /dev/random.
`head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries).


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .