cage VS sway

You... might be able to, kind of, depending on your goal... So the thing is, if all you need is a single screen (or at least, I've not run this multi-monitor) and you're just working around drivers that don't support Xorg, you can just run cage ( https://github.com/cage-kiosk/cage ), run xwayland on that, and run your real GUI on that. Of course, then you're skipping all the advantages of wayland except hardware/driver compatibility.

For "real" wayland, sibling comments are correct that you'd need a wayland compositor that reimplemented awesome.

> As a developer, I needed to port a custom Linux system to hardware that only has Wayland drivers and it was a giant pain. Wayland offers no advantage at all for that system but it broke a lot of functionality that relied on X in terms of window placement, etc.

FWIW, I've had decent luck running cage ( https://www.hjdskes.nl/projects/cage/ ), then on that xwayland, and then just ignoring wayland and running X clients. The result does still have some slight quirks, but it mostly works fine.

That did help me find https://github.com/cage-kiosk/cage/wiki initially I'm here there's other going down that path. Thanks

I thought this was going to be some development news with Wayland compositing going further: https://emacsconf.org/2022/talks/wayland/. Maybe it's because 29.1 was on my mind with the full Wayland client support being released.

If you want to just run one application in a modern way (yes, I'm assuming you agree that Wayland is desirable), then check out https://www.hjdskes.nl/projects/cage/.

You can run Wayland inside Xorg via cage[1] so you don't need to use a Wayland compositor.

[1]: https://github.com/cage-kiosk/cage

Just ran into cage, seems useful.

It's kiosk mode. Sometimes related to POS. You can use https://github.com/cage-kiosk/cage (Wayland) for example.

Maybe starting with reimplementing something like this: https://github.com/cage-kiosk/cage would be the easiest?

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).