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
{{ message }}
This repository has been archived by the owner on Sep 23, 2021. It is now read-only.
After I use the xpra program (even after it has exited), physlock hangs on invocation and nothing happens.
I am using physlock 13, from the git revision d4091fe.
On physlock git-20170902, the version that comes with my operating system by default, it says "physlock: Unable to detect user of tty2" and then exits. I am using NixOS version 19.03. This might have something to do with it, but I can't switch framebuffers with ctrl-alt-f<n> after using xpra, either.
This might not actually be a bug in physlock, especially given the inability to switch framebuffers, but I figured this would be a good place to start looking for answers.
The text was updated successfully, but these errors were encountered:
After I use the xpra program (even after it has exited), physlock hangs on invocation and nothing happens.
I am using physlock 13, from the git revision d4091fe.
On physlock git-20170902, the version that comes with my operating system by default, it says "physlock: Unable to detect user of tty2" and then exits. I am using NixOS version 19.03. This might have something to do with it, but I can't switch framebuffers with ctrl-alt-f<n> after using xpra, either.
This might not actually be a bug in physlock, especially given the inability to switch framebuffers, but I figured this would be a good place to start looking for answers.
The text was updated successfully, but these errors were encountered: