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.
Unfortunately the SingleApplication implementation seems to be full of race conditions, e.g. when one application has started closing down but you are starting a new one (this one seems unavoidable by design) but there also seem to be other issues that mean that after a crash it is not possible to start a new instance for several seconds.
The latter seems to happen because the shared memory instance somehow lingers while the server does not respond.
It is probably fixable (by starting the application if the message is never acknowledged - but this just leads to other issue like that in some cases like extreme system load you can end up with multiple running instances after all), but is this feature really worth the amount of code and really annoying bugs?
Especially since as far as I can tell there are no too serious conflicts between 2 instances running at the same time, as qtpass has almost no internal state.
The text was updated successfully, but these errors were encountered:
And additional bug: If one user runs qtpass, no other users will be able to run qtpass on the same machine on Linux (I suspect it might work ok on Windows, but haven't tested).
Equally annoying, an individual user can run qtpass only on one single display, so if you started qtpass on your desktop you will not be able to start another instance via X forwardning, a VNC server or xpra for example.
I don't know what happened, but I now in over 50% of startup attempts get this message:
"QLocalSocket::connectToServer: Connection refused"
This happens even if the previous attempt was a long time ago.
It might be related to qtpass crashing though I admit, since I've been debugging crashes lately...