Bug 399523

Summary:	Cannot move mouse cursor from edge of display with kdeconnect remote control other than primary display when more than one monitors are connected
Product:	[Applications] kdeconnect	Reporter:	maximilianproell
Component:	plasmoid	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	CONFIRMED ---
Severity:	normal	CC:	andreas.persson, andrej, cshjsc, flokol120, g.guerin, maximilianproell, MilciaQ1610, simon, unfold1911, yoyotax
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description maximilianproell 2018-10-08 18:55:20 UTC

If more than two monitors are connected, I am unable to move the mouse from the left edge of the screen. Only movements in Y-direction are possible.


STEPS TO REPRODUCE
1. Connect smartphone with computer with more than two monitors via kdeconnect
2. Go to remote control
3. Try to move mouse to the right.

OBSERVED RESULT
Mouse cursor does't move to the right.

EXPECTED RESULT
Mouse cursor should move to the right.


SOFTWARE VERSIONS
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

Comment 1 maximilianproell 2018-10-08 23:55:51 UTC

EDIT:
Mouse control only works on primary display. If mouse is moved to other than primary display, mouse will clip to an edge and can't be moved anymore.

Comment 2 Nicolas Fella 2019-09-23 19:24:45 UTC

*** Bug 410505 has been marked as a duplicate of this bug. ***

Comment 3 Nicolas Fella 2019-09-23 19:24:55 UTC

*** Bug 412247 has been marked as a duplicate of this bug. ***

Comment 4 Nicolas Fella 2020-04-12 15:44:33 UTC

*** Bug 417577 has been marked as a duplicate of this bug. ***

Comment 5 Simon Redman 2020-06-04 16:48:42 UTC

On one of the linked duplicates (417577), Neil Moore posted this which does look like it might be causing the problem:

I've run into this as well, there's an upstream Qt bug (https://bugreports.qt.io/browse/QTBUG-55038) that KDEConnect runs into.

Presumably, the current work to use org.freedesktop.portal.RemoteDesktop as the remote input backend will fix this entirely but that work isn't done yet.

Comment 6 Nicolas Fella 2021-03-18 23:24:23 UTC

*** Bug 402246 has been marked as a duplicate of this bug. ***

Comment 7 Ivan Ivanov 2021-03-24 19:13:56 UTC

This bug also affects me. Sadly no progress observed since 2018.

Comment 8 J 2021-07-12 13:40:46 UTC

Same bug happens to me too :(

Comment 9 Gauthier 2021-12-13 15:29:21 UTC

This bug is still present with KDEConnect 21.12.0 (on desktop) / 1.18.1 (Android)

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
Kernel Version: 5.11.9-051109-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620