2026-11-07 05:10 UTC
Replies (9)
-
@jbloggs777@discuss.tchncs.de 2026-11-07 05:48
wiki.archlinux.org/title/Multiseat It sounds like you need a second video card, rather than two monitors plugged into the one card.
-
@luthis@lemmy.nz 2026-11-07 05:50
I assumed this was possible, would be very handy for having multiple sessions running
-
@Kajika@lemmy.ml 2026-11-07 08:30
It is possible, but it is not a wayland limitation per-say but a compositor one (aka the wayland server), and I say “limitation” if the compositor doesn’t have multi-display option. Technically wayland is not the issue: If you look at your /run/user/[uisd] (uid is probably 1000) you will see the wayland “displays” (socket here), usually named wayland-X. The /run[…] is usually set from $XDG_RUNTIME_DIR while the wayland socket to be used is set in the environment variable $WAYLAND_DISPLAY. So running an application in a 2nd session would just require setting the $WAYLAND_DISPLAY to an other value (that exists). It seems that Sway is able to do this with the output command.
-
@umbrella@lemmy.ml 2026-11-07 16:51
comment to watch the thread
-
@vole@lemmy.world 2026-11-07 20:51
If you have an integrated GPU and discrete GPU, or if you buy a cheap GPU, you can multi-seat. That’s the enlightened path. There’s also this: blinry.org/multi-seat-wayland/
-
@markstos@lemmy.world 2026-11-07 22:25
You can do it but using a junk second computer with no hard drive, a slow CPU and little memory. This is the thin-client concept and it has been in use going all the way back to mainframes. It lost popularity when personal computers- PCs- got cheap. Works like this: The thin client BIOS is set to boot over the network. It locates your desktop, downloads a small OS and displays a login, to your remote desktop. From there, it’s passing through the keyboard and mouse input to remote server and displaying the output. The real CPU work is all handled by the server. The whole Edubuntu distro was built around this design. You could have one decent computer in a school computer lap and 20 crappy thin clients and everything would feel pretty snappy and work pretty well. Cheap and low maintenance to admin with only one hard drive / distro to maintain!
-
@Damage@feddit.it 2026-11-08 00:37
On kde you just click “switch user”, log into the new session and then use Ctrl+shift+F#, much like X11
-
@bluemite@lemmy.world 2026-11-08 01:22
I had a set up like this about 15 years ago on my system, but haven’t looked at the options recently. It looks like it is supported. See here: wiki.archlinux.org/title/Multiseat
-
@muusemuuse@sh.itjust.works 2026-11-09 03:44
If you have only one GPU you cant*. If you have two, you can make each its own seat. *xvfb to create a second seat, make a headless session, stream it to a cheap weak thing connected to that other monitor. Cheaper than a second GPU.