Bug 412247 - When I use external input via kde connect from my android phone, the cursor is controllable on my main monitor, but if I move the cursor with the kde app to the second monitor, the cursor just flies to the far right border
Summary: When I use external input via kde connect from my android phone, the cursor i...
Status: RESOLVED DUPLICATE of bug 399523
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmamobile-application (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Nicolas Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-23 16:26 UTC by andreas.persson
Modified: 2019-09-23 19:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
screencapture of bug, cursor uncontrollable on second monitor with kde connect (1.24 MB, video/mp4)
2019-09-23 16:26 UTC, andreas.persson 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description andreas.persson 2019-09-23 16:26:46 UTC 
Created attachment 122822 [details]
screencapture of bug, cursor uncontrollable on second monitor with kde connect

SUMMARY
When I use external input via kde connect from my android phone, the cursor is controllable on my main monitor, but if I move the cursor with the kde app to the second monitor, the cursor just flies to the far right border and cannot be controlled until I manually drag the cursor with my corsair mouse to the main monitor.

Controlling the cursor on my second monitor with kde connect is therefore impossible. I recorded a video so you can see it.

This does not happen with kde connect on gnome 3 or other DEs, this only happen on KDE.

I have nvidia driver, and the gpu 1650

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nicolas Fella 2019-09-23 19:24:55 UTC 
*** This bug has been marked as a duplicate of bug 399523 ***