GNU bug report logs -
#29211
XScreenSaver does not recognise password
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29211 in the body.
You can then email your comments to 29211 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#29211
; Package
guix
.
(Wed, 08 Nov 2017 13:29:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 08 Nov 2017 13:29:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello Guix,
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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#29211
; Package
guix
.
(Wed, 08 Nov 2017 14:06:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 29211 <at> debbugs.gnu.org (full text, mbox):
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’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#29211
; Package
guix
.
(Wed, 08 Nov 2017 15:17:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 29211 <at> debbugs.gnu.org (full text, mbox):
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
Reply sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
You have taken responsibility.
(Wed, 08 Nov 2017 16:22:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
bug acknowledged by developer.
(Wed, 08 Nov 2017 16:22:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 29211-done <at> debbugs.gnu.org (full text, mbox):
Apparently this is not a bug.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#29211
; Package
guix
.
(Wed, 08 Nov 2017 20:36:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 29211 <at> debbugs.gnu.org (full text, mbox):
Diego Nicola Barbato <dnbarbato <at> posteo.de> skribis:
> 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.
Heheh. So all you have to do is ‘guix package -r xscreensaver’.
Thanks for confirming!
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 07 Dec 2017 12:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 256 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.