Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bugzilla DB migration completed. Please report issues to Infra team via email via infra@gentoo.org or IRC
Bug 604624 - xfce-base/xfce4-session requires some screen lock manager to be installed
Summary: xfce-base/xfce4-session requires some screen lock manager to be installed
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-04 10:10 UTC by Uwe Sauter
Modified: 2019-07-10 19:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Sauter 2017-01-04 10:10:05 UTC
With the deprecation of x11-misc/alock-94 I removed alock from my system. Now I cannot lock my screen. I'm using XFCE and configured the shortcut Ctrl-Alt-Del to call "xflock4".

Looking at the strace of xflock4 there are stat calls that look for an installed screen lock program:

# strace xflock4 | grep stat | grep lock
stat("/bin/light-locker-command", 0x7ffd9b27e1b0) = -1 ENOENT (No such file or directory)
stat("/usr/bin/light-locker-command", 0x7ffd9b27e1b0) = -1 ENOENT (No such file or directory)
stat("/bin/xlock", 0x7ffd9b27e000)      = -1 ENOENT (No such file or directory)
stat("/usr/bin/xlock", 0x7ffd9b27e000)  = -1 ENOENT (No such file or directory)
stat("/bin/slock", 0x7ffd9b27e000)      = -1 ENOENT (No such file or directory)
stat("/usr/bin/slock", 0x7ffd9b27e000)  = -1 ENOENT (No such file or directory)
stat("/bin/alock", 0x7ffd9b27e000)      = -1 ENOENT (No such file or directory)
stat("/usr/bin/alock", 0x7ffd9b27e000)  = -1 ENOENT (No such file or directory)

None of the above commands (light-locker-command, xlock, slock, alock) is a dependency of xfce-base/xfce4-session which contains xflock4.

To work properly, at least one of the following packages should be installed as dependency of xfce4-session:

x11-misc/alock
x11-misc/light-locker
x11-misc/slock
x11-misc/xlockmore
x11-misc/xscreensaver
Comment 1 J L 2019-07-10 19:22:56 UTC
I came across this bug after a new install of Xfce (unstable) when trying to figure out why xscreensaver was installed on my system.

Looking at the xflock4 code (https://git.xfce.org/xfce/xfce4-session/tree/scripts/xflock4), the script first checks the session's xfconf channel for the command to be run (/general/LockCommand). If there is none, it will try, in order, xfce4-screesaver, xscreensaver, gnome-screensaver, xlock, slock, etc. From my testing, a fresh Xfce session does not appear to set anything in /general/LockComand.

Since xfce4-screensaver is actively maintained and well integrated in the Xfce project, I would request we pull in xfce4-screensaver as the default when emerging xfce4-session, unless the user manually sets the xscreensaver USE flag.
Comment 2 Denis Dupeyron gentoo-dev 2019-07-10 19:41:31 UTC
(In reply to leopard from comment #1)
> Since xfce4-screensaver is actively maintained and well integrated in the
> Xfce project, I would request we pull in xfce4-screensaver as the default
> when emerging xfce4-session, unless the user manually sets the xscreensaver
> USE flag.

Not really an acceptable solution since xfce4-screensaver is experimental and far from finished yet, and is hardly what every user wants or likes. A virtual would be the right solution.

Also, light-locker needs to be reintegrated to the list of acceptable choices as it was removed for very dubious reasons and is not dead at all, unlike others in the list.