SUMMARY Mouse Input Gets Blocked After Try A Drag & Drop Event Under Wayland STEPS TO REPRODUCE 1. Login to a Wayland session. 2. Launch a program (e.g. Firefox). 3. Try to do a drag & drop to reorder any tab. 4. After figure out you can't drop the tab, press Escape key to leave it where it was initially. 5. Try to do click, right click, mousewheel scroll, etc. OBSERVED RESULT You can't do more than move the cursor, (tested with KDE Connect Virtual Remote Mouse & with a hardware/real mouse). EXPECTED RESULT Can use the mouse input (clicks, right clicks, mousewheel scroll) normally, like you can before trying to do the drag & drop event. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.3/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION
Update of status after the update to Plasma 5.19, the bug is still reproducible under web browsers using GTK (I tested it on Firefox & Brave), but it's not occurring on Telegram Desktop, Plasma, etc. But, strangely, due to this (I assume), I can't add the widget of Global Menu to Latte Dock under Wayland, now this widget works finally under Wayland session :(. It just doesn't even show Latte Dock, but thinking that behavior could be because the lack of Wayland support for the Dock, I just left it on "Always Visible", tried again and I can't interact with it, when I try to left click to drop the widget on it, it just doesn't respond, I have to press Esc key to get out of the stuck. Writing this, I'm thinking, maybe there're 2 different bugs here? One from the part of Latte Dock with Wayland compatibility and the other one, the one which I reported originally here or even another one? Please, I would thank very much if someone could throw some light to this bug. Thank you very much in advance.
OK, I can update this "issue" and tell that it's a KDE Connect Virtual Input Mouse issue. At least, it's the only way I can reproduce it, with a hardware keyboard or touchpad, I haven't been able, so there wasn't a bug really, I suppose. Sorry for the disturbances.