when Xpra is passed an incorrect password file when starting a session (xpra start), it spits out the following:
cannot open password file passwd: [Errno 2] No such file or directory: 'passwd' and happily goes on.
It should actually exit.
Strongly disagree: the password file can be created, or changed, at any time. If it does not exist then the password just won't match - which is also fine. This way, scripts and tools can change/delete the password file to prevent/give-new access to a session.
I understand and it's a good idea.
I have one question however: it seems that Xpra's CWD becomes / for some reason, so passing a relative path to the password file doesn't work (at least in the case I tried). Are you aware of that?
hmmm, I don't know about CWD changing to '/' - it sort of rings a bell.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/115