Bug 479340 - Global menu closes when menu item is clicked
Summary: Global menu closes when menu item is clicked
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Global Menu widget (show other bugs)
Version: 5.92.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6, wayland-only
Depends on:
Blocks:
 
Reported: 2024-01-03 06:35 UTC by Doug
Modified: 2024-02-21 07:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Global menu disappearing when clicked (1.12 MB, video/webm)
2024-01-03 06:35 UTC, Doug
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Doug 2024-01-03 06:35:14 UTC
Created attachment 164644 [details]
Global menu disappearing when clicked

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. set up plasma with a top panel and global menu widget
2. start a plasma session
3. open an app that supports global menu widget and try to click on a top level item (File, Help, etc) in the global menu

OBSERVED RESULT
global menu disappears

EXPECTED RESULT
global menu doesn't disappear and sub menu appears

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Neon Unstable
(available in About System)
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
This is an intermittent issue, but has been persistent for a while
Comment 1 Doug 2024-01-12 05:07:31 UTC
I'm sorry, but why was the keyword for the version changed from 5.91.0 to 5.27.10?  I haven't had this issue in my Plasma 5 installs ever, it seems like it is specific to Plasma 6.
Comment 2 Nate Graham 2024-01-12 20:36:37 UTC
Aha, thanks for that info.
Comment 3 Doug 2024-02-21 07:10:42 UTC
I haven't seen this issue for a few weeks now, I'm going to assume it got fixed somewhere, somehow.