Closed mtheilm closed 1 month ago
Can you check if you have a steam process orphaned somewhere? ps -ef | grep steam
or so?
The "client" in this case is steam - this is from the perspective of the wayland compositor. Steam is just hanging there for 10 seconds without doing anything, for some reason. Steam is the worst.
If you look at htop
while this is happening, how does CPU look?
Steam doesn't appear to be orphaned, and top
shows steam running until it times out (is killed?) on the magic mirror side and then disappears. Nothing abnormal re: CPU (xwayland spins up at 4% and mmserver stays down at 1%). FWIW rebooting the server and retrying yields the same. And bumping the ACCEPT timeout to 60s, shockingly, does not fix the issue :)
Are there any other steam logs in ~/.local/share/Steam/
or so?
I think the next debugging step would be to attach a monitor to that bad boy and start steam up. :/
After some debugging, this appears to be this (bonkers) issue: https://github.com/ValveSoftware/steam-for-linux/issues/10879
Since this is on steam's side and a mitigation inside magic mirror isn't really possible, going to close this.
Description
magic mirror no longer launches steam at all, throwing the following errors. Running with most recent
main
commit (869995731ae2c67dd66a87861103480e4b16a079). Bug report attached.Note that running
vkcube-wayland
does successfully launch and run.Client Error
Server Error
Bug Report
bugreport.tar.gz