Description of problem: In many cases, applications are put in the plus sub-menu when the parent has very few items. The main menu starts with 8 items, 7 sub-menus plus the installer (rpmdrake), although the user can add more. Applications when installed are usually put in one of those sub-menus. Sometimes they are put in a sub-menu, when the parent has as little as 7 items. This is a nuisance at best. An exception is applications put in the tools menu, or its' sub-menu system. There no plus sub-menu is created, even if these menus contain many more lines that can fit in a screen page. (In such cases, a scroll bar would be nice.) It would be much better if the plus menu were never used, as except for the tools menu, few of the main sub-menus would need more than a screen page. It they did, scrolling could be used, as in the tools sub-menu Note that it may be that mozo is not responsible, although it does display and edit the menu. Version-Release number of selected component (if applicable): This problem is not new. How reproducible: Steps to Reproduce: 1. 2. 3.
Forgot to note : this problem occurs in Mate desktop environment, on MGA 7 fully updated. If it occurs in other DE's, either mozo is not responible, or the problem is replicated elsewhere.
Hi, thanks taking time to report this. In facts, populating main menus is a responsibility of packagers in a RPM SPEC file when packaging a RPM. This is our choice to make some applications available at main part of menu and populating other applications in a "Plus" sub-menus in that category. For example, Mozilla Firefox is (in M7) in a "Plus" sub-menu of Internet category on Plasma. In M8, it will be in main menu of the Internet category as it is the default browser. It is not the responsibility of the desktop environment to make these choices. We intend to display for example Plasma apps in main menu when the DE is Plasma and populate "Plus" with GNOME/GTK app. Also, there is some Menu editor in each desktop environment to edit the application menu per user basis. If a program/application should be in main part of a category and not in a "Plus" sub-menu, please open a new bug report for this application, suggesting also a screenshot to show us the problem. Closing this INVALID.
CC: (none) => ouaurelienResolution: (none) => INVALIDStatus: NEW => RESOLVED
In your 4th paragraph you are saying that the desktop chosen DOES make a difference. I tested Firefox, and on Maté desktop/mga7 it also installs in plus. But there is no code in the spec file, nor in the .desktop file specifying the plus menu. There may be some code in a menu file, but I didn't notice a reference to a menu file in the firefox spec. (Which is very long and somewhat confusing at first glance.) It is a while since I did packaging, but I suspect it is related to something like gnome and/or kde or plasma keywords. If so, it is almost certainly decided by the desktop. (That is, the desktop decides to put applications with or without certain keywords in the plus menu.) I should have realised it is not decided by the menu editor. But I don't know what application handles this. So the srpm is changed to unknown. However reopening, as it is a problem I think should be fixed. In this case, for the Maté desktop. Changed title to reflect this.
Status: RESOLVED => REOPENEDSource RPM: /usr/bin/mozo => unknownResolution: INVALID => (none)Summary: plus submenus are used when the parent menu has very few items => In Maté desktop, plus submenus are used when the parent menu has very few items
Sorry for leaving this in aches. Assigning to Mate maintainers. CC'd some other DE maintainers for advice. Note also the Firefox issue (under "Plus") is fixed.
Source RPM: unknown => mate-desktop-1.22.1-1.mga7.src.rpmAssignee: bugsquad => smelrorStatus: REOPENED => NEWCC: (none) => geiger.david68210
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD