Bug 458851 - Application menu sometimes doesn't want to open
Summary: Application menu sometimes doesn't want to open
Status: RESOLVED DUPLICATE of bug 455575
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.25.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-09-07 22:00 UTC by Johannes Joens
Modified: 2022-09-09 05:16 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
kde button that doesn't open menu (1.23 MB, image/png)
2022-09-09 04:43 UTC, Johannes Joens 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Joens 2022-09-07 22:00:56 UTC 
SUMMARY
***
When  trying to open the application menu it sometimes doesn't want to open, after waiting a bit and retrying it works for a bit until it reverts to not wanting to open
***


STEPS TO REPRODUCE
1. Click on the application menu button
2. Wait
3. Try again
4. repeat as many time as you want

OBSERVED RESULT
Application menu sometimes open but not always 

EXPECTED RESULT
Application menu always opens

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernal version: 5.19.7-zen2-1-zen (64-bit)
Graphics Platform: Wayland
nvidia-open-dkms: 515.65.01-11

ADDITIONAL INFORMATION
Only seems to happen on wayland not on x11
Comment 1 Nate Graham 2022-09-09 04:36:11 UTC 
What application menu button? Can you attach a screenshot that shows exactly which button you're clicking?
Comment 2 Johannes Joens 2022-09-09 04:43:45 UTC 
Created attachment 151942 [details]
kde button that doesn't open menu

Requested picture of which button i tried to press.
Comment 3 Nate Graham 2022-09-09 05:16:13 UTC 
Ah that. And you're on Wayland with NVIDIA hardware, oh joy! That means you're hitting Bug 455575.

*** This bug has been marked as a duplicate of bug 455575 ***