Open davelindquist opened 5 years ago
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 haven't seen that issue for months after I did a freh install of archlinux. But a few days ago,it reappeared. Switching VTs does not help :-(
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 I'm downgrading systemd by now.
EDIT: For those on arch, replacing arch mirrors by manjaro mirrors is an easy fix (and a way to prevent future issues)
My current workaround is:
- removed light-locker from system
- Changed the lock command: xfconf-query -c xfce4-session -p /general/LockCommand -s "dm-tool switch-to-greeter"
- Enabled Lock-On-Syspend: xfconf-query -c xfce4-session -p /shutdown/LockScreen -t bool -s true --create
This gives me a working setup where I get a lightdm greeter screen after suspend or when I manually lock the screen.
@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. I switched to xfce4-screensaver now which simply works.
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. That dialog appears and lies because no matter how long you wait it will still be there. I have to Ctrl+Shift+Backspace to restart session.
I have this issue too on GarudaLinux (ArchLinux) after Suspend. To have the access to XFCE, I have to kill (-9) light-locker from Ctrl-Alt-F2 terminal (VT)...
light-locker 1.9.0-4 (community) Linux 5.16.0-zen1-1-zen ZEN SMP PREEMPT 10 Jan 2022 20:12 OS: Garuda Linux x86_64 1.4 Soaring (White-tailed-eagle) DE: Xfce 4.16 WM: Xfwm4 WM Theme: Default Theme: Prof-XFCE-2.1 CPU: Intel i7-2620M (4) @ 3.400GHz GPU: NVIDIA GeForce GT 540M 1920x1080
this pegs my SSD and rarely recovers even. I end up having to reboot and finally just uninstalled it before it killed my hardware...
It can kill hardware? I also got session locked idk what to do
did you tried CTRL + ALT + F7?
I did this and my session got locked what should I do?
Still a problem on Debian Sid.
$ dpkg -l | grep light-locker
ii light-locker 1.8.0-3 amd64 simple screen locker for lightDM display manager
Still occurring on Debian 12/bookworm
light-locker/stable,now 1.8.0-3 amd64 [installed,automatic]
I have this issue too on GarudaLinux (ArchLinux) after Suspend. To have the access to XFCE, I have to kill (-9) light-locker from Ctrl-Alt-F2 terminal (VT)...
light-locker 1.9.0-4 (community) Linux 5.16.0-zen1-1-zen ZEN SMP PREEMPT 10 Jan 2022 20:12 OS: Garuda Linux x86_64 1.4 Soaring (White-tailed-eagle) DE: Xfce 4.16 WM: Xfwm4 WM Theme: Default Theme: Prof-XFCE-2.1 CPU: Intel i7-2620M (4) @ 3.400GHz GPU: NVIDIA GeForce GT 540M 1920x1080
Life-saver! Thanks for this. Waited several minutes for the redirect, but nothing really happens, ugh... Linux Mint 21.3, FWIW.
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!