SUMMARY The clickable area on the left and right side of a vertical panel on the left side of the screen isn't as wide as it is for panels on other sides of the screen. STEPS TO REPRODUCE 1. Create a default panel and place it on the left side of the screen. 2. Click on the very left or right edges of the Desktop Pager, Task Manager, System Tray, Digital Clock (w/ date, click near the time). OBSERVED RESULT The clicked widgets will not be opened/activated. EXPECTED RESULT The clicked widgets should open/activate. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20190520 KDE Plasma Version: 5.16.80 (git master) KDE Frameworks Version: 5.59.0 (git master) Qt Version: 5.12.3 Kernel Version: 5.1.2-1-default ADDITIONAL INFORMATION This issue began near the start of Plasma 5.16's development, but I didn't know how to properly define the problem until now. https://www.youtube.com/watch?v=V-Qb2aSXjR4 This video shows me clicking on the outside edges of the panels, but the inside edge of a left side vertical panel has the same problem. I am clicking roughly once or twice a second.
(In reply to Noah Davis from comment #0) > I am clicking roughly once or twice a second. Actually, that was for an older version of the video. Now I'm just clicking where I pause.
This problem does not exist on Wayland.
Do you have a KWin touch screen edge active on the left side of the screen? System Settings > Desktop Behavior > Touch Screen
(In reply to Nate Graham from comment #3) > Do you have a KWin touch screen edge active on the left side of the screen? > System Settings > Desktop Behavior > Touch Screen I've tested it with and without and it didn't make a difference
That... doesn't seem possible. :(
(In reply to Nate Graham from comment #5) > That... doesn't seem possible. :( Actually, I was wrong. Disabling it did work, but the reason why I thought it didn't work was because I have to restart my computer after disabling it for it to make a difference. Restarting Plasmashell and KWin is not enough.
*** This bug has been marked as a duplicate of bug 387775 ***