Unable to unlock xscreensaver in Xfce

  • Done
  • quality assurance status badge
Details
6 participants
  • Albin
  • Andreas Enge
  • Danny Milosavljevic
  • Ludovic Courtès
  • raingloom
  • zimoun
Owner
unassigned
Submitted by
Albin
Severity
normal
A
(address . bug-guix@gnu.org)
570EB72F.9060101@fripost.org
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
L
L
Ludovic Courtès wrote on 14 Apr 2016 18:50
(name . Albin)(address . albin@fripost.org)(address . 23286@debbugs.gnu.org)
87lh4gm8x3.fsf@gnu.org
Albin <albin@fripost.org> skribis:

Toggle quote (12 lines)
> 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’.
L
L
Ludovic Courtès wrote on 18 Apr 2016 16:45
control message for bug #23286
(address . control@debbugs.gnu.org)
87potn3rhu.fsf@gnu.org
tags 23286 moreinfo
A
A
Andreas Enge wrote on 19 Apr 2016 21:54
Re: bug#23286: Unable to unlock xscreensaver in Xfce
(name . Ludovic Courtès)(address . ludo@gnu.org)
20160419195404.GA5418@solar
On Thu, Apr 14, 2016 at 06:50:32PM +0200, Ludovic Courtès wrote:
Toggle quote (7 lines)
> (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
L
L
Ludovic Courtès wrote on 20 Apr 2016 18:40
(name . Andreas Enge)(address . andreas@enge.fr)
87oa94s07x.fsf@gnu.org
Andreas Enge <andreas@enge.fr> skribis:

Toggle quote (10 lines)
> 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’.
D
D
Danny Milosavljevic wrote on 23 Apr 2016 09:55
(name . Ludovic Courtès)(address . ludo@gnu.org)
20160423095509.46afe0e7@scratchpost.org
On Thu, 14 Apr 2016 18:50:32 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
Toggle quote (10 lines)
> 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)
A
(address . 23286@debbugs.gnu.org)
571BB528.7090801@fripost.org
Den 2016-04-23 kl. 09:55, skrev Danny Milosavljevic:
Toggle quote (29 lines)
> 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
D
D
Danny Milosavljevic wrote on 23 Apr 2016 20:22
(name . Albin)(address . albin@fripost.org)
20160423202252.4802df28@scratchpost.org
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?
D
D
Danny Milosavljevic wrote on 23 Apr 2016 20:28
(name . Albin)(address . albin@fripost.org)
20160423202816.1412a0cc@scratchpost.org
On Sat, 23 Apr 2016 20:22:52 +0200
Danny Milosavljevic <dannym@scratchpost.org> wrote:

Toggle quote (10 lines)
> 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)

?
A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
571BD7DB.7060606@fripost.org
Den 2016-04-23 kl. 20:28, skrev Danny Milosavljevic:
Toggle quote (13 lines)
> 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.

Toggle quote (8 lines)
> (just to clarify: as your normal user)
>
> Also, what does
>
> which xlock
>
> say?

/run/setuid-programs/xlock

Toggle quote (8 lines)
>
> How about
>
> ls -l $(which xlock)
>
> ?
>

-r-sr-sr-x 3 root root 1684296 1 jan 1970 /run/setuid-programs/xlock

Albin
D
D
Danny Milosavljevic wrote on 24 Apr 2016 03:14
(name . Albin)(address . albin@fripost.org)
20160424031423.22ef23ad@scratchpost.org
On Sat, 23 Apr 2016 22:15:23 +0200
Albin <albin@fripost.org> wrote:

Toggle quote (2 lines)
>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?

Toggle quote (5 lines)
> > 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

?
L
L
Ludovic Courtès wrote on 24 Apr 2016 15:47
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
8760v7jezb.fsf@gnu.org
Danny Milosavljevic <dannym@scratchpost.org> skribis:

Toggle quote (16 lines)
> 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’.
A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
571CD23A.1070208@fripost.org
Hi again.

Den 2016-04-24 kl. 03:14, skrev Danny Milosavljevic:
Toggle quote (7 lines)
> 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.

Toggle quote (12 lines)
>
>>> 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

Toggle quote (8 lines)
>
> And
>
> ps -ef |grep xscreensaver
>
> ?
>

albin 419 386 0 16:56 ? 00:00:00 xscreensaver -no-splash


Albin
D
D
Danny Milosavljevic wrote on 26 Apr 2016 23:17
(name . Albin)(address . albin@fripost.org)
20160426231752.5355f72b@scratchpost.org
Hi,

On Sun, 24 Apr 2016 16:03:38 +0200
Albin <albin@fripost.org> wrote:

Toggle quote (4 lines)
> > 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?
A
A
Albin wrote on 6 May 2016 20:29
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
572CE293.5080400@fripost.org
Sorry about the delay.

Den 2016-04-26 kl. 23:17, skrev Danny Milosavljevic:
Toggle quote (16 lines)
> 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
D
D
Danny Milosavljevic wrote on 18 May 2016 20:44
(name . Albin)(address . albin@fripost.org)
20160518204439.31571a4c@scratchpost.org
Toggle quote (11 lines)
> > 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)

?
A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
573F461A.9010904@fripost.org
Den 2016-05-18 kl. 20:44, skrev Danny Milosavljevic:
Toggle quote (18 lines)
>>> 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
D
D
Danny Milosavljevic wrote on 20 May 2016 19:48
(name . Albin)(address . albin@fripost.org)
20160520194849.4bae25b7@scratchpost.org
On Fri, 20 May 2016 19:15:06 +0200
Albin <albin@fripost.org> wrote:

Toggle quote (9 lines)
> > 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.
A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
20160520222201.7b52e715@fripost.org
Den Fri, 20 May 2016 19:48:49 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Toggle quote (26 lines)
> 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
D
D
Danny Milosavljevic wrote on 20 May 2016 20:28
(name . Albin)(address . albin@fripost.org)
20160520202848.460abd5d@scratchpost.org
On Fri, 20 May 2016 22:22:01 +0200
Albin <albin@fripost.org> wrote:

Toggle quote (31 lines)
> 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.

Toggle quote (2 lines)
>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.
D
D
Danny Milosavljevic wrote on 20 May 2016 20:42
(name . Albin)(address . albin@fripost.org)
20160520204209.75bbfb60@scratchpost.org
Errr. Oops. Better not do what I said previously (at least not permanently).

Danny said:
Toggle quote (2 lines)
> 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.

A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
20160521003629.0796482e@fripost.org
Den Fri, 20 May 2016 20:42:09 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Toggle quote (9 lines)
> 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.

Toggle quote (7 lines)
>
> Can you do
>
> $ cat $(which xflock4)
>
> please?

Sure. See the attached file.

Thanks

Albin

Toggle quote (10 lines)
>
> 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: cat-xflock4
D
D
Danny Milosavljevic wrote on 21 May 2016 06:37
(name . Albin)(address . albin@fripost.org)
20160521063749.4bfd1a4d@scratchpost.org
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)
A
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
20160521103559.4c4d11ff@fripost.org
Den Sat, 21 May 2016 06:37:49 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Toggle quote (12 lines)
> 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.

Toggle quote (6 lines)
>
> 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.

Toggle quote (2 lines)
> $ gnome-screensaver-command --lock

Command not found.

Toggle quote (2 lines)
> $ xlock -mode blank

Worked. ('xlock' also worked.)

Toggle quote (2 lines)
> $ slock

Worked.

Toggle quote (5 lines)
>
> Which one was it?
>
> (It will probably still be unable to unlock)

Now what? :)

Albin
L
L
Ludovic Courtès wrote on 22 May 2016 23:43
(name . Albin)(address . albin@fripost.org)
87zirhojkd.fsf@gnu.org
Albin <albin@fripost.org> skribis:

Toggle quote (2 lines)
> Den Sat, 21 May 2016 06:37:49 +0200

[...]

Toggle quote (19 lines)
>> 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’.
A
(name . Ludovic Courtès)(address . ludo@gnu.org)
20160522235645.6896525f@fripost.org
Den Sun, 22 May 2016 23:43:14 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Toggle quote (37 lines)
> 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?

Toggle quote (4 lines)
> since ‘%desktop-services’ already takes care of slock and xlock.
>
> Could you try and report back? We’re getting there! :-)

I hope so! :)

Toggle quote (3 lines)
>
> Ludo’.

Albin
L
L
Ludovic Courtès wrote on 23 May 2016 10:11
(name . Albin)(address . albin@fripost.org)
87bn3xkxcg.fsf@gnu.org
Albin <albin@fripost.org> skribis:

Toggle quote (43 lines)
> 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’.
A
(name . Ludovic Courtès)(address . ludo@gnu.org)
20160523221823.7636bae3@fripost.org
Den Mon, 23 May 2016 10:11:27 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Toggle quote (54 lines)
> 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.

Toggle quote (2 lines)
> Thanks for your patience. :-)

Likewise! :)

Toggle quote (3 lines)
>
> Ludo’.

Albin
Z
R
R
raingloom wrote on 18 Feb 2020 22:41
(address . 23286@debbugs.gnu.org)
1582062067.1392.0@riseup.net
Is this also why i3lock can't be unlocked?

On Tue, Feb 18, 2020 at 15:26, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (14 lines)
> 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
>
>
>
Z
Z
zimoun wrote on 18 Feb 2020 23:38
(name . raingloom)(address . raingloom@riseup.net)(address . 23286@debbugs.gnu.org)
CAJ3okZ1wbvxqneH+zVCT9yakvRCqui1Qo-f0mMEZC2i2KnWGKQ@mail.gmail.com
On Tue, 18 Feb 2020 at 22:42, raingloom <raingloom@riseup.net> wrote:

Toggle quote (2 lines)
> Is this also why i3lock can't be unlocked?

I do not know.

Have you tried the initial fix and the Danny's updated one?



All the best,
simon
A
Re: Hunting #23286: Unable to unlock xscreensaver in Xfce
a42f97b3-e279-8824-911a-d62277254ebf@fripost.org
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:
Toggle quote (12 lines)
> 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
>
Z
Z
zimoun wrote on 28 Feb 2020 12:53
(name . Albin)(address . albin@fripost.org)(address . 23286-done@debbugs.gnu.org)
CAJ3okZ0VAnE9ki4rS0Qsszd5ETUo8qzs3ydrr4oR_dPp+MAugQ@mail.gmail.com
Dear Albin,

On Tue, 25 Feb 2020 at 21:40, Albin <albin@fripost.org> wrote:

Toggle quote (2 lines)
> 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

Toggle quote (1 lines)
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 23286@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 23286
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch