protontricks appears to require --no-bwrap about protontricks HOT 4 CLOSED

The "filesystem argument not handled yet" error was reported in the previous issue #281 and Protontricks was updated to make that error message more prominent. I suggested --no-bwrap as a potential workaround:

If renaming or deleting the offending directory is not an option, you should be able to use --no-bwrap flag as a workaround, though that means Proton won't be run under Steam Runtime and you might run into other issues.

The root cause is Steam Runtime not supporting the two characters.

Do you know what created the problematic root directory /sudo:[email protected]:? It seems like an odd directory, and one you might not have intended to create. If that's the case, another option would be to delete it.

from protontricks.

Thank you.
As far as I can tell, the 'sudo:' string is added by protontricks itself?
I will keep digging; but the original invocation simply requests "echo $WINEPREFIX" and there is no mention of filesystems to mount. I was originally searching for the addition of that string, but I stopped when I found the --no-bwrap option solved the issue.
So I will dig more to find where that mount option comes from.

from protontricks.

The mount directories are discovered in the Bash script here using a simple for dir in /* loop.

https://github.com/Matoking/protontricks/blob/master/src/protontricks/data/scripts/bwrap_launcher.sh#L51

Protontricks itself doesn't use sudo anywhere.

The simple way to check this would be to run ls -lha / and see what comes up.

from protontricks.

oh....
Now I feel stupid. There is a directory in my root named "sudo:[email protected]:" from 2 years ago.

emacs syntax for opening a directory as a sudo'd root is: "sudo::root@[hostname]:/[whatever]" and I must have created the directory by typo.
Thanks for your time.

from protontricks.