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

help-circle
  • 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


















  • does retrains have any effect with hard? this is what man nfs says:

    If neither option is specified (or if the hard option is specified), NFS requests are retried indefinitely. If the soft option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return an error to the calling application.

    also, do you know what can I do with CIFS/SMB? I have most of my shares through samba :/


  • well that’s also interesting, but I mainly experience this problem on my desktop. there was a plasma version when even the taskbar panel got frozen, and the kde file manager, double commander too for like a minute, every time they try to do anything with an unreachable network drive. and its even worse on my laptop so there I just don’t mount my shares anymore.

    I have been wondering how does windows do it, and programs made for windows, because this is a nonissue there (though windows has its fair share of problems with network shares though…). maybe they just learned to do all IO ops on a different thread…