-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Painful "You'll be redirected to the unlock dialog in a few seconds" - Does it have to be there? #126
Comments
this pegs my SSD and rarely recovers even. I end up having to reboot and finally just uninstalled it before it killed my hardware... |
did you tried CTRL + ALT + F7? |
Yeah, CTRL - ALT - F7 is an easy way to make this happen. It seems like it's doing something weird like:
But this is just a rough hypothesis. Can anyone explain exactly what is going on, and why this message is needed? (light-locker never used to do this -- how did it work before?) Thanks! |
my keyboard wouldnt even work, it was almost like a kernel panic, I just stopped using it all together... |
Hello, |
I give up with light-locker. That "something is broken after suspend" kills my whole prodoctivity. My current workaround is:
This gives me a working setup where I get a lightdm greeter screen after suspend or when I manually lock the screen. |
+1 See also: #94 |
I can confirm, the issue is back. See #146 EDIT: For those on arch, replacing arch mirrors by manjaro mirrors is an easy fix (and a way to prevent future issues) |
@micw For me this workaround left the session unlocked, ctrl + alt + F7 just switches back to the desktop |
The lock-on-suspend stopped to work for me after I rebootet. The "dm-tool switch-to-greeter" still works. You can test it by just issuing the command. |
After a recent update, I'm also getting this bug. Running light-locker 1.8.0-2 with systemd 243.51-1 on arch (5.3.1.arch1-1). My current workaround is not to run light-locker at all. |
I have this issue too. on Mx Linux 18.3. |
I have this issue too on GarudaLinux (ArchLinux) after Suspend. light-locker 1.9.0-4 (community) |
It can kill hardware? I also got session locked idk what to do |
I did this and my session got locked what should I do? |
Still a problem on Debian Sid.
|
Still occurring on Debian 12/bookworm
|
The new light-locker seems to have implemented a very painful dialog + delay -- when you switch to a session that is locked, you get:
This delay (before the unlock dialog comes up) is PAINFUL; several seconds of wait time. Is there a reason that this has to be there? The older versions did not have this; why was this delay added? Can it be removed, or configured out?
Thanks very much!
The text was updated successfully, but these errors were encountered: