• 0 Posts
  • 103 Comments
Joined 3 years ago
cake
Cake day: July 11th, 2023

help-circle





  • openSUSE Tumbleweed

    tumbleweed is like that though. there’s a cost to immediately getting all the updates: you are supposed to be testing it and reporting problems you find. if you don’t want that that’s fair, me neither, that’s why I don’t run tumbleweed. I never understood the people saying they never have problems.

    but please don’t write this down as “the linux experience”

    if leap is too slow for you, you could try fedora kde edition, so far it seems pretty stable. but maybe you could continue with tumbleweed after setting up automatic snapshots before update installation. if your rootfs is BTRFS it shouldn’t be hard.

    Well, I learned earlier this year that if my system is booting normally and able to play games (all I really care about to be honest),

    I don’t think you need tumbleweed. do you run steam as a flatpak package? if so then its updates and for wine/proton they arrive quickly, I think you would be fine with leap.

    So, I just wanted to know what everyone else feels about updating their systems, especially if you have a similar use case like mine. :/

    where I use opensuse leap, I fear the major version updates, but I don’t know why because I always read the release notes, and I don’t think I had major issues yet.

    where I use fedora kde, I just let it do it itself. these are not my primary systems (yet), so if something breaks then its not that much of a pain, but no problems so far. it already supports the update install method that installs all of them after a reboot, and that’s what I use,














  • 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