org.chromium.Chromium VS sway

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

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).