133
Where is Linux not working well in your daily usage? Share your pain points as of 2026, so we can respectfully discuss (libretechni.ca)
submitted 8 months ago by to c/linux@programming.dev
149 comments fedilink hide all child comments
 

Thought I'd create a distinct thread from the previous one asking about daily use, because I really do want to hear more on people's pain points. Great to know people are generally sounding pretty positive in those posts who recently switched, but want to know your difficulties as well! This way old and new users can share their thoughts, hopefully to inspire a respectful discussion.

OQB @kiol@discuss.online

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 8 months ago (4 children)

Ok, I was not successful in setting this up. It's not as seamless as rustdesk or anydesk. After installing sunshine, it sorta drops you off on a browser without any instructions. After asking AI, I think I have that setup.

Then moving on into Fedora, I found the flatpak and installed the moonlight installer. Then launched the app and clicked the download, it finishes downloading and does nothing. No new app. No next steps. Just nothing.

So I gave up. I'm trying Remmina and trying RDP. Maybe it will be better, but I don't have high hopes.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 8 months ago* (last edited 8 months ago) (3 children)

    STEP BY STEP SOLUTION

    Using my ArchLinux as a Sunshine server, and Ubuntu as a Moonlight client:

    1. Sunshine devs advise using your Distros package manager ("apt" if on Ubuntu/Debian. AURs "yay" or "paru" if on ArchLinux, or "dns" if on Fedora/CentOS/RHEL), instead of using your Distros AppStore, or either AppImage or Flatpak -- although they may still work.

    2. Run the following on the terminal command line of your Sunshine server:

    sudo setcap cap_sys_admin+p $(readlink -f $(which sunshine))

    1. Restart Sunshine server.

    Then either restart Sunshine by opening on your browser https://localhost:47990/troubleshooting or reboot the whole machine if that doesn't work.

    1. Set username and password for Sunshine here if prompted: https://localhost:47990/
    2. In Moonlight client, click the gear on the top right (settings), then Enable Capture system keyboard shortcuts
    3. Connect to Sunshine using Moonlight client using the 192.168.xxx.xxx IP of your Sunshine server. Running the following on the terminal of your Sunshine server should show your IP: ip addr
    4. Input pin shown from Moonlight into https://localhost:47990/pin webpage of the Sunshine server.
    5. Use CTL + Shift + Alt + Q to escape.

    Extra info / rant, may not be useful

    Again, step 5 is what allows special keys to be ran on the remote host and not the local.

    I just tried Sunshine (remote host) and Moonlight (client). There was a bit more setting up. They mention on their docs somewhere to use your distro's package manager instead of app stores if you can.

    On ArchLinux, I needed to run this in the command line first, and then restart. sudo setcap cap_sys_admin+p $(readlink -f $(which sunshine))

    And then after running Sunshine, and accessing its web console https://localhost:47990/, setting a username and password, to access it via Moonshine on my client by putting my 192.168.xxx.xxx IP, then placing the pin on the Sunshine remote host at https://localhost:47990/pin. And then had 2 "Desktop" icons, 1 to connect with high res and another low res; and then a third icon to connect to "Steam" for Steam Big Picture mode connection.

    Also Moonlight and Sunshine starts with very low brightness. I've fixed this before, by going into the Moonlight or Sunshine settings -- I don't remember which one.

    Although Moonlight and Sunshine does not ask for connection verification after I've connected once. Rustdesk would ask me everytime, and I did not figure out how to remove Rustdesk prompting the remote host to ask the connection.

    And both Moonlight and Rustdesk run the super key on the client host.###

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 8 months ago (2 children)

    Hey man, I got it to work. It's incredibly fast and almost no lag.

    The downside is the hot keys don't transfer to the remote PC.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •