Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Applications menu empty #50

Open
cryobry opened this issue May 12, 2019 · 4 comments
Open

Applications menu empty #50

cryobry opened this issue May 12, 2019 · 4 comments

Comments

@cryobry
Copy link

cryobry commented May 12, 2019

Fedora 30
19.04.0

The applications menu is completely empty when I open the menu, although the recent documents and places plugins are working fine. There don't seem to be any errors raised in the journal that I can find.

bug

@vkareh
Copy link
Member

vkareh commented May 12, 2019

Seems like an error with libmate-menus. Have you reported to the Fedora bugzilla?

@cryobry
Copy link
Author

cryobry commented May 12, 2019 via email

@darkshram
Copy link

darkshram commented Jun 24, 2019

ALDOS (fork of fedora without SystemD)
mate-menu 19.04.0

I have the same issue. I don't think to be a mate-menu issue. It's definitely something weird with mate-menus library in certain desktop scenarios:

  • my PC has tons of applications and other DE installed for testing. In this scenario mate-menu has no applications menu.
  • My laptop only has MATE, Xfce and KDE. Mate-menu works perfectly there without touching anything.

Because mate-menu was unusable with the applications menu empty, I started using brisk-menu, which showed the applications in the menu. Strangely the applications menu showed the preferences categories in the application menu. They are not supposed to be shown in applications menu, so I used mozo and tried to removed the preferences categories from the menu with mozo. These categories had no icons and neither disappeared from brisk menu until I did 'mate-menu --replace &'.. Funny thing is I was trying to debug mate-menu and to my surprise the applications were back in the applications menu.

Captura de pantalla -2019-06-24 10-35-40

So, it seems to be related with the preferences categories, which neither mate-menu or brisk-menu use (both use a mate-control-center desktop entry). Removing the preferences categories fixed the issue for me, but made them disappear from the other menu applets, which actually make use of preferences categories.

Back up ~/.config/menus/. Then use mozo and remove ALL the preferences-related categories from the menu. Then do:
mate-panel --replace &

And check if the applications menu is back.

In my case, if I delete ~/.config/menus/ (a hard and violent reset way), applications menu is gone.

Captura de pantalla -2019-06-24 10-18-36

But, if using mozo and then removing all preferences categories, makes applications menu come back in mate-menu.

@byteit101
Copy link

byteit101 commented Mar 5, 2022

I just struck this on my upgrade from Debian 10 to 11. It wasn't the preferences for me, but instead a 3rd party icon issue.

I narrowed it down by unchecking (in mozo/preferences) items to do a binary search of which items were causing the issue. once I unchecked "Xilinx Design Tools", everything came back. I've had those tools installed since Debian 8, and they only now caused issues. As I would like to use them from time to time, I investigated which tool was causing the issue, and as it turns out it was the root entry causing issues. It had no icon except the default, and setting the icon to anything made them load properly. I'm unsure why the "Wine" category with an unset/missing icon doesn't cause the same issue.

Of note, when running mozo before I updated the icon, I got this output. It vanished after I set the icon:

$ mozo
/usr/lib/python3/dist-packages/gi/overrides/Gtk.py:1649: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  return _Gtk_main(*args, **kwargs)
$

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants