I am aware of the switches you can pass to each app to make it use native wayland, but is there any way to do it globally?

  • boredsquirrel
    14·
    13 days ago

    You mean Electron?

    The Arch wiki has docs about that.

    For Flatpaks I use the environment variable

    ELECTRON_OZONE_PLATFORM_HINT=wayland

    See my dotfiles on github.com/boredsquirrel/dotfiles

    Same possible for Qt QT_QPA_PLATFORM=wayland

    • Fisch@discuss.tchncs.deEnglish
      3·
      13 days ago

      Is there a noticeable benefit to those apps running natively on Wayland vs running through xWayland?

      • boredsquirrel
        31·
        12 days ago

        I have not checked this, but as far as I know

        • performance: apps are running on a subset of XOrg and xWayland translates it to Wayland
        • RAM: if you have no XWayland apps anymore you save RAM
        • features: some apps may have more features on XOrg, some may have more on Wayland. OBS on XWayland can record keystrokes, QGis on XWayland has not broken dockable toolbars.
        • Rustmilian@lemmy.worldEnglish
          1·
          12 days ago
          • performance: apps are running on a subset of XOrg and xWayland translates it to Wayland

          “translates it to Wayland” is not correct, XWayland is an X server that runs on Wayland, not a translation layer.

          • RAM: if you have no XWayland apps anymore you save RAM

          True. 👍

          • features: some apps may have more features on XOrg, some may have more on Wayland. OBS on XWayland can record keystrokes, QGis on XWayland has not broken dockable toolbars.

          OBS on Wayland can record keystrokes too, it just that Global hotkeys can be problematic on KDE and requires a work around.

          • boredsquirrel
            1·
            11 days ago

            an X server that runs on Wayland

            So… isnt the X window translated to a Wayland surface?

            • Rustmilian@lemmy.worldEnglish
              2·
              11 days ago

              It does not “translate” or convert X11 windows, but rather forwards them as is over wayland input devices as Wayland surfaces to the underlying Wayland compositor.
              Xwayland server still runs the same code as the regular X server, but relies on the Wayland compositor for presentation and composition of the X11 windows.
              “translation” suggests conversion of X11 API calls or other code, which is not happening here.

              https://wayland.freedesktop.org/xserver.html

  • dinckel@lemmy.world
    8·
    13 days ago

    Depends on your distribution. Arch packages some electron apps in a way, where they can accept their own flags through a dedicated file. For others, it’s just a plain electron-flags.conf in your ~/.config

    I would recommend visiting either the arch wiki, or tour distributions equivalent for details

    Keep in mind that this does not apply to CEF apps, as that’s an entirely different framework

  • hallettj@leminal.spaceEnglish
    6·
    12 days ago

    Probably not directly helpful, but Nix packages for Chromium and Electron apps are set up so that you can switch to native Wayland mode globally by setting an environment variable, NIXOS_OZONE_WL=1

    I don’t know of any global setting that isn’t distro-specific.

  • SteveTech@programming.devEnglish
    5·
    12 days ago

    For electron, if ELECTRON_OZONE_PLATFORM_HINT and electron-flags.conf don’t work, you can also add --ozone-platform-hint=wayland to the end of Exec in each .desktop file (also works on Chromium, but not CEF AFAIK and sometimes CEF).

    There’s also --ozone-platform-hint=auto if you find yourself switching between X11 and Wayland.

      • Björn Tantau@swg-empire.de
        2·
        13 days ago

        Bad is relative. But I have some problems with scaling on a HiDPI display with some Electron apps. I think that might be solved if they were Wayland native.

      • Asyx@lemmy.ml
        1·
        12 days ago

        If you need fractional scaling, they are unusable blurry. Some screens just need fractional scaling so for those setups it’s almost essential to do this.

        You need fractional scaling it your resolution is very high compared to the screen size. So something like a 15 inch 1440p screen would need 150% or 125% scaling because 100% is too small, 200% is too large but with anything in between, xwayland apps are blurry af.

      • Presi300@lemmy.worldOPEnglish
        21·
        13 days ago

        They are kinda choppy, when compared to native Wayland apps and screensharing from an app, running in xwayland doesn’t really work…

      • dinckel@lemmy.world
        1·
        13 days ago

        Define bad.

        If you can run native in wayland, run in native wayland. Your performance will be better, and if you need scaling, scaling is considerably better too

      • thayer@lemmy.caEnglish
        11·
        13 days ago

        Like X11, xwayland is not as secure as a pure Wayland environment but I think it’s important to note that hundreds of thousands of desktop Linux users are likely still running X11.

        So, in my opinion, it is not ideal to run xwayland but still completely acceptable for most users who don’t have special security requirements.

        • Vitaly@feddit.uk
          2·
          13 days ago

          I still run x11 because some of my apps just don’t work on wayland, specifically terminal apps for some reason