Is there an unannounced hard System-d + Wayland dependency?

[Slatepaws]

For the past day i have been tearing my hair out trying to get Fex to run. I got it installed, got the rootfs mounted via the standard squashfs kernel system using this.
/usr/share/fex-emu-rootfs-layers/gentoo/images/00-base.sqfs /usr/share/fex-emu/RootFS/Gentoo squashfs defaults
from: chadmed/asahi-overlay#155 (comment)

FEXConfig launches, set that to rootfs. but that's all that works.

but FEXServer just doesn't seem to work. No matter the options launched with other than -h or -v results in no output, not even errors. All the other commands just spit the error out from issue #4483
By all your documentation it's just a standard daemon. Or does it 'expect' to have the windows-lite system-d to be installed?
Edit: no the described fixes in the issue do not work. muvm flat out panics and crashes.

[Sonicadvance1]

Definitely no wayland dependency in FEX, I don't use Wayland on any of my Arm64 machines. It's Asahi that strongly encourages wayland.

FEXServer is a daemon and will exit if there aren't any FEX instances connected to it. In the same vein if FEX is started and there isn't a FEXServer running, then it'll start one in the background.

If you really want FEXServer in the foreground then you can start it with FEXServer -f -p and it'll stay open in a terminal without any messages by default.

[Sonicadvance1]

I don't have time to diagnose, but it smells like something is going wrong with the XDG config changes that occurred recently.

[Slatepaws]

I don't have time to diagnose, but it smells like something is going wrong with the XDG config changes that occurred recently.

I'll try a few things later. deleting and creating directories to it's expectations and moving the mount point of the squashfs. Kinda burnt out this weekend on debugging and trying to get this to work for the moment. I'll post later on the results.

[Slatepaws]

I don't have time to diagnose, but it smells like something is going wrong with the XDG config changes that occurred recently.

Some progress.

Creating the .fex-emu in the user home dir gets the server to start. but will complain about a miss-configured root-fs.
In fact it will complain no matter where you set it in FEXConfig other than.
/home/kevin/.local/share/fex-emu/RootFS/

After this it 'seems' to work but i have nothing to test it on at the moment.
output-test.txt

[Slatepaws]

I don't have time to diagnose, but it smells like something is going wrong with the XDG config changes that occurred recently.

Had some time to test. Unigine-valley benchmark runs. But you have to run it in a window manager without fractional scaling or the settings and launch window appears 'tiny'.

Steam, the main reason i wanted to get this working. So i can gauge the project and possible value of the steamframe.

Doesn't though. /home/kevin/.local/share/Steam/ubuntu12_32/steamui.so failed: /usr/lib/libgl.so.1: undefined symbol: __gxx_personality_v0

Don't know if it's calling the root-fs or system libgl.

Side note, Is the software supposed to behave in such a way that it will automatically start the server upon attempted execution of a x86_32/x86_64 binary?

[Sonicadvance1]

Doesn't though. /home/kevin/.local/share/Steam/ubuntu12_32/steamui.so failed: /usr/lib/libgl.so.1: undefined symbol: __gxx_personality_v0

Don't know if it's calling the root-fs or system libgl.

That would be using the rootfs libgl.

Side note, Is the software supposed to behave in such a way that it will automatically start the server upon attempted execution of a x86_32/x86_64 binary?

Yes, FEX will autostart the FEXServer if it isn't running