I am running Fedora 39 right now and the last time I did a distro upgrade my graphics drivers were a huge PITA. Did your upgrade to 40 went smooth?

  • Para_lyzed
    1•8 months ago

    You can install sunshine on Fedora 40 with their COPR repo. Their GitHub releases lag behind on OS releases, but the COPR is automatically configured for new versions of Fedora since it doesn’t rely on compiling in a Docker container. Haven’t tried it myself, but it was recommended on their issues page.

      • Para_lyzed
        1•8 months ago

        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?

        • @[email protected]
          1•8 months ago

          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

          • Para_lyzed
            1•8 months ago

            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).