Install x2go on the client machine. You need X and SSH on the target machine. That’s it, when you connect it will open a new desktop session on the server.
If you want to connect to an existing desktop session you need x2godesktopsharing installed on the target, you need to activate sharing in x2godesktopsharing, and in x2go client you need to select “session type” as “X2Go/X11 desktop sharing”.
Many modern laptops no longer support S3 sleep at all. It is likely to be an issue with the bios rather than a linux project. On my laptop, with Ryzen 7 5825U, I had to give up on S3 and use s2idle. Also had to pass "pcie_aspm=off" as a kernel parameter because it would take ages to wake the ssd without it. Overall works ok. Not as good as S3 but better than nothing.
So to check what suspend states your laptop supports run cat /sys/power/mem_sleep. It should print something like s2idle shallow [deep] with the option that is enabled having [] around it. To change the enabled option run echo "s2idle" > /sys/power/mem_sleep. https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate has more info.
I haven't really noticed much of a difference. I figured it was probably worth actually being able to wake the laptop from sleep rather than having to restart it every time.
Maybe you can set up a KWin window rule to force Latte to be where you want it to be?
Not that Plasma panels work that much better than Latte in that regard, they still sometimes shift monitors just because something is plugged in (not even enabled, just plugged in!)
I really wish we could pin things to the exact monitor via its physical port location or serial number or something from EDID.
Thanks for the suggestion. This does work. You can force the dock to a specific screen, but then it doesn’t autohide (dodge) as it still thinks the other random screen is the primary and only triggers off that. Still, this may be the answer if nobody can suggest an alternative.
You are probably gonna want to chroot into your laptop using a livecd for linux. This will allow you to basically access your terminal without being able to login or boot, and then you can uninstall Nimdow, or turn off auto-login.
The best way used to be XPRA. You can also tunnel it thru SSH, but not necessary in a trusted LAN. XPRA is like a per application display proxy that keeps an app running even if the connection is interrupted and enables reconnects as well as transfers of Xclient windows to other Xservers, i.e. you can transfer the remote window from your notebook to your workstation Xserver whithout having to restart the app.
While transition to Thumbleweed can go smooth if you are lucky enugh, switch from Thumbleweed to Slowroll can be problematic. It will envolve downgrading packages that is usually not tested at all. Better switch from Leap to Slowroll directly.
Also I see “Red Hat” thrown around a lot. There’s no Red Hat anymore, it’s IBM, and IBM’s target user is a RHEL customer.
I’m willing to bet most people commenting on Mastodon (and here for that matter) have very little in common with a RHEL customer. IBM, like Valve with the Deck, have very specific use cases in mind and can afford to support a Wayland-based desktop for those particular circumstances.
But does IBM care about the desktop needs of the average Linux user? I doubt it.
Great point. IBM has a long history of squeezing every penny from their customers. At one corner job, IBM had to come onsite a few times a year to perform system updates. We were not allowed by IBM to upgrade the OS ourselves.
I think you can mount network shares with the Kerberos token you got from AD. Sometimes just the user credentials suffice. At least that’s how it used to be when I last tried something like that years ago.
I guess WSL is best way, but I think you’ll only be able to have the Linux windows like windows windows in the taskbar of windows and launch them with windows
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.