If I click on one entry in the global menu (such as File) and then hover to another entry (such as Settings), the menu doesn't switch to the hovered entry. The menu still has this behaviour in 5.9.2. I think this same issue was filed here: https://bugs.kde.org/show_bug.cgi?id=375535 but it was closed and I don't seem to have the ability to reopen it.
Can you perhaps create a video, so I can see exactly how it doesn't react and how your panel and everything is setup? We might have found yet another position mapping glitch :/
Created attachment 104151 [details] global menu doesn't open on hover I am also having this issue under 5.9.2 and Qt 5.8.0
(In reply to Kai Uwe Broulik from comment #1) > Can you perhaps create a video, so I can see exactly how it doesn't react I could do that later, but I think I described the behaviour well enough. > and how your panel and everything is setup? I'll attach a screenshot of my setup.
Created attachment 104152 [details] screenshot of my panel setup, for purposes of replication
I can confirm the same bug (bug or a feature?) Also I see another bug...my Global Menu doesn't persist between reboots, instead I'm left with empty white panel. :( (I'm so sad.....) Plasma 5.9.4 KF5 5.33.0 Qt 5.8.0
I don't think this is a simple glitch. If you open a menu under X11, you'll find that hover events don't get passed through to other windows unless you click to close the window first (this click also doesn't get passed through, of course). The only exception is in a menubar, where hovers *do* get passed through so this switching behaviour can be implemented. The global menu applet isn't *really* a menubar, so this doesn't work here.
Created attachment 105444 [details] qml replacement Moving the Connections object to the root in /usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/main.qml fixes this. You can use the attached file as a replacement, though it has a couple of other changes (removing the underlining, and reducing the spacing between menus).
*** This bug has been marked as a duplicate of bug 375535 ***