org.chromium.Chromium VS wlroots

Seems like it's a buggy wayland fractional scalling implementation... It's reverted in the chromium flatpak https://github.com/flathub/org.chromium.Chromium/commit/eea7af903decb3a3b9bb6fdacbb55d24a90e18f3

My philosophy has been to let the distro package manager handle system packages (kernel, OpenSSL, etc) but then use flatpak [1] to install user progs like Chromium and VSCode so I get bleeding edge releases and sandboxing.

[1] https://flathub.org/apps/details/org.chromium.Chromium

If it helps I'm using https://flathub.org/apps/details/org.chromium.Chromium along with https://flathub.org/apps/details/com.github.tchx84.Flatseal

You can inspect how Chromium is built on Flatpak here: https://github.com/flathub/org.chromium.Chromium

Oh that doesn't work? Hmm I wonder if you could try the executable listed at https://flathub.org/apps/details/org.chromium.Chromium and put that in your config?

No need to trust anything, unlike snaps, the way they're distributed is public and open source: https://github.com/flathub/org.chromium.Chromium

Would a workaround be installing chromium from flathub, and using that for browsing? https://flathub.org/apps/details/org.chromium.Chromium

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.

gamescope use wlroots