Closed chrishoage closed 5 years ago
@chrishoage If you look in the issue tracker there's already many duplicates of this exact issue.
It wasn't clear to me that this was the exact same issue, considering it works for me on the first lock
from what I was reading in the other issues it didn't work for them ever
The dm-tool switch-to-greeter
workaround from #138 worked for me, with the unfortunate side effect that whichever window was active when the screen was locked loses keyboard until I switch to a different window and back.
I had time to downgrade systemd
and systemd-sysvcompat
and the issue is gone.
There seems to be a compatibility issue with systemd version 243.0-1 and light-locker
I too am having this issue. Using downgraded systemd for the time being until we figure out why this is.
I'm having this same issue on Arch Linux
Seems like I'm having the same issue.
Same here.
same on arch....
I you don't have any extra context to add to the issue, an equivalent could be using the thumbs up feature.
An easy way to reproduce this would be
light-locker-command -l # run this twice
Always produces this issue with systemd 243.
It's likely to be a bug in logind https://github.com/systemd/systemd/commits/v243/src/login, probably could bisect for the issue. I do know in GNOME they had issues with logind in 234 that required an upstream fix https://github.com/systemd/systemd/commit/471cffcfb0e005b7c4044b3b52cc4f25d217efac#diff-0eb89e0717dc797d17bc97f3e4794a6a.
Didn't have the convenience to bisect, but reverting https://github.com/systemd/systemd/commit/3b92c086a8d5338e2164ffa0ae48b3d03d10cfb5 got rid of the issue. I'm pretty sure it's what causes the issue here as well.
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.
@petrmanek Awesome workaround man. I know a couple more of the same kind - to not run GNU/Linux, to not use a computer and to not exist :D
@petrmanek Awesome workaround man. I know a couple more of the same kind - to not run GNU/Linux, to not use a computer and to not exist :D
This almost sounds like a enterprise strategy of sorts. :D :D
But seriously, I don't really like selective package downgrading. So this, albeit a crude solution, makes sense to me as a short-term fix. If this becomes a long-term issue though, my next "workaround" for this will be to find a nice Wayland compositor and cease using LightDM completely.
I had time to downgrade
systemd
andsystemd-sysvcompat
and the issue is gone.There seems to be a compatibility issue with systemd version 243.0-1 and light-locker
I have the same issue on my laptop under Archlinux and i confirm after downgrading systemd
and systemd-sysvcompat
from 243.51-1
to 242.84-2
the issue is gone.
Since this seems to be an issue with systemd, and not with light-locker, has anyone reported this to the systemd folks?
If you're confident this is an actual issue with systemd and not an issue with how light-locker uses/interfaces with systemd then by all means go file an issue with systemd
Searching their github issue tracker this issue does not have an active GHI open.
The reason I started with a GHI in the light-locker repo is because systemd otherwise works fine, and I definitely don't understand what the issue is enough to understand it's an upstream issue.
I've declined to open an issue with upstream systemd for the same reasons. Mostly because this looks like a slightly unmaintained project, so it felt inappropriate to make such a report.
However, bringing the issue to them could perhaps help us figure out what code changes need to be make in light-locker, if any, so we can proceed with fixing this.
https://github.com/systemd/systemd/issues/13769 is tracking this.
As a work around for those using Arch/XFCE (and possibly others): Replacing light-locker by xfce4-screensaver (incl. locker) works perfect for me using an up-to-date systemd. Maybe due to no switch of the VT?
Though note @newrokor that may not work for everyone as their screenlocker has a different dbus api.
We got this fixed in nixos https://github.com/NixOS/nixpkgs/issues/69399. Your distro should include commits from https://github.com/systemd/systemd/pull/13811 into systemd.
I haven't seen the bug for a while now. Currently running systemd v243.78. Don't know if the commits referenced by @worldofpeace already managed to make it into the mainline since v243.51.
This problem still occurs for me on systemd 243.78-2 in arch linux.
This problem still occurs for me on systemd 243.78-2 in arch linux.
For me it's ok i no longer have this issue on my Arch
systemd
and systemd-sysvcompat
in version 243.78-2
Did you try to reboot ?
edit:
Oh no the #$?%ing lock screen is back :cry:
This problem still occurs for me too using systemd 243.78-2 in arch linux.
For Arch users - 243.78-2
does not include the fix yet. See bug report for more info.
The issue is fixed for Arch now in systemd 273.162-2, which includes this commit that fixes this upstream issue. I upgraded systemd and tried using light-locker on my two computers and they seem to work fine.
@Elliot2560 Just upgraded to 243.162-2. Will update the thread if I see anything suspicious.
Worked for me -- thank you! It's gonna take a few days to break the habit of immediately switching to tty6 and unlocking the session from there :)
Finally :)
I wonder how many users switched to another screen locker due to this :(
(which still happening on other distros not having yet the update)
So if it is fixed upstream, let's close this issue
After upgrading systemd on Arch to 247, the same problem is back in two machines I have with the same setup.
Is anyone else experiencing this again after upgrading?
If so, should we open a new issue to track it or reopen this one?
I'm having this (or at least a very similar) issue again after upgrading as well.
Assuming you're on Arch: The package maintainer cherry picked this commit https://github.com/the-cavalry/light-locker/pull/153 to the build in the arch package repo https://github.com/archlinux/svntogit-community/commit/f2f327b937416353702e29851201d0c24e91ed77
There is this bug tracking it in the Arch bug tracker https://bugs.archlinux.org/task/68905
Downgrading from 1.9.0-3 to 1.9.0-2 works around the issue for now
This is an odd one. Recently light-locker has started to not send me to the greeter only after my second time locking. The first time works as normal. The second time I am presented with the lock screen and never sent to VT8. If I manually go to VT8 nothing is there.
To fix it I have to go to VT2 and
pkill light-locker
to get my session back.It doesn't appear the greeter matters here, I've tried with lightdm-mini-greeter and webkit2-greeter and both have this issue.
Lines of note are ones relationg to session switching
None of these kinds of logs that are present in the first lock attempt are present in the second lock attempt.
A systemd update was installed directly before these issues happened. I noticed some systemd references in the logs in the first lock attempt that were not present int he second lock attempt
systemd update in question, in case others have similar issues. When I have time later in this week I will attempt a downgrade and see if it has any effect with my issue.
full debug logs