Bug 477245

Summary:	Under Wayland, remote input from KDE-Connect is not recognized by a Smartone.
Product:	[Applications] kdeconnect	Reporter:	Trinity <Sy-Klone>
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andrew.g.r.holmes, cwo.kde
Priority:	NOR
Version First Reported In:	23.08.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Trinity 2023-11-19 18:31:02 UTC

For about 4-6 weeks, all of the functions of KDE-Connect no longer work on my smartphone, a OnePlus8Pro with LineageOS 20.0 under Wayland.
Remote input via the OnePlus8Pro smartphone does not work under Wayland, but it does under X11.
So I can't use the mouse pointer over the smartphone display, but the laser pointer works on Wayland.
We use KDE-Connect to control video playback on a TV that is connected to the laptop via HDMI.


1. Start KDE Plasma under Wayland
2. Connect smartphone to PC via KDE-Connect.
3. In KDE-Connect, select "Remote input" in the menu (middle right)
= The mouse cursor cannot be controlled with Wayland over it.

Informationen:

Linux: EndeavourOS
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Linux-Kernel: 6.6.1-arch1-1 (64-bit)
Graphics Platform: Wayland

More information:

The following packages are installed:

kdeconnect 23.08.3-1
wayland 1.22.0-1
plasma-wayland-session 5.27.9.1-3
kwayland-integration 5.27.9-1
xorg-xwayland 23.2.2-1
mesa 1:23.2.1-2

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