cage VS xpadneo

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?

In the other distros I've tried (ubuntu / pop os) I usually solve the problem by installing xpadneo using the official method that can be found here. But this doesn't seem to be working in this case. I've already tried using gnome bluetooth settings, blueman and bluetoothctl.

That was more than a year ago though and it seems some people are working on linux drivers. xpadneo is probably a good starting point: https://github.com/atar-axis/xpadneo

If that doesn't work either, I would try making an issue on their github and asking there: https://github.com/atar-axis/xpadneo/issues

2) install https://github.com/atar-axis/xpadneo

This very same controller has worked on this very same physical computer in the past, but under Ubuntu using the xpadneo driver (https://github.com/atar-axis/xpadneo/). One day, for no reason as near as I can tell, it simply stopped working and showed the exact same symptoms as above (controller works for phone, not for PC, doesn't show up in bluetooth list. Other bluetooth devices work fine with the PC). This triggered my distro-hop to Endeavour just to discover the exact same issue.

You can try this custom mapping from xpadneo: https://github.com/atar-axis/xpadneo/blob/master/docs/SDL.md