Kai Krakow

Please provide logs as per bug report instructions.

> `[22977.776738] Bluetooth: hci0: ACL packet for unknown connection handle 3837` This looks like bluez could not fully pair the controller and lost the connection. Please check our troubleshooting docs...

If uhid is loaded and it still doesn't work, bluez may ship with uhid disabled. If it still doesn't work, the controller probably doesn't fully handshake, try a different Bluetooth...

> It's not impossible to fix any of this, but we ran out of time (note the timestamps on those commits) and made a judgment call. It would be nice...

> why using steamuser instead of the actual username? I could not find any clear explanation so far Most likely so that Steam cloud saves still sync to the correct...

> What in opposite means, if you have multiple spearate (real) users on Linux, they would share all cloud saves, because they are all "steamuser"? Nope, the prefixes are not...

I wonder what the game from the initial issue report actually uses for the username in the game: - I think Proton mostly cares about properly mapping `C:\Users\steamuser` so this...

I think the problem is that fossilize assigns the work into thread buckets statically and not dynamically, resulting in a progress of almost 100% near the end, waiting potentially on...

`fossilize_replay` is meant to run when the game is not running, so the behavior of it running 100% on some cores after the game exited is expected. If you start...

It cannot and does not run while the game is running - for maybe not so obvious reasons. But I think you can adjust Steam to not do background compilation...