@jac Hey, thanks for sharing!

They have a lot of useful information.

cc mostly in case if you find it useful @Max_P wayland headless https://games-on-whales.github.io/wolf/stable/dev/wayland.html

https://games-on-whales.github.io/gow/monitor.html#_force_xorg_to_use_a_custom_edid

And a mention of custom EDID for a monitor to be registered huh . Guess I’ll follow up on this as well eventually, less work setting things up and more things to learn.

@Max_P Anyhow I think I should be good. That was all super interesting looking at the freedesktop documentation it does answer some things I was wondering about myself.

Now I don’t think I feel in the mood to toy with creating my own display manager, maybe as a pet project but man I can’t imagine anyone new be like “so there’s a centralized documentation/communication channel for all of this, right?” 😆

@Max_P Just to pick your brain and sorry for asking so many questions but what if from what you said nested compositors/clients/etc I could just create a separate virtual screen and have WAYLAND_DISPLAY=wayland-1 (or 0:1) wouldn’t I be technically be able to capture that and project it for my needs?

I guess I’m just jumbling/reorganizing my mind with this new information. I feel like the question would be “can I create a virtual monitor within a parent session?”

Anyhow, thanks again!

@Max_P That looks amazingly promising regardless. I’m still bummed and a bit confused on the one shared GPU business I thought it wouldn’t matter if you ran multiple graphical applications regardless or is this imposed by Wayland at the moment? If not wayland would X11 do the same?

Just throwing questions more out of curiosity.

How… do you find all these pieces to glue together? Who or what is putting these out there “hey I want to initiate an desktop env”

Thank you!!