Bug 485109

Summary:	On Wayland, starting a drag&drop using remote input then clicking with the mouse can leave the pointer stuck in a dragging state
Product:	[Applications] kdeconnect	Reporter:	Antti Savolainen <antti.savo>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	CONFIRMED ---
Severity:	normal	CC:	andrew.g.r.holmes, cwo.kde, fvalasiad, madness742
Priority:	NOR	Keywords:	wayland-only
Version First Reported In:	24.02.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Antti Savolainen 2024-04-05 23:00:04 UTC

SUMMARY
Demonstrative video: https://youtu.be/0c5M77MwjYo
If I create a KDE Connect connection between my PC and phone and then use remote input to drag a firefox browser tab, mouse becomes unusable. I'm fully reliant on keyboard input from that point forward

STEPS TO REPRODUCE
1. Create a connection between PC and phone
2. Use remote input from the phone
3. Drag a browser tab

OBSERVED RESULT
Mouse becomes stuck

EXPECTED RESULT
The tab should be dragged as normal

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

Comment 1 cwo 2024-08-04 19:15:03 UTC

I was able to reproduce this on git master (both Plasma and KDE Connect) on Wayland. I have not been able to trigger the bug on X11, so I suspect it is Wayland-only.

It works correctly if the user starts to drag, then completes it by tapping the screen. If the user moves to the regular mouse (or pointing stick in my case) and clicks while the dragging operation is still active, the pointer becomes stuck in the dragging state and neither clicking on the computer nor tapping on the mobile device will help it get unstuck. Moving the pointer in this state over the panel will move the widgets there, so plasmashell still registers the pointer as being in the dragging state. It does not actually need to be a Firefox tab; I've also tried it with a task manager icon and that triggers the bug as well.

While clicking/tapping and other mouse operations on either the computer or the mobile device do not get the cursor out of this state, the escape key seems to work, and regular operation is possible again after pressing it.

Comment 2 Fotios Valasiadis 2024-08-31 02:07:29 UTC

I am also experiencing this, here is my kinfo:

Operating System: TUXEDO OS 3
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-101041-tuxedo (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics