GNU bug report logs - #29211
XScreenSaver does not recognise password

Previous Next

Full log

View this message in rfc822 format

From: Diego Nicola Barbato <dnbarbato <at> posteo.de>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 29211 <at> debbugs.gnu.org
Subject: bug#29211: XScreenSaver does not recognise password
Date: Wed, 08 Nov 2017 16:16:05 +0100

Hello Ludo,

ludo <at> gnu.org (Ludovic Courtès) writes:

> Hi Diego,
>
> Diego Nicola Barbato <dnbarbato <at> posteo.de> skribis:
>
>> When I lock my screen with XScreenSaver by first running
>> `xscreensaver &' and then `xscreensaver-command --lock' I am unable to
>> unlock the screen by entering my password.  This happens even though I
>> have added `(screen-locker-service xscreensaver "xscreensaver")' to my
>> services in my `config.scm'.
>> I run StumpWM on GuixSD.
>>
>> Greetings,
>>
>> Diego
>>
>> P.S. I am not sure whether this is relevant but this bug seems to
>> coincide with a change in the time displayed on the unlock dialog:  It
>> no longer displays the wrong time (two hours behind the output of
>> `date') and the format has changed from a 24h format to one using AM and
>> PM.
>
> To me that suggests ‘xscreensaver’ is taken from your profile (or the
> global profile) instead of being taken from
> /run/setuid-programs/xscreensaver.
>
> What does “type -P xscreensaver” display?
>
> Thanks,
> Ludo’.

You are right. `type -P xscreensaver' returns
`/home/diego/.guix-profile/bin/xscreensaver'.  And if i run
`/run/setuid-programs/xscreensaver &' instead of `xscreensaver &'
everything works as expected. 

Apparently my setup should never have worked in the first place.  The
fact that it did until about two weeks ago led me to think this was a
bug.

Thanks,

Diego

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.