After switching virtual desktops through the pager, it seems the system sends a wrong mouse signal which causes this bug: https://github.com/SublimeTextIssues/Core/issues/893#issuecomment-534408322 From the comment there: "This was a fun one, after many days using a surface book instead of my workstation I was able to reproduce this. Turns out gtk/X/linux gets into a state where it thinks a mouse button is being held down. Sublime Text does not allow you to scroll (along other things) when a mouse button "modifier" is being pressed, while most other applications don't care. This explains why it persists across Sublime Text and Merge even through application restarts. You should be able to confirm this using xev by looking at the modifiers. As a work around for this we'll be ignoring mouse button 1 as a modifier in the future for linux." The issue then goes away after switching to a different application.
Where does that bug report mention switching virtual desktops through the pager? Can you expand on where plasma is involved?
(In reply to David Edmundson from comment #1) > Where does that bug report mention switching virtual desktops through the > pager? > > Can you expand on where plasma is involved? The bug report in the sublime issue tracker does not mention plasma, but the issue that it reports (about not being able to scroll in sublime because x11 received a wrong mouse signal as reported by xev) is triggered every time I switch virtual desktops in KDE through the pager.
Ok, please can you outline steps involving just plasma and xev. I switched desktops and my MotionNotify events have no modifier
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!