You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I launch Rhythm Doctor, doorstop seems to be logging to my .config/mimeapps.list file and it breaks all my default application handling! It adds the line Found UnityPlayer, hooking into it instead to the start of the file so my system can't parse the file.
It also makes a folder in the game directory called Found UnityPlayer, hooking into it instead in the game folder, with this file, minus the .txt extension. profilerc.txt
It seems to be some error with how doorstop is trying to capture/redirect stdout, but for now I've compiled doorstop without logging to fix it.
The text was updated successfully, but these errors were encountered:
This problem is now more present with the latest update from Steam, forcing Linux native games to run inside their runtimes.
Take a look at this issue, specifically this comment and comments after it.
Even tho Valheim uses an older version of doorstop, the issue is the same since even the latest version of doorstop is using printf to print logs, which will not work anymore inside the steam's linux container runtime (read this comment).
I saw this PR on the old Unix version of doorstop and I think something like that should be implemented in the new version, moving logging to a separate file instead of the stdout
Using Unix version of BepInEx 5 on Rhythm Doctor.
Whenever I launch Rhythm Doctor, doorstop seems to be logging to my
.config/mimeapps.list
file and it breaks all my default application handling! It adds the lineFound UnityPlayer, hooking into it instead
to the start of the file so my system can't parse the file.It also makes a folder in the game directory called
Found UnityPlayer, hooking into it instead in the game folder
, with this file, minus the.txt
extension.profilerc.txt
It seems to be some error with how doorstop is trying to capture/redirect stdout, but for now I've compiled doorstop without logging to fix it.
The text was updated successfully, but these errors were encountered: