Bug in unstable menu package?
Hello, I have recently dist-upgraded from potato to sid, and I have noticed that update-menus does not generate all of the available menu entries. There are many more menu entries in /usr/lib/menu[/default] that are not present in the menus themselves. For example, gnome-terminal provides /usr/lib/menu/doc-base-gnome-terminal but there are no entries in the Gnome/KDE/wmaker/mwm menus. There are no window manager menus, rendering Window Maker unusable (I can't save a session, quit etc.). If I run update-menus with debugging on, I see it reads the entries OK, and then pipes data to each of the menu-methods. I can't see where the problem is. I assume it must be in update-menus itself, as I see missing entries in several menu-method backends. Is there anything else I can do to diagnose/correct the problem? Thanks, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ For GPG Public Key: finger [EMAIL PROTECTED] or see public keyservers.
Re: 'menu' package : question : console support ? ; mailing-lists
On Wed, Aug 30, 2000 at 06:26:15AM -0700, Sean Champ wrote: if the debian 'menu' package [ http://www.debian.org/doc/packaging-manuals/menu.html/ ] does offer console-support , this email can probably be disregarded. Well, i don't believe menu has a non-command-line interface at all. It just creates menus for other apps to work with. Sean 'Shaleh' Perry explains this in more detail. ( on a tangent is a question that has been pending for a while, here. would people like|support a (probably, very minor) degree of regulated parliamentary procedure, on the mailing-lists? Considering how much trouble some people seem to have with just unsubscribing, i don't see how you could get them to follow a procedure. In general, the volume of newbies on this list will demolish any attempt to impose order... - bug-report ( debian-bugs ? ) Go to the bug tracking system (see the website). There's no use in even posting messages saying that the bug has been reported and is being worked on, people will continue to ask is this a bug? for weeks after it's fixed. - request-for-feature File it as a wishlist bug, or contact the upstream maintainer. - intent-to-package ( to be directed to debian-devel , no?) This is discussed in the developer documentation, and doesn't affect debian-user at all. - usage-question - general question This seems the difference between what command does X and how do i do X with foo (which usually brings about suggestions of using bar, baz, and qux as well). It'd be more useful IMNSHO to just convince people to come up with informative subject lines. - others? Offtopic? Convince people to add OT: to the subject line, as most mailers add Re: now. And teach people how to change subject lines when the topic drifts, to use compose new message instead of reply when necessary, and in general to use mailers that don't break threads. That's just my $1.50 (damn inflation) -- finger for GPG public key. pgpoIymaLz3lc.pgp Description: PGP signature
'menu' package : question : console support ? ; mailing-lists
hi.
if the debian 'menu' package [
http://www.debian.org/doc/packaging-manuals/menu.html/ ] does offer
console-support , this email can probably be disregarded.
( having a need to stay booted to ms-w right now, i can't check this myself,
yet. also, the following )
if it ('menu') doesn't offer console-only support:
this email will hopefully be taken as a request for that feature, and as a
presentation to the forum for the opening of discussion about how some
console-support could be implemented.
( on a tangent is a question that has been pending for a while, here.
would people like|support a (probably, very minor) degree of regulated
parliamentary procedure, on the mailing-lists?
, and i'm not meaning anything like what might be used by the
freemasons or
congress or the UN, by that. but it seems like there would be a few general
classifications of mailing-list traffic:
- request-for-feature
- intent-to-package ( to be directed to debian-devel , no?)
- bug-report ( debian-bugs ? )
- usage-question
- general question
- others?
... and certain ways that a list-post of each type would be handled.
( and the option to develop some software-ish things to handle the posting and
managing of such list-posts )
and this should maybe be stated in a seperate email, but i like to present it
when there's an example of something that it seems relevant to. namely, the
intent of this email . also, kind of like pinging people with the idea, to see
what comes back in-reply.
)
if 'menu' does not have console-support yet, here are some initial ideas about
how this might be implemented.
feel free to disregard the following if your time is short and|or if you're not
a developer and|or if you're not interested in it, but i'm still working my way
into development, and would like to hear what some experienced people would have
to say about the following, time-allowing .
( ... 'community' . )
1) i'd installed the 'screen' package. it seems like this might be used as a
route towards implementing a console-based menu system.
a) problem-issues:
1) something about the way the screen would flash at times.
(ech and a feeling of something that might be
fishy in or about the code or
method-of-implementation . )
2) i don't know how to rate 'screen' on resource-usage,
or if it might have any other problems that i'm
not yet aware of.
2) i know that there are already some console-based menu systems that have been
developed. saw one of them somewhere in the debian package-tree. ( as well as
suggestions on what their names are ... it was a while ago that i saw them ) any
help with deciding about which is the better of the options, would be
appreciated.
3) the following tasks would seem to be worth inclusion
as functions accessible via a menu-system:
-- mailing-list posting,
categorized by the purpose of the post
-- package-management, probably just something
to start-up dselect, but maybe otherwise.
-- system-management.
(e.g.: easy access to config-files,
as a means for the new user to get acquainted
with what's where and which files
and paths are for what purposes )
-- help-doc access. maybe just an interface to
dhelp. maybe otherwise.
( when 'otherwise' is meant kind of like a stub-code
for some pending reports, proposals,
and work )
-- debian-tips , when that finally gets developed
and released.
-- maybe something for new-users. sort of an (interactive)
walk-through, towards familiarizing someone with the
Linux environment.
and a 'debian-devel' module to handle things like:
-- debian-rules
-- CVS-functions
-- (insert-[helpful|time-saving]-thing-here)
( I still haven't made it throughly
into debian-devel, packaging, and updating
of out-of-date packages. ( pppoe , for example ) .
i don't know what's out there for development-tools,
yet. )
...and that might be enough, for now.
hoping that the statement, feel free to disregard the following, was enough to
keep this from seeming like some excessive text,
--
s.c.
RE: 'menu' package : question : console support ? ; mailing-lis
On 30-Aug-2000 Sean Champ wrote:
hi.
if the debian 'menu' package [
http://www.debian.org/doc/packaging-manuals/menu.html/ ] does offer
console-support , this email can probably be disregarded.
( having a need to stay booted to ms-w right now, i can't check this myself,
yet. also, the following )
if it ('menu') doesn't offer console-only support:
this email will hopefully be taken as a request for that feature, and as a
presentation to the forum for the opening of discussion about how some
console-support could be implemented.
menu only supports the creation of menu files. It is up to packagers to supply
scripts to make menus for their programs. There is a console package called
pdmenu which will read the Debian menu system.
[Philadelphia] Debian's Menu Package: A Catalog of Debian Software
The Philadelphia Area Debian Society (PADS) (http://www.CJFearnley.com/pads/) presents Debian's Menu Package: A Catalog of Debian Software When: Wednesday 15 December 1999, 8:00 PM - 9:30 PM Speaker: Chris Fearnley, Senior Vice President Technology, LinuxForce Inc. Where: IQ Group, 6th floor (its the room with a big Q on the door) 325 Chestnut Street Philadelphia, PA Abstract Menus are a now familiar device to index the functionality of a system. Debian's menu package provides a mechanism for each Debian package to provide a menu interface to its software. We will describe the system and explore how to use it as a user, a system administrator and a developer. Dinner Attendees are invited to gather for dinner prior to the meeting at 6:30 PM at The Mexican Post, 104 Chestnut Street, Philadelphia, PA. Please RSVP so we can get an appropriate sized table. -- Christopher J. Fearnley | LinuxForce Inc. [EMAIL PROTECTED] | Senior Vice President Technology http://www.LinuxForce2000.com| Design Science Revolutionary Dare to be Naïve -- Bucky Fuller
Re: menu package
Hi,
I just did an upgrade from menu version 1.3-2 to 1.4-1 and I noticed that
the program update-menus provided by the new package segmentation faults
when the pre-removal and post-removal scripts execute it. This effects
packages such as procps and xproc. Anyone seen this? Thanks...
No, I haven't (I'm the author).
Is it really update-menus that segfaults, or the install-menu
programme? (usually you cansee this from the output, or when it
crashes -- what's the output for you?).
If you're sure it's update-menus, could you do:
tar -czf - /etc/menu /usr/lib/menu|uuencode menu.tgz|mail -s menufiles [EMAIL
PROTECTED]
I'm rather convinced it's something to do with one of the menufiles you
have, and the above way is about the only to find out what.
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
menu package
Hi, I just did an upgrade from menu version 1.3-2 to 1.4-1 and I noticed that the program update-menus provided by the new package segmentation faults when the pre-removal and post-removal scripts execute it. This effects packages such as procps and xproc. Anyone seen this? Thanks... J. Goldman -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
