Skip to content
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

Doesn't seem to work anymore on suspend / sleep after latest update #394

Closed
1 task done
pimpeters opened this issue Aug 29, 2023 · 9 comments
Closed
1 task done
Labels

Comments

@pimpeters
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Operating system

Arch Linux x86_64

Installation method

Package Manager (from OS)

Betterlockscreen & Dependency-Versions

- Betterlockscreen: v4.1.0
- i3lock-color: 2.13.c.5
- ImageMagick: 7.1.1-15
- dunst (if used): -
- feh (if used): 3.10

Bug description

Manual calling /usr/bin/betterlockscreen --lock seems to work.
But after suspending / sleeping it shows betterlockscreen for about 0,5 second and after that just passes through the auth.

Manually calling lockscreen and suspending after that seems to work.

Steps to reproduce

  1. Suspend system (systemctl suspend or closing lit)
  2. Resume system and you should see the lockscreen flash for 0,5s and after that it will automatically unlock

Relevant log output

Aug 29 18:20:12 artemis systemd[1]: betterlockscreen@pim.service: Deactivated successfully.
Aug 29 18:20:11 artemis betterlockscreen[7510]: [*] Running postlock...
Aug 29 18:20:11 artemis betterlockscreen[7510]: [*] Locking screen...
Aug 29 18:20:11 artemis betterlockscreen[7510]: [*] Running prelock...
Aug 29 18:20:11 artemis betterlockscreen[7510]: [B] Betterlockscreen
@pimpeters pimpeters added the bug label Aug 29, 2023
@korikori
Copy link

Came here to report the same - I see the lock screen before the screen is turned off during suspend, but then after resuming I don't even see it flash, it just throws me out to desktop.

Aug 29 21:15:07 tempest systemd[1]: Starting Lock screen when going to sleep/suspend...
Aug 29 21:15:07 tempest betterlockscreen[7010]: [B] Betterlockscreen
Aug 29 21:15:07 tempest betterlockscreen[7010]: [*] Running prelock...
Aug 29 21:15:07 tempest betterlockscreen[7010]: [*] Locking screen...
Aug 29 21:15:07 tempest betterlockscreen[7010]: [*] Running postlock...
Aug 29 21:15:08 tempest systemd[1]: betterlockscreen@kori.service: Deactivated successfully.
Aug 29 21:15:08 tempest systemd[1]: Started Lock screen when going to sleep/suspend.

@l4loLX3
Copy link

l4loLX3 commented Aug 30, 2023

Hi!
I’m using a Arch Linux x86_64 system on a laptop with qtile as a WM. Changing betterlockscreen@.service line 8 "Type=simple" to "Type=forking" seem to work for me at the moment.
source: https://wiki.archlinux.org/title/Session_lock#Before_suspend_or_hibernate
note1: don't forget to "systemctl restart betterlockscreen@$USER" after you make the change.

@korikori
Copy link

Thanks @l4loLX3, this worked for me.

@SebTM
Copy link
Collaborator

SebTM commented Aug 30, 2023

Do we have some non-arch users that can verify that or can you check in/with the arch-forum why that changed?

@SebTM
Copy link
Collaborator

SebTM commented Sep 2, 2023

Hey, can please everyone having issues try the pull-request #395 and let me know if it fixes your issues so I can make a release?

@korikori
Copy link

korikori commented Sep 2, 2023

Yes @SebTM, this works for me even without the Type=forking fix proposed by @l4loLX3 above.

@pimpeters
Copy link
Author

@SebTM that PR also fixes it for me!

@SebTM
Copy link
Collaborator

SebTM commented Sep 2, 2023

Released, so closing for now - please reopen/create a new issue if you encounter any issue still/again

@SebTM SebTM closed this as completed Sep 2, 2023
@l4loLX3
Copy link

l4loLX3 commented Sep 2, 2023

Yes @SebTM. Thank you. I also can confirm that is fix after the last update without the Type=forking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants