Bug#1072722: nvidia-driver: Please configure SYSTEMD_SLEEP_FREEZE_USER_SESSION=false

Luca Boccassi bluca at debian.org
Sun Jun 9 22:26:52 BST 2024


On Sun, 9 Jun 2024 at 21:07, Andreas Beckmann <anbe at debian.org> wrote:
>
> Hi Peter,
>
> thanks for testing that.
>
> On 08/06/2024 16.42, Peter De Wachter wrote:
> > Those locations work. But the correct environment variable turns out to be
> > SYSTEMD_SLEEP_FREEZE_USER_SESSIONS (plural), the NEWS file has it wrong.
>
> Hi Luca,
>
> do you need a cloned bug against systemd for the variable mismatch?

Thanks but no need, it's just the changelog, already fixed it.

> > (I've no idea why suspend seemed to work for me yesterday with the wrong
> > variable. Today it definitely didn't.) The overrides probably also need to
> > be installed for the other service files that run systemd-sleep:
> > systemd-hybrid-sleep.service, systemd-hibernate.service and
> > systemd-suspend-then-hibernate.service.
>
> Can you give some hints here?
>
> And if it is the case that we need these override variables in many
> places, isn't there an easier way to "configure systemd-sleep behavior"
> regardless of the way it is being called?

This is a workaround, so the drop-in is the only way. The correct fix
is for the functionality to stop relying on the user session being
runnable to come out of suspension, as that's the real problem. I
realize you can't fix this, but at least it should be reported
upstream, asking them to fix it (they probably won't, I know)



More information about the pkg-nvidia-devel mailing list