Bug 471258

Summary:	Remote input function doesn't work
Product:	[Applications] kdeconnect	Reporter:	vyamak
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andrew.g.r.holmes, cwo.kde, dashonwwIII, matithomas, plata.hill, rwb
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description vyamak 2023-06-20 06:23:43 UTC

STEPS TO REPRODUCE
1. download kde connect 1.26.0 from play market
2. connect to the manjaro pc with kde
3. in remote input menu move finger on the screen and tap on clicks buttons

OBSERVED RESULT
nothing happens


EXPECTED RESULT
the cursor will move and click


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Android version: 10
Graphics Platform: Wayland
Processor: Intel Xeon E5-2420
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

Comment 1 Plata 2024-05-15 17:32:04 UTC

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

Comment 2 Plata 2024-05-15 17:33:36 UTC

While the original bug report is for Manjaro, it happens also on e.g. Ubuntu or Fedora.

Comment 3 cwo 2024-08-04 22:09:18 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 ***