Add convenient way to use xidlehook with xss-lock

[wchresta]

Description

services.screen-locker provides a convenient way to define the xss-lock service together with the xautolock service to get automatic screenlock after idle. Unfortunately, xautolock lacks some features that xidlehook would provide.

While there is a definition for xidlehook in services.xidlehook, there is no convenient way to use xidlehook together with xss-lock. So, to achieve screen locking via xss-lock and xidlehook, one has to define their own xss-lock service definition.

This FR asks to add a convenient way to use xidlehook together with xss-lock without the user having to define either service themselves.

This could be achieved with one of the following:

• Add xidlehook as an alternative to xautolock in screen-locker
• Add a convenient way to disable both xautolocker and xset in screen-locker, such that one can use xidlehook instead via services.xidlehook
• Refactor screen-locker and pull out services.xss-lock such that it can be used in combination with services.xidlehook.

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[Aleksanaa]

Indeed, xss-lock should not be bound to any specific implementation of auto locking. It can even be used in wayland (but I just discovered swayidle has the same feature to listen to systemd event).

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.