* bug#23286: Unable to unlock xscreensaver in Xfce
@ 2016-04-13 21:16 Albin
2016-04-14 16:50 ` Ludovic Courtès
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
0 siblings, 2 replies; 32+ messages in thread
From: Albin @ 2016-04-13 21:16 UTC (permalink / raw)
To: 23286
Hi!
I just installed the xscreensaver package in Xfce and added it to
autostart. I also enabled the screen lock from the xscreensaver-demo
window. Now, if I manually run xflock4 or leave the computer alone for
a couple of minutes the screensaver starts and when I move the mouse the
unlock box appears with this text:
XscreenSaver 5.35
My hostname
Authentication failed!
My username
[OK]
Any keyboard or mouse button input just closes the unlock box and the
screensaver resumes. I'm able to escape, however, by pressing
ctrl+alt+F2 to open a new TTY from where it's possible to log in and
shut down the computer.
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-13 21:16 bug#23286: Unable to unlock xscreensaver in Xfce Albin
@ 2016-04-14 16:50 ` Ludovic Courtès
2016-04-19 19:54 ` Andreas Enge
2016-04-23 7:55 ` Danny Milosavljevic
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
1 sibling, 2 replies; 32+ messages in thread
From: Ludovic Courtès @ 2016-04-14 16:50 UTC (permalink / raw)
To: Albin; +Cc: 23286
Albin <albin@fripost.org> skribis:
> I just installed the xscreensaver package in Xfce and added it to
> autostart. I also enabled the screen lock from the xscreensaver-demo
> window. Now, if I manually run xflock4 or leave the computer alone for
> a couple of minutes the screensaver starts and when I move the mouse the
> unlock box appears with this text:
>
> XscreenSaver 5.35
> My hostname
> Authentication failed!
> My username
> [OK]
As Chris Webber mentioned on the mailing list (IIRC), you’ll also have
to enable xscreensaver in the OS config:
(use-modules (gnu services xorg))
(operating-system
;; …
(services (cons (screen-locker-service "xscreensaver")
%desktop-services)))
Could you try and report back?
I guess we’ll enable it by default in %desktop-services.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-14 16:50 ` Ludovic Courtès
@ 2016-04-19 19:54 ` Andreas Enge
2016-04-20 16:40 ` Ludovic Courtès
2016-04-23 7:55 ` Danny Milosavljevic
1 sibling, 1 reply; 32+ messages in thread
From: Andreas Enge @ 2016-04-19 19:54 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Albin, 23286
On Thu, Apr 14, 2016 at 06:50:32PM +0200, Ludovic Courtès wrote:
> (operating-system
> ;; …
> (services (cons (screen-locker-service "xscreensaver")
> %desktop-services)))
> Could you try and report back?
> I guess we’ll enable it by default in %desktop-services.
Will this be compatible with our desktop environments, xfce4 and gnome?
Andreas
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-19 19:54 ` Andreas Enge
@ 2016-04-20 16:40 ` Ludovic Courtès
0 siblings, 0 replies; 32+ messages in thread
From: Ludovic Courtès @ 2016-04-20 16:40 UTC (permalink / raw)
To: Andreas Enge; +Cc: Albin, 23286
Andreas Enge <andreas@enge.fr> skribis:
> On Thu, Apr 14, 2016 at 06:50:32PM +0200, Ludovic Courtès wrote:
>> (operating-system
>> ;; …
>> (services (cons (screen-locker-service "xscreensaver")
>> %desktop-services)))
>> Could you try and report back?
>> I guess we’ll enable it by default in %desktop-services.
>
> Will this be compatible with our desktop environments, xfce4 and gnome?
Yes (this service simply adds a PAM entry and a setuid binary.)
Ludo’.
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-14 16:50 ` Ludovic Courtès
2016-04-19 19:54 ` Andreas Enge
@ 2016-04-23 7:55 ` Danny Milosavljevic
2016-04-23 17:47 ` Albin
2016-04-24 13:47 ` Ludovic Courtès
1 sibling, 2 replies; 32+ messages in thread
From: Danny Milosavljevic @ 2016-04-23 7:55 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Albin, 23286
On Thu, 14 Apr 2016 18:50:32 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> As Chris Webber mentioned on the mailing list (IIRC), you’ll also have
> to enable xscreensaver in the OS config:
>
> (use-modules (gnu services xorg))
>
> (operating-system
> ;; …
> (services (cons (screen-locker-service "xscreensaver")
> %desktop-services)))
guix system: error: failed to load '/etc/config.scm':
gnu/services/xorg.scm:442:41: In procedure screen-locker-service:
gnu/services/xorg.scm:442:41: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): "xscreensaver"
To fix, use
(use-modules (gnu services xorg))
(use-package-modules .... xdisorg)
(operating-system
;; …
(services (cons (screen-locker-service xscreensaver)
%desktop-services)))
(i.e. without the doublequotes)
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 7:55 ` Danny Milosavljevic
@ 2016-04-23 17:47 ` Albin
2016-04-23 18:22 ` Danny Milosavljevic
2016-04-24 13:47 ` Ludovic Courtès
1 sibling, 1 reply; 32+ messages in thread
From: Albin @ 2016-04-23 17:47 UTC (permalink / raw)
To: Danny Milosavljevic, Ludovic Courtès; +Cc: 23286
Den 2016-04-23 kl. 09:55, skrev Danny Milosavljevic:
> On Thu, 14 Apr 2016 18:50:32 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>> As Chris Webber mentioned on the mailing list (IIRC), you’ll also have
>> to enable xscreensaver in the OS config:
>>
>> (use-modules (gnu services xorg))
>>
>> (operating-system
>> ;; …
>> (services (cons (screen-locker-service "xscreensaver")
>> %desktop-services)))
>
> guix system: error: failed to load '/etc/config.scm':
> gnu/services/xorg.scm:442:41: In procedure screen-locker-service:
> gnu/services/xorg.scm:442:41: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): "xscreensaver"
>
> To fix, use
>
> (use-modules (gnu services xorg))
> (use-package-modules .... xdisorg)
>
> (operating-system
> ;; …
> (services (cons (screen-locker-service xscreensaver)
> %desktop-services)))
>
> (i.e. without the doublequotes)
>
Danny, I tried your fix but it didn't work for me. I was able to run,
as root, `guix pull` + `guix system reconfigure` and log back in, but
when I try to unlock the screen my user password is refused.
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 17:47 ` Albin
@ 2016-04-23 18:22 ` Danny Milosavljevic
2016-04-23 18:28 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-04-23 18:22 UTC (permalink / raw)
To: Albin; +Cc: 23286
Hi,
weird. It works for me here. I did the same as you did. (although I'm using fluxbox)
What happens when you run
xlock
manually?
Can you unlock the screen there?
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 18:22 ` Danny Milosavljevic
@ 2016-04-23 18:28 ` Danny Milosavljevic
2016-04-23 20:15 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-04-23 18:28 UTC (permalink / raw)
To: Albin; +Cc: 23286
On Sat, 23 Apr 2016 20:22:52 +0200
Danny Milosavljevic <dannym@scratchpost.org> wrote:
> Hi,
>
> weird. It works for me here. I did the same as you did. (although I'm using fluxbox)
>
> What happens when you run
>
> xlock
>
> manually?
(just to clarify: as your normal user)
Also, what does
which xlock
say?
How about
ls -l $(which xlock)
?
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 18:28 ` Danny Milosavljevic
@ 2016-04-23 20:15 ` Albin
2016-04-24 1:14 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-04-23 20:15 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Den 2016-04-23 kl. 20:28, skrev Danny Milosavljevic:
> On Sat, 23 Apr 2016 20:22:52 +0200
> Danny Milosavljevic <dannym@scratchpost.org> wrote:
>
>> Hi,
>>
>> weird. It works for me here. I did the same as you did. (although I'm using fluxbox)
>>
>> What happens when you run
>>
>> xlock
>>
>> manually?
Hi!
This starts the screensaver and I'm now able to enter my password to
unlock. The unlock screen looks a bit different though.
> (just to clarify: as your normal user)
>
> Also, what does
>
> which xlock
>
> say?
/run/setuid-programs/xlock
>
> How about
>
> ls -l $(which xlock)
>
> ?
>
-r-sr-sr-x 3 root root 1684296 1 jan 1970 /run/setuid-programs/xlock
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 20:15 ` Albin
@ 2016-04-24 1:14 ` Danny Milosavljevic
2016-04-24 14:03 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-04-24 1:14 UTC (permalink / raw)
To: Albin; +Cc: 23286
On Sat, 23 Apr 2016 22:15:23 +0200
Albin <albin@fripost.org> wrote:
>This starts the screensaver and I'm now able to enter my password to unlock. The unlock screen looks a bit different though.
Just to be sure, are you saying that the unlocking works fine with that?
> > ls -l $(which xlock)
> -r-sr-sr-x 3 root root 1684296 1 jan 1970 /run/setuid-programs/xlock
> works
And what does
ls -l /run/setuid-programs/xscreensaver
say?
And
ps -ef |grep xscreensaver
?
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-24 1:14 ` Danny Milosavljevic
@ 2016-04-24 14:03 ` Albin
2016-04-26 21:17 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-04-24 14:03 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Hi again.
Den 2016-04-24 kl. 03:14, skrev Danny Milosavljevic:
> On Sat, 23 Apr 2016 22:15:23 +0200
> Albin <albin@fripost.org> wrote:
>
>> This starts the screensaver and I'm now able to enter my password to unlock. The unlock screen looks a bit different though.
>
> Just to be sure, are you saying that the unlocking works fine with that?
Yes, but it doesn't work with Xfce's native screen locking program xflock4.
>
>>> ls -l $(which xlock)
>> -r-sr-sr-x 3 root root 1684296 1 jan 1970 /run/setuid-programs/xlock
>
>> works
>
> And what does
>
> ls -l /run/setuid-programs/xscreensaver
>
> say?
-r-sr-sr-x 3 root root 266584 1 jan 1970 /run/setuid-programs/xscreensaver
>
> And
>
> ps -ef |grep xscreensaver
>
> ?
>
albin 419 386 0 16:56 ? 00:00:00 xscreensaver -no-splash
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-24 14:03 ` Albin
@ 2016-04-26 21:17 ` Danny Milosavljevic
2016-05-06 18:29 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-04-26 21:17 UTC (permalink / raw)
To: Albin; +Cc: 23286
Hi,
On Sun, 24 Apr 2016 16:03:38 +0200
Albin <albin@fripost.org> wrote:
> > Just to be sure, are you saying that the unlocking works fine with that?
>
> Yes, but it doesn't work with Xfce's native screen locking program xflock4.
Ah, then what does
ls -l $(which xflock4)
say?
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-26 21:17 ` Danny Milosavljevic
@ 2016-05-06 18:29 ` Albin
2016-05-18 18:44 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-06 18:29 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Sorry about the delay.
Den 2016-04-26 kl. 23:17, skrev Danny Milosavljevic:
> Hi,
>
> On Sun, 24 Apr 2016 16:03:38 +0200
> Albin <albin@fripost.org> wrote:
>
>>> Just to be sure, are you saying that the unlocking works fine with that?
>>
>> Yes, but it doesn't work with Xfce's native screen locking program xflock4.
>
> Ah, then what does
>
> ls -l $(which xflock4)
>
> say?
>
It says:
lrwxrwxrwx 4 root guixbuild 76 1 jan 1970
/run/current-system/profile/bin/xflock4 ->
/gnu/store/[...]-xfce-session-4.12.0/bin/xflock4
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-06 18:29 ` Albin
@ 2016-05-18 18:44 ` Danny Milosavljevic
2016-05-20 17:15 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-05-18 18:44 UTC (permalink / raw)
To: Albin; +Cc: 23286
> > ls -l $(which xflock4)
>
> It says:
>
> lrwxrwxrwx 4 root guixbuild 76 1 jan 1970
> /run/current-system/profile/bin/xflock4 ->
> /gnu/store/[...]-xfce-session-4.12.0/bin/xflock4
>
> Albin
And
ls -lL $(which xflock4)
?
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-18 18:44 ` Danny Milosavljevic
@ 2016-05-20 17:15 ` Albin
2016-05-20 17:48 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-20 17:15 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Den 2016-05-18 kl. 20:44, skrev Danny Milosavljevic:
>>> ls -l $(which xflock4)
>>
>> It says:
>>
>> lrwxrwxrwx 4 root guixbuild 76 1 jan 1970
>> /run/current-system/profile/bin/xflock4 ->
>> /gnu/store/[...]-xfce-session-4.12.0/bin/xflock4
>>
>> Albin
>
>
> And
>
> ls -lL $(which xflock4)
>
> ?
>
The output from that is:
-r-xr-xr-x 10 root root 1536 1 jan 1970
/run/current-system/profile/bin/xflock4
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 17:15 ` Albin
@ 2016-05-20 17:48 ` Danny Milosavljevic
2016-05-20 20:22 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-05-20 17:48 UTC (permalink / raw)
To: Albin; +Cc: 23286
On Fri, 20 May 2016 19:15:06 +0200
Albin <albin@fripost.org> wrote:
> > ls -lL $(which xflock4)
> The output from that is:
>
> -r-xr-xr-x 10 root root 1536 1 jan 1970
> /run/current-system/profile/bin/xflock4
>
>
> Albin
Aha!
Add (screen-locker-service xfce4-session "xflock4") to your services in your guix config file.
This means:
(operating-system
......
(services (cons* (screen-locker-service xfce4-session "xflock4") %desktop-services)))
Or add it to an existing "services" entry.
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 17:48 ` Danny Milosavljevic
@ 2016-05-20 20:22 ` Albin
2016-05-20 18:28 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-20 20:22 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Den Fri, 20 May 2016 19:48:49 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> On Fri, 20 May 2016 19:15:06 +0200
> Albin <albin@fripost.org> wrote:
>
> > > ls -lL $(which xflock4)
> > The output from that is:
> >
> > -r-xr-xr-x 10 root root 1536 1 jan 1970
> > /run/current-system/profile/bin/xflock4
> >
> >
> > Albin
>
> Aha!
>
> Add (screen-locker-service xfce4-session "xflock4") to your services
> in your guix config file.
>
> This means:
>
> (operating-system
> ......
> (services (cons* (screen-locker-service xfce4-session "xflock4")
> %desktop-services)))
>
> Or add it to an existing "services" entry.
When I try to reconfigure with this I get:
guix system: error: failed to load '/etc/config.scm':
/etc/config.scm:56:19: In procedure #<procedure 3cf9820 ()>:
/etc/config.scm:56:19: In procedure module-lookup: Unbound variable:
xfce4-session
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 20:22 ` Albin
@ 2016-05-20 18:28 ` Danny Milosavljevic
2016-05-20 18:42 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-05-20 18:28 UTC (permalink / raw)
To: Albin; +Cc: 23286
On Fri, 20 May 2016 22:22:01 +0200
Albin <albin@fripost.org> wrote:
> Den Fri, 20 May 2016 19:48:49 +0200
> skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
>
> > On Fri, 20 May 2016 19:15:06 +0200
> > Albin <albin@fripost.org> wrote:
> >
> > > > ls -lL $(which xflock4)
> > > The output from that is:
> > >
> > > -r-xr-xr-x 10 root root 1536 1 jan 1970
> > > /run/current-system/profile/bin/xflock4
> >
> > Add (screen-locker-service xfce4-session "xflock4") to your services
> > in your guix config file.
> >
> > This means:
> >
> > (operating-system
> > ......
> > (services (cons* (screen-locker-service xfce4-session "xflock4")
> > %desktop-services)))
> >
> > Or add it to an existing "services" entry.
>
> When I try to reconfigure with this I get:
>
> guix system: error: failed to load '/etc/config.scm':
> /etc/config.scm:56:19: In procedure #<procedure 3cf9820 ()>:
> /etc/config.scm:56:19: In procedure module-lookup: Unbound variable:
> xfce4-session
Extend use-package-modules so that it contains xfce:
(use-package-modules xfce .....)
If you have no "use-package-modules" form, it's supposed to go at the toplevel.
>Do you mean as a replacement for "screen-locker-service xscreensaver" or an additional service?
I don't think it makes a difference. It should support multiple instances just fine.
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 18:28 ` Danny Milosavljevic
@ 2016-05-20 18:42 ` Danny Milosavljevic
2016-05-20 22:36 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-05-20 18:42 UTC (permalink / raw)
To: Albin; +Cc: 23286
Errr. Oops. Better not do what I said previously (at least not permanently).
Danny said:
> services (cons* (screen-locker-service xfce4-session "xflock4")
Because of [1], that is maybe not the right fix (however, it should work).
Can you do
$ cat $(which xflock4)
please?
It seems to be a wrapper that just uses other tools to do the actual locking. Which ones?
It might be that it doesn't find xscreensaver-common but does find gnome-screensaver-command in your profile. Either way it's using something to lock the screen which then won't be able to unlock.
[1] https://unix.stackexchange.com/questions/101806/why-doesnt-my-screen-lock-in-xfce
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 18:42 ` Danny Milosavljevic
@ 2016-05-20 22:36 ` Albin
2016-05-21 4:37 ` Danny Milosavljevic
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-20 22:36 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Den Fri, 20 May 2016 20:42:09 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> Errr. Oops. Better not do what I said previously (at least not
> permanently).
>
> Danny said:
> > services (cons* (screen-locker-service xfce4-session "xflock4")
>
> Because of [1], that is maybe not the right fix (however, it should
> work).
Yes, it didn't work. I got the same problem as before with an
automatic authentication failure.
>
> Can you do
>
> $ cat $(which xflock4)
>
> please?
Sure. See the attached file.
Thanks
Albin
>
> It seems to be a wrapper that just uses other tools to do the actual
> locking. Which ones?
>
> It might be that it doesn't find xscreensaver-common but does find
> gnome-screensaver-command in your profile. Either way it's using
> something to lock the screen which then won't be able to unlock.
>
> [1]
> https://unix.stackexchange.com/questions/101806/why-doesnt-my-screen-lock-in-xfce
[-- Attachment #2: cat-xflock4 --]
[-- Type: application/octet-stream, Size: 1536 bytes --]
#!/gnu/store/b1yqjimbdh5bf9jnizd4h7yf110744j2-bash-4.3.42/bin/sh
#
# xfce4
#
# Copyright (C) 1999, 2003 Olivier Fourdan (fourdan@xfce.org)
# Copyright (C) 2011 Guido Berhoerster (guido+xfce.org@berhoerster.name)
# Copyright (C) 2011 Jarno Suni (8@iki.fi)
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
# Lock by xscreensaver or gnome-screensaver, if a respective daemon is running
for lock_cmd in \
"xscreensaver-command -lock" \
"gnome-screensaver-command --lock"
do
$lock_cmd >/dev/null 2>&1 && exit
done
# else run another access locking utility, if installed
for lock_cmd in \
"xlock -mode blank" \
"slock"
do
set -- $lock_cmd
if command -v -- $1 >/dev/null 2>&1; then
$lock_cmd >/dev/null 2>&1 &
# turn off display backlight:
xset dpms force off
exit
fi
done
# else access locking failed
exit 1
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-20 22:36 ` Albin
@ 2016-05-21 4:37 ` Danny Milosavljevic
2016-05-21 8:35 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Danny Milosavljevic @ 2016-05-21 4:37 UTC (permalink / raw)
To: Albin; +Cc: 23286
On Sat, 21 May 2016 00:36:29 +0200
Albin <albin@fripost.org> wrote:
Ok, then let's try to find out which locker xflock4 actually uses (from the file you attached).
To recap, when you call
$ xflock4
manually it locks but doesn't allow you to unlock, right?
Please try to call these manually (in that order) and stop at the first one that doesn't throw an error:
$ xscreensaver-command -lock
$ gnome-screensaver-command --lock
$ xlock -mode blank
$ slock
Which one was it?
(It will probably still be unable to unlock)
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-21 4:37 ` Danny Milosavljevic
@ 2016-05-21 8:35 ` Albin
2016-05-22 21:43 ` Ludovic Courtès
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-21 8:35 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: 23286
Den Sat, 21 May 2016 06:37:49 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> On Sat, 21 May 2016 00:36:29 +0200
> Albin <albin@fripost.org> wrote:
>
> Ok, then let's try to find out which locker xflock4 actually uses
> (from the file you attached).
>
> To recap, when you call
>
> $ xflock4
>
> manually it locks but doesn't allow you to unlock, right?
Right.
>
> Please try to call these manually (in that order) and stop at the
> first one that doesn't throw an error:
>
> $ xscreensaver-command -lock
Unable to unlock.
> $ gnome-screensaver-command --lock
Command not found.
> $ xlock -mode blank
Worked. ('xlock' also worked.)
> $ slock
Worked.
>
> Which one was it?
>
> (It will probably still be unable to unlock)
Now what? :)
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-21 8:35 ` Albin
@ 2016-05-22 21:43 ` Ludovic Courtès
2016-05-22 21:56 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Ludovic Courtès @ 2016-05-22 21:43 UTC (permalink / raw)
To: Albin; +Cc: 23286
Albin <albin@fripost.org> skribis:
> Den Sat, 21 May 2016 06:37:49 +0200
[...]
>> Please try to call these manually (in that order) and stop at the
>> first one that doesn't throw an error:
>>
>> $ xscreensaver-command -lock
>
> Unable to unlock.
>
>> $ gnome-screensaver-command --lock
>
> Command not found.
>
>> $ xlock -mode blank
>
> Worked. ('xlock' also worked.)
>
>> $ slock
>
> Worked.
IIUC, xfce-lock uses one of the above lockers. For them to work, and if
you want to be able to unlock your screen ;-), you need to make sure you
use ‘screen-locker-service’ for each of them.
So:
(operating-system
;; …
(services (cons (screen-locker-service xscreensaver)
%desktop-services)))
since ‘%desktop-services’ already takes care of slock and xlock.
Could you try and report back? We’re getting there! :-)
Ludo’.
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-22 21:43 ` Ludovic Courtès
@ 2016-05-22 21:56 ` Albin
2016-05-23 8:11 ` Ludovic Courtès
0 siblings, 1 reply; 32+ messages in thread
From: Albin @ 2016-05-22 21:56 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 23286
Den Sun, 22 May 2016 23:43:14 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> Albin <albin@fripost.org> skribis:
>
> > Den Sat, 21 May 2016 06:37:49 +0200
>
> [...]
>
> >> Please try to call these manually (in that order) and stop at the
> >> first one that doesn't throw an error:
> >>
> >> $ xscreensaver-command -lock
> >
> > Unable to unlock.
> >
> >> $ gnome-screensaver-command --lock
> >
> > Command not found.
> >
> >> $ xlock -mode blank
> >
> > Worked. ('xlock' also worked.)
> >
> >> $ slock
> >
> > Worked.
>
> IIUC, xfce-lock uses one of the above lockers. For them to work, and
> if you want to be able to unlock your screen ;-), you need to make
> sure you use ‘screen-locker-service’ for each of them.
>
> So:
>
> (operating-system
> ;; …
> (services (cons (screen-locker-service xscreensaver)
> %desktop-services)))
>
This was my original configuration which didn't let me unlock if I had
locked with xflock4. Any other ideas?
> since ‘%desktop-services’ already takes care of slock and xlock.
>
> Could you try and report back? We’re getting there! :-)
I hope so! :)
>
> Ludo’.
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-22 21:56 ` Albin
@ 2016-05-23 8:11 ` Ludovic Courtès
2016-05-23 20:18 ` Albin
0 siblings, 1 reply; 32+ messages in thread
From: Ludovic Courtès @ 2016-05-23 8:11 UTC (permalink / raw)
To: Albin; +Cc: 23286
Albin <albin@fripost.org> skribis:
> Den Sun, 22 May 2016 23:43:14 +0200
> skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
>
>> Albin <albin@fripost.org> skribis:
>>
>> > Den Sat, 21 May 2016 06:37:49 +0200
>>
>> [...]
>>
>> >> Please try to call these manually (in that order) and stop at the
>> >> first one that doesn't throw an error:
>> >>
>> >> $ xscreensaver-command -lock
>> >
>> > Unable to unlock.
>> >
>> >> $ gnome-screensaver-command --lock
>> >
>> > Command not found.
>> >
>> >> $ xlock -mode blank
>> >
>> > Worked. ('xlock' also worked.)
>> >
>> >> $ slock
>> >
>> > Worked.
>>
>> IIUC, xfce-lock uses one of the above lockers. For them to work, and
>> if you want to be able to unlock your screen ;-), you need to make
>> sure you use ‘screen-locker-service’ for each of them.
>>
>> So:
>>
>> (operating-system
>> ;; …
>> (services (cons (screen-locker-service xscreensaver)
>> %desktop-services)))
>>
>
> This was my original configuration which didn't let me unlock if I had
> locked with xflock4. Any other ideas?
Oh wait; since the command is called “xscreensaver-command”, not
“xscreensaver” (well in fact there are both), this should be:
(cons (screen-locker-service xscreensaver "xscreensaver-command")
%desktop-services)
Could you try this one?
Thanks for your patience. :-)
Ludo’.
^ permalink raw reply [flat|nested] 32+ messages in thread* bug#23286: Unable to unlock xscreensaver in Xfce
2016-05-23 8:11 ` Ludovic Courtès
@ 2016-05-23 20:18 ` Albin
0 siblings, 0 replies; 32+ messages in thread
From: Albin @ 2016-05-23 20:18 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 23286
Den Mon, 23 May 2016 10:11:27 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> Albin <albin@fripost.org> skribis:
>
> > Den Sun, 22 May 2016 23:43:14 +0200
> > skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:
> >
> >> Albin <albin@fripost.org> skribis:
> >>
> >> > Den Sat, 21 May 2016 06:37:49 +0200
> >>
> >> [...]
> >>
> >> >> Please try to call these manually (in that order) and stop at
> >> >> the first one that doesn't throw an error:
> >> >>
> >> >> $ xscreensaver-command -lock
> >> >
> >> > Unable to unlock.
> >> >
> >> >> $ gnome-screensaver-command --lock
> >> >
> >> > Command not found.
> >> >
> >> >> $ xlock -mode blank
> >> >
> >> > Worked. ('xlock' also worked.)
> >> >
> >> >> $ slock
> >> >
> >> > Worked.
> >>
> >> IIUC, xfce-lock uses one of the above lockers. For them to work,
> >> and if you want to be able to unlock your screen ;-), you need to
> >> make sure you use ‘screen-locker-service’ for each of them.
> >>
> >> So:
> >>
> >> (operating-system
> >> ;; …
> >> (services (cons (screen-locker-service xscreensaver)
> >> %desktop-services)))
> >>
> >
> > This was my original configuration which didn't let me unlock if I
> > had locked with xflock4. Any other ideas?
>
> Oh wait; since the command is called “xscreensaver-command”, not
> “xscreensaver” (well in fact there are both), this should be:
>
> (cons (screen-locker-service xscreensaver "xscreensaver-command")
> %desktop-services)
>
> Could you try this one?
>
It didn't work. I got the same authentication error when tried to
unlock.
> Thanks for your patience. :-)
Likewise! :)
>
> Ludo’.
Albin
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Unable to unlock xscreensaver in Xfce
2016-04-23 7:55 ` Danny Milosavljevic
2016-04-23 17:47 ` Albin
@ 2016-04-24 13:47 ` Ludovic Courtès
1 sibling, 0 replies; 32+ messages in thread
From: Ludovic Courtès @ 2016-04-24 13:47 UTC (permalink / raw)
To: Danny Milosavljevic; +Cc: Albin, 23286
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Thu, 14 Apr 2016 18:50:32 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>> As Chris Webber mentioned on the mailing list (IIRC), you’ll also have
>> to enable xscreensaver in the OS config:
>>
>> (use-modules (gnu services xorg))
>>
>> (operating-system
>> ;; …
>> (services (cons (screen-locker-service "xscreensaver")
>> %desktop-services)))
>
> guix system: error: failed to load '/etc/config.scm':
> gnu/services/xorg.scm:442:41: In procedure screen-locker-service:
> gnu/services/xorg.scm:442:41: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): "xscreensaver"
Oops, my bad: this should be
(use-modules (gnu services xorg) (gnu packages xdisorg))
(operating-system
;; …
(services (cons (screen-locker-service xscreensaver)
%desktop-services)))
where ‘xscreensaver’ is a reference to the ‘xscreensaver’ variable
exported by the (gnu packages xdisorg) module.
Ludo’.
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Hunting #23286: Unable to unlock xscreensaver in Xfce
2016-04-13 21:16 bug#23286: Unable to unlock xscreensaver in Xfce Albin
2016-04-14 16:50 ` Ludovic Courtès
@ 2020-02-18 14:26 ` zimoun
2020-02-18 21:41 ` raingloom
2020-02-25 20:39 ` Albin
1 sibling, 2 replies; 32+ messages in thread
From: zimoun @ 2020-02-18 14:26 UTC (permalink / raw)
To: Albin, 23286
Dear,
The bug #23286 is more than 3 years old.
What is the status?
Any progress? :-)
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23286
All the best,
simon
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Hunting #23286: Unable to unlock xscreensaver in Xfce
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
@ 2020-02-18 21:41 ` raingloom
2020-02-18 22:38 ` zimoun
2020-02-25 20:39 ` Albin
1 sibling, 1 reply; 32+ messages in thread
From: raingloom @ 2020-02-18 21:41 UTC (permalink / raw)
To: 23286
Is this also why i3lock can't be unlocked?
On Tue, Feb 18, 2020 at 15:26, zimoun <zimon.toutoune@gmail.com> wrote:
> Dear,
>
> The bug #23286 is more than 3 years old.
> What is the status?
> Any progress? :-)
>
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23286
>
> All the best,
> simon
>
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Hunting #23286: Unable to unlock xscreensaver in Xfce
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
2020-02-18 21:41 ` raingloom
@ 2020-02-25 20:39 ` Albin
2020-02-28 11:53 ` zimoun
1 sibling, 1 reply; 32+ messages in thread
From: Albin @ 2020-02-25 20:39 UTC (permalink / raw)
To: zimoun, 23286
Dear Simon,
I'm not using GNU Guix anymore so I'm afraid I can't answer your question.
Best,
Albin
On 2020-02-18 15:26, zimoun wrote:
> Dear,
>
> The bug #23286 is more than 3 years old.
> What is the status?
> Any progress? :-)
>
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23286
>
> All the best,
> simon
>
^ permalink raw reply [flat|nested] 32+ messages in thread
* bug#23286: Hunting #23286: Unable to unlock xscreensaver in Xfce
2020-02-25 20:39 ` Albin
@ 2020-02-28 11:53 ` zimoun
0 siblings, 0 replies; 32+ messages in thread
From: zimoun @ 2020-02-28 11:53 UTC (permalink / raw)
To: Albin; +Cc: 23286-done
Dear Albin,
On Tue, 25 Feb 2020 at 21:40, Albin <albin@fripost.org> wrote:
> I'm not using GNU Guix anymore so I'm afraid I can't answer your question.
I am sad to learn that you had switched to another system.
Well, because it was tagged 'moreinfo' on Monday April, 18th 2016 --
almost 4 years ago -- and the last activity was on May, 23rd 2016; and
the user that reported the issue -- probably local to their own
configuration -- does not run Guix anymore; and because the screen
locking service seems working elsewhere, then I am closing this bug.
Fell free to reopen it if you hit it again.
All the best,
simon
> > [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23286
^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~2020-02-28 11:54 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-13 21:16 bug#23286: Unable to unlock xscreensaver in Xfce Albin
2016-04-14 16:50 ` Ludovic Courtès
2016-04-19 19:54 ` Andreas Enge
2016-04-20 16:40 ` Ludovic Courtès
2016-04-23 7:55 ` Danny Milosavljevic
2016-04-23 17:47 ` Albin
2016-04-23 18:22 ` Danny Milosavljevic
2016-04-23 18:28 ` Danny Milosavljevic
2016-04-23 20:15 ` Albin
2016-04-24 1:14 ` Danny Milosavljevic
2016-04-24 14:03 ` Albin
2016-04-26 21:17 ` Danny Milosavljevic
2016-05-06 18:29 ` Albin
2016-05-18 18:44 ` Danny Milosavljevic
2016-05-20 17:15 ` Albin
2016-05-20 17:48 ` Danny Milosavljevic
2016-05-20 20:22 ` Albin
2016-05-20 18:28 ` Danny Milosavljevic
2016-05-20 18:42 ` Danny Milosavljevic
2016-05-20 22:36 ` Albin
2016-05-21 4:37 ` Danny Milosavljevic
2016-05-21 8:35 ` Albin
2016-05-22 21:43 ` Ludovic Courtès
2016-05-22 21:56 ` Albin
2016-05-23 8:11 ` Ludovic Courtès
2016-05-23 20:18 ` Albin
2016-04-24 13:47 ` Ludovic Courtès
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
2020-02-18 21:41 ` raingloom
2020-02-18 22:38 ` zimoun
2020-02-25 20:39 ` Albin
2020-02-28 11:53 ` zimoun
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).