Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoteDesktop: KDE connect doesn't work #15

Open
Quackdoc opened this issue Nov 13, 2023 · 4 comments
Open

RemoteDesktop: KDE connect doesn't work #15

Quackdoc opened this issue Nov 13, 2023 · 4 comments

Comments

@Quackdoc
Copy link

KDE connect uses the remotedesktop portal for mouse and keyboard input. It fails with the below output

kdeconnect.plugin.mousepad: Unable to handle remote input. RemoteDesktop portal not authenticated
kdeconnect.plugin.mousepad: authenticating "/org/freedesktop/portal/desktop/request/1_3353/kdeconnect3112798555"
kdeconnect.plugin.mousepad: configuring "/org/freedesktop/portal/desktop/request/1_3353/kdeconnect2341811113"
@Decodetalkers
Copy link
Collaborator

I cannot find out what is wrong.. so have you help solve the problem?

@Enovale
Copy link

Enovale commented Jun 4, 2024

I was getting this as well until I forced the RemoteDesktop interface to use Luminous instead of Hyprland. now it gives me the slurp selector over my screen, but when I select a monitor nothing changes. no errors are thrown in kdeconnect when I try to move the mouse but nothing actually happens when I move the mouse or use the keyboard input.

@Quackdoc
Copy link
Author

Quackdoc commented Jun 4, 2024

I completely forgot about this issue until I just received this reply. I had done some preliminary investigation back when I reported the issue. I believe that the problem is that with Luminous, the video session is mandatory?

It has been a really long time since I checked, so I might be wrong. But I believe the issue is it tries to start a pipewire or GStream and that fails and when it fails the protocol times out.

Kdeconnect does not use the video part at all, so I believe it is related. The other possibility I considered was that instead of getting user to select and then start the protocol, the protocol should be started right away. It could be that it's timing out while it's waiting for the user to select a display.

EDIT: written with voice to text so pardon any inconsistencies I missed

@Decodetalkers Decodetalkers pinned this issue Oct 17, 2024
@Decodetalkers
Copy link
Collaborator

Decodetalkers commented Oct 17, 2024

Ok,, it works now, but there is some problems about remote... how to know that the remote need to control screen? and also problems about the keyboard..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants