> (3)
> I found an entry "idle" in menu --> development. I discoverd (with "man
> idle") that it's a primitive system call. It does not work at all (causes
> a sequence of unresolved symbol... seg. fault etc.etc.) so I tried to
> delete it from menu, with menudrake. The result was that I lost almost
> ALL the entries in menu, and even the "exit" voice in WindowMaker... I
> got out with a "kill -9" !!!
Do you launch menudrake from Drakconf, or menu, or a other way ?
Do you launch menudrake as user or as root ?
Which desktop you use ?
IDLE seen to call the python shell, i don't have trouble when i remove this
entry in my computer.
update-menus make long time to regenerate your menus (in fact menudrake
keep save button disable since this task), after this you have to wait for
your desktop refresh they menus, on KDE2 you can configurate this
parameters in kcontrol.
> (4)
> Again, with menudrake, if I try to change that horrible "question_mark
> icon" with something else, I can have 2 possibilities:
> a) Nothing change, even if I work with "root account"
> b) Menu is drastically modified, and I lost entries
if you are root you can't modify your menus entries (limitation of debian
menu). It's a good habit to not use your root account to work.
Perhaps root can change system menu with a argument on the menudrake
comment ligne (for ex --edit-sysmenu). It's that is call when you use
menudrake from the DrakConf interface.
If you edit the system menu you change the menu for all the users of the
system, files is save in /etc/menu/ directory. When you use menudrake as
user it write menu entries in ~/.menu/ directories.
Can you exactly send me your manipulation please, menu is very complex and
i can't reproduce the bug here.
Thank you for our bug report in all case.
Vince
--
Vincent Saugey -- Distribution Developer for MandrakeSoft
