Re: betterlockscreen: patch to enable call to suspend with void.

Re: betterlockscreen: patch to enable call to suspend with void.

[Piraty]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

New comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/19354#issuecomment-599615413

Comment:
I don't use this package, but i guess the sudo line only works for those who configure NOPASSWD in sudoers ?

Re: betterlockscreen: patch to enable call to suspend with void.

[Piraty]

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

New comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/19354#issuecomment-599615413

Comment:
I don't use this package, but i guess the sudo line only works for those who configure NOPASSWD in sudoers ?

I'm afraid it's not that simple

Re: betterlockscreen: patch to enable call to suspend with void.

[MaxLeoSchmid]

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

New comment by MaxLeoSchmid on void-packages repository

https://github.com/void-linux/void-packages/pull/19354#issuecomment-599649589

Comment:
You're right.

I have the NOPASSWD exeption/rule(?) set for halt, zzz etc. like it is described in the wiki here:
[https://wiki.voidlinux.org/Post_Installation#Allow_users_to_shutdown_without_a_password](https://wiki.voidlinux.org/Post_Installation#Allow_users_to_shutdown_without_a_password)

I didn't think about the fact, that the "sudo zzz"  process would just stay around if you don't add the rule in the sudoers file.

Would there be any issues with xbps just changing the line manually after installing?
If not a wiki entry showing you, how to do that, would probably be a better way.

Re: betterlockscreen: patch to enable call to suspend with void.

[Piraty]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

New comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/19354#issuecomment-599702624

Comment:
i don't know about systemd-suspend, but usually things like consolekit or elogind are used to elevate permission for such event. If that is above your skill, ask upstream

Re: betterlockscreen: patch to enable call to suspend with void.

[Piraty]

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

New comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/19354#issuecomment-599702624

Comment:
i don't know about systemd-suspend, but usually things like consolekit or elogind are used to elevate permission for such event. At least you can ask upstream if they up to support different mechanisms of suspend

Re: [PR PATCH] [Closed]: betterlockscreen: patch to enable call to suspend with void.

[MaxLeoSchmid]

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]

There's a closed pull request on the void-packages repository

betterlockscreen: patch to enable call to suspend with void.
https://github.com/void-linux/void-packages/pull/19354

Description:
betterlockscreen assumes you are running systemd and therefore invokes
suspend using systemctl. With the patch you can now suspend on void.
The patch also adds a 1 second delay before suspending to make sure the screen
actually locks before suspending.