Linux

66797 readers

435 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Wayland headless multi seat? (sh.itjust.works)

submitted 6 days ago by muusemuuse@sh.itjust.works to c/linux@lemmy.ml

14 comments fedilink hide all child comments

I'd like to try to get fedora to host a second headless Wayland session in the background for a remote user. I have a GPU but I want to share its render and compute, not the physical HDMI output, so I need a virtual Wayland session for the second seat.

Supposedly logind could handle the seat and udev permission issues clean enough, but headless use is still beyond me there.

I'd like a KDE Plasma environment running headless and then sunshine can just stream this session out using the war capture method. I just don't know how to start up a separate Wayland session under another linux user in the background with a plasma session drawing to an imaginary monitor.

There seem to be 2 ways of doing this.

wlheadless-run - a young project made to solve this particular problem
kwin --virtual can theoretically do this, but I'm not finding clear examples of it

you are viewing a single comment's thread
view the rest of the comments

[–] moonpiedumplings@programming.dev 2 points 6 days ago* (last edited 6 days ago) (1 children)

If you log in (preferably as another user) to another tty (Cntrl + Alt + F2/3/4/5), and then run dbus-run-session startplasma-wayland, does that work?

Sometimes just startplasma-wayland works, which used to work for me but didn't work for me this time.

Then, you should be able to switch back to the original KDE session, which continues to work normally, at least it does for me. Both sessions should have shared access to the GPU, as well. You can then probably run sunshine in that second instance of KDE, while the monitor can be attached to tty1 or tty2, whichever one is the default where KDE is put.

Then, you would probably want to configure sunshine to work even when the screen is locked, that way you can lock the second session with Win + L, but it can still be interacted with remotely via sunshine.

EDIT: I only am somewhat confident that this setup will work, I haven't tested it personally.

[–] muusemuuse@sh.itjust.works 1 points 6 days ago (1 children)

I would need to use the headless backend in kwin, which apparently isn't something you can do from start plasma-wayland but you can do with kwin_wayland --virtual -s waylandR. I can give it a specific socket (waylandR) which lets me point sunshine at that, but I cannot get moonlight to accept a PIN that way. it seems mad about this setup and I'm not sure why.

[–] moonpiedumplings@programming.dev 1 points 6 days ago (1 children)

Do you actually need the headless backend? Or do you need a background session that doesn't interfere with the main session?

[–] muusemuuse@sh.itjust.works 0 points 6 days ago (1 children)

the physical display output is claimed by something else totally separate.

Anyway I did figure out how to the headless backend working, but I did not figure out the udev rules for this headless session

Allows Sunshine to access /dev/uinput

KERNEL=="uinput", SUBSYSTEM=="misc", OPTIONS+="static_node=uinput", GROUP="input", MODE="0660", TAG+="uaccess"

Allows Sunshine to access /dev/uhid

KERNEL=="uhid", GROUP="input", MODE="0660", TAG+="uaccess"

Joypads

KERNEL=="hidraw*", ATTRS{name}=="Sunshine PS5 (virtual) pad*", GROUP="input", MODE="0660", TAG+="uaccess" SUBSYSTEMS=="input", ATTRS{name}=="Sunshine X-Box One (virtual) pad*", GROUP="input", MODE="0660", TAG+="uaccess" SUBSYSTEMS=="input", ATTRS{name}=="Sunshine gamepad (virtual) motion sensors*", GROUP="input", MODE="0660", TAG+="uaccess" SUBSYSTEMS=="input", ATTRS{name}=="Sunshine Nintendo (virtual) pad*", GROUP="input", MODE="0660", TAG+="uaccess" SUBSYSTEMS=="input", ATTRS{name}=="Sunshine PS5 (virtual) pad*", GROUP="input", MODE="0660", TAG+="uaccess"

this is....not enough

[–] moonpiedumplings@programming.dev 1 points 6 days ago* (last edited 6 days ago)

the physical display output is claimed by something else totally separate.

Yes, and the above solution I laid out is a way to get around that, that potentially dodges the complexity of configuring a headless session. It's possible to run two KDE sessions at once, next to eachother, and then simply put one on the main display, with the second being "headless", and not shown.

I started fiddling with the above setup I described, actually installing and testing sunshine. Unfortunately I hit some hiccups. I got sunshine to run, but with no input, and then then it attached to the wrong KDE, even though it was streaming the correct one initially. Now I'm running the same KDE session as a different user (since I was on the same user before), but having pairing issues, but I suspect these are because moonlight is seeing the wrong SSL cert, since the sunshine as a new user generated a new cert.