35
Did Fedora 40 break something for you?
(gehirneimer.de)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
There's a GNOME extension GSConnect that uses the KDE Connect backend if you're on GNOME. I haven't used it in awhile since switching to KDE, but it worked well when I used it.
As far as KDE's documentation says though, you should be able to use it on any DE. What exactly is the problem you're experiencing? Will it not start, will it not connect (if so try re-pairing), or is there functionality that is missing?
It says it requires kde desktop but the cli works so i set it to autostart on hyprland. One thing tho is i cant type from the app but i got sunshine for that
The remote input issue is related to Wayland, and currently all wlroots based compositors (including Hyperland) have issues with this. KDE Plasma has merged support for remote input to work with KDE Connect, however many other DEs do not have the support merged, and will have to rely on xdg-desktop-portal-wlr to implement it. Here are the related bug reports and issues:
https://bugs.kde.org/show_bug.cgi?id=448604
https://github.com/emersion/xdg-desktop-portal-wlr/issues/2
https://github.com/hyprwm/Hyprland/issues/1775
Also, it seems the other issue is unrelated, are you seeing an error on the command line, or is there a dialog popup, and can you quote what is said? I'm having trouble finding any related issues anywhere on GitHub, even the Hyperland issues around remote desktop did not seem to have this particular error (or didn't mention it at least).