Skip to content

screensaver-proxy: Activate the screensaver for logind Lock - #477

Closed
radkawar wants to merge 1 commit into
linuxmint:masterfrom
radkawar:fix/logind-lock-activation
Closed

radkawar wants to merge 1 commit into
linuxmint:masterfrom
radkawar:fix/logind-lock-activation

Conversation

@radkawar

Copy link
Copy Markdown

Watch logind's Lock signal for this daemon's own login session and activate the screensaver through the existing cinnamon-screensaver-command --lock helper. The helper preserves custom screensaver behavior. The listener belongs in the persistent proxy: cinnamon-screensaver normally exits after 30 seconds idle and cannot receive the signal then. Stop removes the subscription.

Native testing: Linux Mint 22.3 Cinnamon X11, golden KVM guest admitted through the normal lab FIFO. Built an unmodified 6.6.2 daemon package and the same patch backported to 6.6.2, using dpkg-buildpackage -b -us -uc -j2. With the screensaver's LockedHint patch from linuxmint/cinnamon-screensaver#521 installed, waited 35 seconds after each fresh graphical login and confirmed the screensaver bus name was unowned. Baseline: loginctl lock-session left LockedHint=no. Patched: the same request activated the screensaver (GetActive=true, LockedHint=yes); logind unlock returned both to false/no.

AI disclosure: Developed with AI assistance. The native baseline comparison described above was executed.

Signed-off-by: radkawar <radkawar28@gmail.com>
@mtwebster

Copy link
Copy Markdown
Member

This is handled in Cinnamon now for the upcoming release.

This daemon's main purpose is to forward inhibitors using the freedesktop screensaver api to Cinnamon's session manager.

@mtwebster mtwebster closed this Oct 15, 2026
@radkawar

Copy link
Copy Markdown
Author

Thanks for the explanation. I will keep the tested Mint 22.3 compatibility backport fork-only rather than pursue this for the upcoming Cinnamon release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants