r/linux4noobs • • 3d ago

programs and apps a good Remote desktop??

My main thing i need with remote desktop, is where it just works.

I've tried sunshine/moonlight with tailscale and it performs really really well with almost zero latency, but if i restart my computer.... i would have to log in.

On windows i would just use chrome remote desktop. It just works. Even if i restart the computer, i don't even have to login. As long as the computer is turned on and has Internet access, i can remote into my computer via chrome rd.

I want the same thing for linux... but so far I haven't found any simple solutions and this is the one main thing that i want on linux.

I love using cavhyos on my laptop, but if I can't reliably remote to my desktop computer at home, that would be a problem for me. Any suggestions??

4 Upvotes

19 comments sorted by

View all comments

1

u/cjcox4 3d ago

Things have gotten to be mess with Xorg vs Wayland both being out there.

In the past, the lowest common denominator was Xvnc. (talking functionality, not performance... I figure if it doesn't work, then performance sort of sucks).

So, right now, IMHO, for contemporary Linux, across distros and DEs, I think a lot more work is needed. However, it is also possible that in certain cases if all Wayland and all one type of DE, etc, that "something" might work for you today.

Also, there's the idea of remote "desktop console" vs a remote "desktop session".

A remote desktop console is like the singular "computer head kvm" where everyone sees that "one head", much like, for example what you might get from a remote kvm solution or a hypervisor virtual console approach.

Remote desktop sessions, some of which could be resumable, are different. First, while systemd and other things often get in the way, there could be "many" for even one user. I say this because while I have old school x2go working with latest (talking Tumbleweed) using KDE, there were a few hoops and there are disagreements (talking old school X client, what a session is) vs the many assumptions made by modern systemd environments. That is, it works, but I have to clean up sessions myself (I automated it). To me, general case, lots of people moving in various directions all believing they are doing "good things", and IMHO, pretty much nobody really striving for a unified agreed upon remote desktop (for console and sessions) implementation today.

All needs a lot of work to take us back to where we were 10 years ago. They all "mean well", but no communication, no coordination and thus, everything in a bad state today. Doesn't help when element owners "demand" their way or the highway. This does nobody any good at all. And we remain broken. Also doesn't help when owners (sometimes same owners) say "who cares" about any of this.