If you’re able to give precise instructions on what to do to resolve the issue, then couldn’t you also automate it and make it seamless from the user’s perspective?
These steps require logging in again. I don’t think it’s secure to have it automatically try and fix the lock screen, since it just introduces more ways to potentially bypass it.
The user does have to log in again to access the second TTY. I don’t know exactly what Hyprland’s settings do, but “allow_session_lock_restore” doesn’t sound like something you want turning on randomly while an attacker is sitting trying to access your computer. It’s very possible the crash itself was caused intentionally by the attacker in that case.
Edit: Nevermind “allow_session_lock_restore” is just for saving open windows and stuff, so not really an issue. Restarting the lock screen however is very much not something you want to do while trying to keep an attacker out of your computer.
If you’re able to give precise instructions on what to do to resolve the issue, then couldn’t you also automate it and make it seamless from the user’s perspective?
These steps require logging in again. I don’t think it’s secure to have it automatically try and fix the lock screen, since it just introduces more ways to potentially bypass it.
A background process monitoring the login screen doesn’t have to “log in again”
The user does have to log in again to access the second TTY. I don’t know exactly what Hyprland’s settings do,
but “allow_session_lock_restore” doesn’t sound like something you want turning on randomly while an attacker is sitting trying to access your computer.It’s very possible the crash itself was caused intentionally by the attacker in that case.Edit: Nevermind “allow_session_lock_restore” is just for saving open windows and stuff, so not really an issue. Restarting the lock screen however is very much not something you want to do while trying to keep an attacker out of your computer.