Search Criteria
Package Details: systemd-lock-handler 2.4.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/systemd-lock-handler.git (read-only, click to copy) |
---|---|
Package Base: | systemd-lock-handler |
Description: | Logind lock event to systemd target translation. |
Upstream URL: | https://git.sr.ht/~whynothugo/systemd-lock-handler |
Keywords: | lock session systemd unlock |
Licenses: | ISC |
Submitter: | whynothugo |
Maintainer: | whynothugo |
Last Packager: | whynothugo |
Votes: | 5 |
Popularity: | 0.001297 |
First Submitted: | 2017-05-29 02:18 (UTC) |
Last Updated: | 2023-05-04 13:01 (UTC) |
Dependencies (2)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, go-sylixosAUR, gcc-go-snapshotAUR, gcc-go) (make)
Latest Comments
whynothugo commented on 2023-08-15 14:39 (UTC)
I'm not actively using this package on Arch. If somebody wants to (co)-maintain it, the help is appreciated.
OJFord commented on 2023-03-18 19:29 (UTC)
Thanks!
I'm not sure I follow that though - as I described this initially manifested to me as 'not locked on resume from sleep', and I've since noticed (as I added notifications on failed systemd units) that my idle hint does actually seem to be working: I get a failed systemd-lock-handler.service (and no locked screen) if I leave it unattended for a bit.
whynothugo commented on 2023-03-14 23:58 (UTC)
BTW, issue tracker is here: https://todo.sr.ht/~whynothugo/systemd-lock-handler
whynothugo commented on 2023-03-14 23:58 (UTC)
Based on these lines:
Looks like I tried to grab the next inhibitor too soon. Usually the second grab happens after resuming from sleep, but this one happened too quickly. Obvious this is a bug, but I'm not entirely sure how to determine when the system has come back from sleep.
This could be worse tho; the service dies always after having completed all its work.
I've updated
systemd-lock-handler.service
to restart on failure after 10 seconds, though that's obviously a terrible hack until a real solution is found.OJFord commented on 2023-03-10 17:38 (UTC) (edited on 2023-03-10 17:48 (UTC) by OJFord)
@whynothugo Do you have an issue tracker for non-packaging issues?
I have an error preventing locking on sleep.target (so it sleeps unlocked), but lock.target is fine, that seems related to the 2.4 change:
That's
systemctl suspend
at 16:59, followed by a resume (no lock-screen) andloginctl lock-session
(successful, and unlocked) at 17:11.Naively I would think if 'The operation inhibition has been requested for is already running' that's simply not an error, it just needs to catch it and carry on? Perhaps it's a symptom of something else though.
This isn't a one-off, it hasn't been working for me for some time, but I thought it related to the systemd suspend-then-hibernate regression/behaviour change in <v253, so I hadn't looked into it until now. Let me know if there's anything else I can provide (or if there's somewhere better to take this discussion/that a duplicate issue exists already).
My swaylock.service is exactly per the readme (as at v2.4.1) - except that if I change WantedBy -> RequiredBy lock.target it seems to work, or work more often, or perhaps that was a fluke - since I did have that set prior to copying the new readme (I didn't have it forking, or Restart/After/OnSuccess as added to the readme in 2.4 before).
It seems that at least part of the problem is that systemd-lock-handler.service itself doesn't restart on failure, and this seems to happen (at least) after a successful resume, which then leaves it failed & exited for the next sleep event.
ayushnix commented on 2023-02-05 05:30 (UTC)
@whynothugo looks like your key has changed for the 2.4.0 tag but it hasn't been updated in the PKGBUILD. I also can't find your key on either GitHub or Sourcehut :)
whynothugo commented on 2021-08-09 12:22 (UTC)
@alcubierre-drive Fixed. I rotated my signing key, but didn't update the one in PKGBUILD.
alcubierre-drive commented on 2021-08-09 09:33 (UTC)
I can't update; I get an invalid PGP signature error:
==> Verifying source file signatures with gpg... systemd-lock-handler git repo ... FAILED (unknown public key 388ADF1E2EEA7F1A) ==> ERROR: One or more PGP signatures could not be verified! error: failed to download sources for 'systemd-lock-handler-2.1.0-1': error: packages failed to build: systemd-lock-handler-2.1.0-1
BlubbTec commented on 2019-08-05 12:58 (UTC)
I also get this error when running:
BlubbTec commented on 2019-08-05 12:58 (UTC)
This also requires
python-service_identity
as a dependency, otherwise I get: