Bug 470839

Summary:	Android to linux kdeConnect not sending remote cursor input
Product:	[Applications] kdeconnect	Reporter:	marioedwards45 <marioedwards45>
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andrew.g.r.holmes, cwo.kde, plata.hill
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Android 10.x
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description marioedwards45@gmail.com 2023-06-09 17:11:45 UTC

So Ive used kdeConnect on my windows 10 machine for a while as a track pad but when i tried to do the same on linux(Fedora 38) it doesn't want to work i got the popup asking for conformation to enable remote input and i enabled it 


SOFTWARE/OS VERSIONS
Windows: 
Android:
Linux(Fedora38):

Comment 1 Ben Bonacci 2023-06-10 09:37:05 UTC

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

Comment 2 Plata 2024-05-15 17:30:27 UTC

Is this a specific problem with Android? If not, probably the same as:
- https://bugs.kde.org/show_bug.cgi?id=471258
- https://bugs.kde.org/show_bug.cgi?id=471959

Comment 3 cwo 2024-08-04 22:09:23 UTC

Thank you for the bug report! There are several open issues regarding the remote input function not working from a mobile device to a pc running Wayland.

I suspect that the cause for these is the same, namely that the permissions dialog is not shown. On Wayland, explicit permission is required to allow such security-relevant features to work.

If you still experience trouble using remote input in this setup, please try manually restarting kdeconnectd by running "kdeconnectd --replace" in a terminal, then use the remote input function again and see if you get a permissions popup now.

I'm marking all the open bugs regarding this as a duplicate of the newest one, as it has the clearest technical reasoning. If you think that you are affected by a different underlying issue, please comment on this bug again. Thanks!

*** This bug has been marked as a duplicate of bug 489058 ***