Unable to unlock xscreensaver in Xfce

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

Albin <albin@fripost.org> skribis:

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’.

tags 23286 moreinfo

On Thu, Apr 14, 2016 at 06:50:32PM +0200, Ludovic Courtès wrote:

Will this be compatible with our desktop environments, xfce4 and gnome?

Andreas

Andreas Enge <andreas@enge.fr> skribis:

Yes (this service simply adds a PAM entry and a setuid binary.)

Ludo’.

On Thu, 14 Apr 2016 18:50:32 +0200

ludo@gnu.org (Ludovic Courtès) wrote:

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)

Den 2016-04-23 kl. 09:55, skrev Danny Milosavljevic:

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

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?

On Sat, 23 Apr 2016 20:22:52 +0200

Danny Milosavljevic <dannym@scratchpost.org> wrote:

(just to clarify: as your normal user)

Also, what does

which xlock

say?

How about

ls -l $(which xlock)

?

Den 2016-04-23 kl. 20:28, skrev Danny Milosavljevic:

Hi!

This starts the screensaver and I'm now able to enter my password to

unlock. The unlock screen looks a bit different though.

/run/setuid-programs/xlock

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

Albin

On Sat, 23 Apr 2016 22:15:23 +0200

Albin <albin@fripost.org> wrote:

Just to be sure, are you saying that the unlocking works fine with that?

And what does

ls -l /run/setuid-programs/xscreensaver

say?

And

ps -ef |grep xscreensaver

?

Danny Milosavljevic <dannym@scratchpost.org> skribis:

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’.

Hi again.

Den 2016-04-24 kl. 03:14, skrev Danny Milosavljevic:

Yes, but it doesn't work with Xfce's native screen locking program xflock4.

-r-sr-sr-x 3 root root 266584 1 jan 1970 /run/setuid-programs/xscreensaver

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

Albin

Hi,

On Sun, 24 Apr 2016 16:03:38 +0200

Albin <albin@fripost.org> wrote:

Ah, then what does

ls -l $(which xflock4)

say?

Sorry about the delay.

Den 2016-04-26 kl. 23:17, skrev Danny Milosavljevic:

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)

?

Den 2016-05-18 kl. 20:44, skrev Danny Milosavljevic:

The output from that is:

-r-xr-xr-x 10 root root 1536 1 jan 1970

/run/current-system/profile/bin/xflock4

Albin

On Fri, 20 May 2016 19:15:06 +0200

Albin <albin@fripost.org> wrote:

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.

Den Fri, 20 May 2016 19:48:49 +0200

skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

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

On Fri, 20 May 2016 22:22:01 +0200

Albin <albin@fripost.org> wrote:

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.

I don't think it makes a difference. It should support multiple instances just fine.

Errr. Oops. Better not do what I said previously (at least not permanently).

Danny said:

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

Den Fri, 20 May 2016 20:42:09 +0200

skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Yes, it didn't work. I got the same problem as before with an

automatic authentication failure.

Sure. See the attached file.

Thanks

Albin

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)

Den Sat, 21 May 2016 06:37:49 +0200

skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

Right.

Unable to unlock.

Command not found.

Worked. ('xlock' also worked.)

Worked.

Now what? :)

Albin

Albin <albin@fripost.org> skribis:

[...]

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’.

Den Sun, 22 May 2016 23:43:14 +0200

skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

This was my original configuration which didn't let me unlock if I had

locked with xflock4. Any other ideas?

I hope so! :)

Albin

Albin <albin@fripost.org> skribis:

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’.

Den Mon, 23 May 2016 10:11:27 +0200

skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

It didn't work. I got the same authentication error when tried to

unlock.

Likewise! :)

Albin

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

Is this also why i3lock can't be unlocked?

On Tue, Feb 18, 2020 at 15:26, zimoun <zimon.toutoune@gmail.com> wrote:

On Tue, 18 Feb 2020 at 22:42, raingloom <raingloom@riseup.net> wrote:

I do not know.

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

All the best,

simon

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 Albin,

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

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