Xfce Forum

compost

Member

Registered: 2023-10-28

Posts: 1

XScreenSaver fails to activate on lid close—sometimes (new problem)

I upgraded from Debian bullseye to bookworm a few months ago and my computer developed a number of problems around the screensaver:

- When suspending by closing the lid, xscreensaver would not always activate.
- When resuming, if the screensaver did activate, I would see an image of the desktop as I had left it -- rather than the screensaver graphics and the login box. It was interactive, but invisible.
- I've occasionally had the screensaver randomly activate, on what seems like a delay after a suspend.

All of these have been sometimes-yes-sometimes-no failures, which leads me to think of race conditions and such.

Power Manager settings:

- When laptop lid closed: Suspend
- Display power management: Unchecked
- Light Locker: Automatically lock the screen: Never
- Light Locker: Lock screen when system is going to sleep: Checked (?)

XScreenSaver settings:

- Blank after 6 minutes
- Lock after 1 minute
- Fade to black when blanking: checked
- Display Power Management: unchecked

Things that do work properly:

- xscreensaver-command --lock
- Suspending from the keyboard (Fn key combo)
- Suspending from the user menu

In the past, the power manager settings have been *very* difficult to get right, so this isn't totally surprising. But it's a bit of a nasty shock to find that closing my laptop hasn't locked it.

What else should I be checking on?

Kartoffelstolz

Member

Registered: 2024-02-24

Posts: 3

Re: XScreenSaver fails to activate on lid close—sometimes (new problem)

I had a very similar problem and running these commands got rid of it:

cd .config/xfce4/xfconf/xfce-perchannel-xml
mv displays.xml displays.xml.bak
mv xfce4-power-manager.xml xfce4-power-manager.xml.bak
mv xfce4-session.xml xfce4-session.xml.bak

EDIT: Do this in another tty after logging out of the XFCE session for best effect

The rest of my post: https://forum.xfce.org/viewtopic.php?pid=74869

I'm hoping this solves a nearly identical but obscure issue I had. Apologies if this is discouraged necroposting.

Last edited by Kartoffelstolz (2024-02-24 22:15:50)