Bug 450169

Summary: Apps sometimes don't start by mouse click on Wayland
Product: [Unmaintained] kdeplasma-addons Reporter: Jan Rathmann <jan.rathmann>
Component: Application DashboardAssignee: Eike Hein <hein>
Status: RESOLVED FIXED    
Severity: normal CC: jan.rathmann, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.24.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jan Rathmann 2022-02-13 17:53:47 UTC
Hello,

sometimes launching apps by mouse click in the Application Dashboard gets "broken" in the Wayland session: That means, if I click on the respective application icon, the Dashboard disappears as usual but the application is not started (as if I had clicked somewhere on the free space inside the Dashboard).

Unfortunately, so far I was not able to find out how I can deliberately trigger this bug, so that anyone else can test if it's reproducable. Anyway, here is what I know about it:

* I never saw this when using X11, only on Wayland since I switched ~3 months ago.
* For some time after session start, everything work ok.
* Then at an unknown point launching apps by mouse click doesn't work anymore, as described above. It seems to stay this way (it always doesn't work) until I restart the session.
* It doesn't affect launching apps by keyboard: If I type the app name on the Dashboard and press Enter, it works just fine (my workaround when the bug appears)
* It happens often: It's common that I notice this bug at least once a day.
* I tried to see if I can artifically trigger the bug by testing some situations of daily usage (e.g. video playback in browser, open several apps etc.), but nothing of that seemed to trigger the bug directly.
* Upgrading Plasma from 5.23 to 24 didn't make any difference.

Kind regards, Jan

SOFTWARE/OS VERSIONS
Kubuntu 21.10 + Backports-PPA
KDE Plasma Version: 5.24.0
KDE Frameworks Version:  5.90.0
Qt Version:  5.15.2
Comment 1 Jan Rathmann 2022-10-20 17:03:02 UTC
Since I haven't seen this bug for a long time, I assume it somehow got fixed during this year :)