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
The app didn’t seem to respect the environment variable for X11 I tried to set for that one app.
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.
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.
Why are people ratioing this purely subjective take? I’ve had builds that didn’t get along with various peripherals. That’s like a super common refrain from people with a great many distros.
My Logitech F710 never worked right with Windows because the driver’s power saving feature doesn’t mesh well with Windows 10’s power saving feature, causing dropped inputs. No such problems under Linux.
Not everything works everywhere. People are used to how things don’t work with Windows and learning how things don’t work differently with a Linux distro is annoying because you learn by running into problems. If you have people to switch over and have a good time you have to help than through this.
I’d rather use x11 than windows. But you do you.
Yeah, my monitors didn’t work under Ubuntu X11. At least on PopOS, that just worked.
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
The app didn’t seem to respect the environment variable for X11 I tried to set for that one app.
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.
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.
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.
Why are people ratioing this purely subjective take? I’ve had builds that didn’t get along with various peripherals. That’s like a super common refrain from people with a great many distros.
Heck, that can even happen with Windows.
My Logitech F710 never worked right with Windows because the driver’s power saving feature doesn’t mesh well with Windows 10’s power saving feature, causing dropped inputs. No such problems under Linux.
Not everything works everywhere. People are used to how things don’t work with Windows and learning how things don’t work differently with a Linux distro is annoying because you learn by running into problems. If you have people to switch over and have a good time you have to help than through this.