While investigating bug 15835, I found another bug: if I add, touch or remove a .desktop file in /usr/share/applications while menu-cached is not running, when menu-cached is launched, it does not detect the modification and the menu cache is not updated. I made a bug report on LXDE bug tracker: https://sourceforge.net/p/lxde/bugs/752/.
lxde-common-0.99.0-9.mga5 contains the patch force-menu-cache-regeneration-on-login that provides a solution for this bug.
I have no menu in LXDE after I updated lxde-common-0.99.0-9.mga5.
CC: (none) => yochenhsieh
What is the result of the following command? /usr/libexec/menu-cache/menu-cache-gen -i /etc/xdg/menus/applications.menu -o /tmp/test.txt -vvv
Created attachment 6543 [details] output of command
Created attachment 6544 [details] /tmp/test.txt
Menu cache generation looks good. Is the directory $HOME/.cache/menus/ empty? Is the process /usr/libexec/menu-cache/menu-cached running? Does the menu reappear after log out then log in?
Yes, ~/.cache/menus is empty. Yes, menu-cached is running. No, menu won't reappear.
Is ~/.cache/menus writable by the user? Does the menu reappear if you add, touch or remove a .desktop file in /usr/share/applications?
Yes, permission is 700 for the user. No, any change to desktop files in /usr/share/applications won't affect the menu.
In the file ~/.config/lxsession/LXDE/desktop.conf, section [Environment], what is the value of menu_prefix?
menu_prefix=lxde-
If you replace with "menu_prefix=", it should correct the problem. Normally this problem can only affect machines that have been running Cauldron and not the ones upgrading from Mga4.
Yes, that fixed it. This is indeed my cauldron vm. But what will happen if a machine installed Mga5 alpha and followed cauldron development since then?
I think the problem may be the same. It is preferable to remove ~/.config/lxsession/LXDE/desktop.conf (and maybe ~/.config/lxpanel/LXDE/panels/panel also) before logging into LXDE after Mga5 is released.
Does this piece of advice apply to some extent to Mageia 4 users? If so, a note in the release notes or errata would be nice. If only cauldron users are affected (including those having tested the alpha), I don't think a note is needed. If RC users are affected, then I'd add a note saying it applies only to people who tested a development version of Mageia 5. What would be the last not affected pre-mga5 ISO?
After some tests, it appears that it can also affect Mga4 users if they had launched lxsession-default-apps and clicked the button "Apply" in the Settings section, entry "menu prefix". So I think a note in the release notes or errata would be nice. How to do that?
The errata is on our wiki here: https://wiki.mageia.org/en/Mageia_5_Errata#LXDE I've added it. Please feel free to add more info if you need.
Whiteboard: (none) => ERRATA
(In reply to You-Cheng Hsieh from comment #17) > The errata is on our wiki here: > https://wiki.mageia.org/en/Mageia_5_Errata#LXDE > I've added it. Please feel free to add more info if you need. There should be some elements of context in the errata entry: what users are likely to be concerned by the issue.
Whiteboard: ERRATA => FOR_ERRATA
i have updated the errata https://wiki.mageia.org/en/Mageia_5_Errata#LXDE concerning this problem so I close the bug.
Status: NEW => RESOLVEDResolution: (none) => FIXEDWhiteboard: FOR_ERRATA => IN_ERRATA