I see. maybe they are trying to be wayland compatible but failing at it? I have written some relevant advice here: https://sh.itjust.works/comment/21809713

libinput is a major component in that area. you should ask around here: https://gitlab.freedesktop.org/libinput/libinput also have a look at the existing open/closed issues

they should just work under wayland without supporting it. what’s the problem with them?

aren’t there better ways for that in most window managers?

but that’s already a thing!

ok, on kde, no idea about others

why do you want to hide the window from the user in such a bizarre way? what’s the purpose?

The app didn’t seem to respect the environment variable for X11 I tried to set for that one app.

that should only matter if it would run in wayland mode and you want to override it to run in x11 mode.
though, maybe omnissa tries to use wayland mode, but does that very poorly, and in that case you would actually want to override this.
there’s multiple ways to disable wayland for an app (actually what you do is convince the app to not use wayland), and it depends on the framework the app uses. but setting the environment variable WAYLAND_DISPLAY= (like this, to the empty value) should work, as lots of apps look for that to know if they should use wayland.

usually you set the environment variables for an app in its own launcher icon’s editor menu. there’s other ways too but this does not require using the terminal.

I have an odd monitor configuration, one 2k high refresh rate, HDR monitor in the center, 1080p monitors to the left, right, and above. The right is also a higher refresh rate.

I could get it to work in Ubuntu… inconsistently. Sometimes I’d log in and have one 640x480 monitor in the center. PopOS just worked.

yeah that’s a bit complicated. but I would expect kde plasma to handle it well. it has a display config menu a bit like windows has, where you can drag each display to where it should be. be aware though that it does not affect the user selector screen that you see between a fresh boot and the first login; that’s configurable too but in a different way.

I have so many questions, but it’s ok if you dont want or can’t answer them. why doesn’t omnissa work in wayland? X11-only apps are still supposed to work (because of a compatibility layer xwayland), and I take advantage of that all the time with multiple apps. and why don’t your monitors work? hdmi/dp/dvi are all very basic things that should just work, regardless of using X11 or not

that’s weird. does that not work in the browser either?

all 16 777 216 colors, actually

maybe the snapshot could be rolled back by a PXE bootable system. but for the second part, btrfs can do snapshots per subvolume, so if you could create a subvolume on user creation that could work

Btrfs and snapshots could help with atomicity, did you consider that?

do as I say

look babe, it’s a unique 8 point curve for each fan, isn’t that beautiful! do you hear it too?

Also that right click menu is lighters faster than the old school menu. Every application and their mother wants to add shit to the right click menu and it would lag out to the point it would take 10 seconds to open.

if you don’t install all the garbage of the internet, that’s not a problem. it can also be cleaned up, even without regedit.

windows 11

oh… now I understand everything

why would anyone else use your computer? honest question. and do they need access to your local files, or just a machine?

no I mean piping a downloaded script to the interpreter

that sounds horrible.

only of manual duplex printing would be a thing on linux…