-
Notifications
You must be signed in to change notification settings - Fork 22
Won't let me unlock #29
Comments
Is this all on the lock screen? |
What do you mean? Sent from ProtonMail mobile -------- Original Message -------- On Sep 26, 2017, 03:58, Victor Tran wrote: Is this all on the lock screen? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
|
Where are you having issues unlocking your computer? For the shell issue, that's been resolved in theShell Blueprint and fixed in the next release. |
This is on the lock screen. Turned on via shortcut or by suspending and waking it up again.
Sent from ProtonMail mobile
…-------- Original Message --------
On Sep 26, 2017, 08:17, Victor Tran wrote:
Where are you having issues unlocking your computer?
For the shell issue, that's been resolved in theShell Blueprint and fixed in the next release.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#29 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGb-cq1lkzowQoZwGFl4MVSwnHQM-hvPks5smOtFgaJpZM4PjoUJ).
|
@vicr123 I'll get a VM spun up so I can record the issue I'm running into. |
What distribution are you running this on? I feel this may be an old version of theShell where it has issues starting up if you have your computer plugged in, which was addressed in theShell 7.0. |
Arch
Sent from ProtonMail mobile
…-------- Original Message --------
On Sep 27, 2017, 00:40, Victor Tran wrote:
What distribution are you running this on?
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#29 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGb-clMBU7ptz-3Ir9ao622501p7ztAlks5smdHXgaJpZM4PjoUJ).
|
What version of theShell are you running? |
I was running stable and blueprint. Same issue.
Sent from ProtonMail mobile
…-------- Original Message --------
On Sep 28, 2017, 08:46, Victor Tran wrote:
What version of theShell are you running?
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#29 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGb-cmGWKdM50mYz_LW9M4OjUMVkodFiks5sm5UvgaJpZM4PjoUJ).
|
Is |
I'll have to check later.
Sent from ProtonMail mobile
…-------- Original Message --------
On Sep 28, 2017, 09:03, Victor Tran wrote:
Is tscheckpass installed on your computer? It should have been a dependency of tsscreenlock, and the executable is located in /usr/bin/tscheckpass
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#29 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGb-cuMESav4-_oVPOPVvBUCmVVHzDeFks5sm5k4gaJpZM4PjoUJ).
|
@vicr123 running |
So after cloning and compiling tscheckpass myself, it seems like it should work now. Don't have time to test right now. |
Still does not work after recompiling and replacing original binary. |
Your password was set when you installed Arch using |
Was set using passwd |
I know this happens if you don't have a password, unless that was already fixed. |
Can't seem to unlock the computer. Displays what my shell is... Not my username. My correct password doesn't unlock my screen.
The text was updated successfully, but these errors were encountered: