xfce4-screensaver issueshttps://gitlab.xfce.org/apps/xfce4-screensaver/-/issues2024-03-10T19:11:02Zhttps://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/147allow typing in password immediately instead of waiting for fingerprint scan ...2024-03-10T19:11:02ZAndy Schroderallow typing in password immediately instead of waiting for fingerprint scan to timeout.If you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, if the lock screen is waiting to scan a fingerprint, you can't type in your password u...If you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, if the lock screen is waiting to scan a fingerprint, you can't type in your password until the fingerprint scanning times out. You should be able to do either one at the same time. I think this is going to have to be fixed as part of https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/145 .https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/146fingerprint authentication doesn't always work when coming out of suspend mode2024-03-10T19:09:53ZAndy Schroderfingerprint authentication doesn't always work when coming out of suspend modeIf you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, sometimes fingerprint authentication is not available when coming out of suspend mode ...If you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, sometimes fingerprint authentication is not available when coming out of suspend mode and you can only type in a password.
I'm not sure why. This could be an issue with fprintd or the fingerprint reader not waking up by the time the lock screen comes up. Either way, I think the lock screen should keep checking for fprintd to be ready instead of having to unlock and relock again for the fingerprint reader to work again.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/145allow rescanning fingerprint without having to press escape twice2024-03-10T19:11:10ZAndy Schroderallow rescanning fingerprint without having to press escape twiceIf you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, if you don't scan within the timeout period of opening your laptop lid, you have to ei...If you follow https://wiki.debian.org/SecurityManagement/fingerprint%20authentication you get fingerprint authentication on the lock screen.
However, if you don't scan within the timeout period of opening your laptop lid, you have to either type in the password or hit escape once to blank the screen and then a second time to bring the login prompt back up. Once the login prompt is back up, then you have a chance to try to scan the fingerprint again.
This is also an issue if you have dirty or scratched fingers, you swipe the wrong finger, you don't center your finger over the reader, reader isn't accurate, etc.. Either laptop fingerprint readers aren't nearly as good as phone fingerprint readers or fprintd is just not very robust, not sure which it is, but needing to scan your fingerprint twice is a common issue and having to do the double escape trick is needed. Also, sometimes this happens on a phone too, but you can just quickly rescan and it is not as big of a nuisance.
I think there should be some limit to how many times you can scan though without having to wait an extra 10 seconds. Probably 5 or 10 times is excessive and could be considered a brute force attempt. Also, the double escape trick I mentioned above should probably require waiting an extra 10 seconds after done 5 or 10 times.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/142Option to ignore input for a set amount of time after activating2024-01-27T18:50:44Zdrws rwxOption to ignore input for a set amount of time after activatingIn setups where manual inhibition is used it would be very helpful if `xfce4-screensaver` could ignore input for a set amount of time after activating, to prevent catching unwanted input when mouse is put away for example.In setups where manual inhibition is used it would be very helpful if `xfce4-screensaver` could ignore input for a set amount of time after activating, to prevent catching unwanted input when mouse is put away for example.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/140Cannot unlock laptop after closing lid2024-03-14T14:56:02ZAndrew PamCannot unlock laptop after closing lidIf I close my laptop lid without first manually locking the screen, the screensaver seems to take a screen capture and then blank the screen. When I reopen the laptop and resume, this screen capture is displayed full screen and blocks t...If I close my laptop lid without first manually locking the screen, the screensaver seems to take a screen capture and then blank the screen. When I reopen the laptop and resume, this screen capture is displayed full screen and blocks the password entry dialogue, which is both invisible and does not have keyboard focus. The only way to log back in is to switch to a text console, log in and kill the screen saver (which also kills the lock screen), log out of the text console and switch back to the graphics VT.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/139Unable to create new xfce4-screensaver entry with arbitrary Exec path2024-01-02T20:00:00ZWilliam N. Braswell, Jr.Unable to create new xfce4-screensaver entry with arbitrary Exec pathI'm trying to create a new screensaver entry by using an existing program such as `/usr/bin/xeyes`. My ultimate goal is to be able to use any arbitrary command as a screensaver, specifically the `/usr/bin/mpv` movie player to play a loop...I'm trying to create a new screensaver entry by using an existing program such as `/usr/bin/xeyes`. My ultimate goal is to be able to use any arbitrary command as a screensaver, specifically the `/usr/bin/mpv` movie player to play a looping video as a screensaver.
My system info:
```
$ cat /etc/issue
Ubuntu 20.04 LTS \n \l
$ uname -a
Linux FOO 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ xfce4-screensaver-command --version
xfce4-screensaver-command 0.1.10
```
If you study the following two links, you will find basically the same procedure for creating a new xfce4-screensaver entry:
https://docs.xfce.org/apps/xfce4-screensaver/faq#where_are_all_the_screensavers
https://www.youtube.com/watch?v=tiJwKVPlyuY
Following the official XFCE docs, I created the below 6 lines saved in the file "/usr/share/applications/screensavers/xfce-xeyes-screensaver.desktop":
```
[Desktop Entry]
Type=Application
Name=Xeyes
Exec=/usr/bin/xeyes
TryExec=/usr/bin/xeyes
Categories=Screensaver;
```
This DOES correctly cause an new entry named "Xeyes" to show up in my Screensaver Preferences GUI, but it DOES NOT actually work, when I click on that entry for a preview it just shows a blank screen.
Further, when I run `killall xfce4-screensaver` to stop the default process, then run it manually in a terminal via `xfce4-screensaver --debug`, and click the screen lock button, I am able to find the following error which does not show up with the working screensaver entries:
```
...
[manager_maybe_start_job_for_window] gs-manager.c:210 (16:18:43.490): Starting job for window
[gs_job_start] gs-job.c:453 (16:18:43.490): Starting job
[spawn_on_widget] gs-job.c:360 (16:18:43.492): Could not start command '(null) ': Failed to execute child process “(null)” (No such file or directory)
...
```
See attached file for full debug output.
I have confirmed that it DOES WORK if I just copy the "Exec" and "TryExec" lines from one of the existing screensaver entries such as "Exec=/usr/libexec/xfce4-screensaver/popsquares", which shows the "Pop art squares" screensaver and DOES NOT give the error above.
Searching the Internet for "[spawn_on_widget] gs-job.c" or "Could not start command (null)" both brought up nothing! Please help
[wbraswell_20231231-xfce4_screensaver_debug.txt](/uploads/35f5fdb47316df58c3cae490fd1b1f3b/wbraswell_20231231-xfce4_screensaver_debug.txt)
[ EDIT: I will leave this issue open for the "arbitrary Exec path" enhancement request, and create a new issue for any further concerns. ]https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/138Lockscreen multi-monitor displaying desktop contents2024-03-04T13:38:45ZM KLockscreen multi-monitor displaying desktop contentsFor as long as I remember using the lock-screen of XFCE (which is only 2 years) on EndeavourOS (Arch) I have the following problem.
I have two displays and a receiver. Locking the system and turning a display/receiver off makes you able ...For as long as I remember using the lock-screen of XFCE (which is only 2 years) on EndeavourOS (Arch) I have the following problem.
I have two displays and a receiver. Locking the system and turning a display/receiver off makes you able to see the contents of the desktop.
My system is almost always running the latest updates and only ever lags behind 2-3 weeks.
Steps to reproduces:
1. Have multiple displays.
2. Lock the screen.
3. Turn one of the displays off.
4. Enjoy seeing the contents of your desktop.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/137Show unlock dialog on all monitors2023-10-11T16:59:37ZhaarpShow unlock dialog on all monitorsHey!
It would be great if it was possible to (optionally?) show the unlock dialog on all monitors in parallel. Reasons:
- The machine might have been brought to a different location and the monitor setup chosen while locked might not h...Hey!
It would be great if it was possible to (optionally?) show the unlock dialog on all monitors in parallel. Reasons:
- The machine might have been brought to a different location and the monitor setup chosen while locked might not have handled the relevant monitor correctly (the one chosen to show the dialog)
- The logic to decide on which monitor to show the dialog can be unexpected (not the primary one?)
- Some monitors might take a long time to wake up from sleep, while others are quick. I'd love to start typing my password into a dialog visible on a fast monitor while the slow ones are still busy.
This is not super important but would be a good addition, imo :smile:
Thanks!https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/135[Feature Request] Setting to allow media keys2023-09-27T16:24:49ZKip[Feature Request] Setting to allow media keysIt would be wonderful if there was a setting that allowed the user's media keys (e.g. MPRIS) on their keyboard to still function while the screensaver is currently locked.It would be wonderful if there was a setting that allowed the user's media keys (e.g. MPRIS) on their keyboard to still function while the screensaver is currently locked.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/134xfce4-screensaver doesn't honor "loginctl unlock-session"2023-11-21T22:24:07ZMikko Rantalainenxfce4-screensaver doesn't honor "loginctl unlock-session"xfce4-screensaver doesn't honor systemd controlled "loginctl unlock-session" to unlock the screensaver.
Test case:
- Run `sleep 15 && loginctl unlock-session` in terminal.
- Lock the screen (I think Ctrl+Shift+L by default should be ok...xfce4-screensaver doesn't honor systemd controlled "loginctl unlock-session" to unlock the screensaver.
Test case:
- Run `sleep 15 && loginctl unlock-session` in terminal.
- Lock the screen (I think Ctrl+Shift+L by default should be okay).
- Wait for 15 seconds.
Expected result:
The `loginctl` should unlock the screensaver.
Actual result:
Nothing happens.
This results in requiring to enter the password twice to do user switching when running on Ubuntu 22.04 and using lightdm as the login manager: once for the lightdm and another time to unlock the screensaver.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/132Does not re-engage DPMS if unlock dialog not triggered2023-08-01T14:16:53ZhaarpDoes not re-engage DPMS if unlock dialog not triggeredxfce4-screensaver-4.18.2 plus 9df3ad56 running on a Gentoo box.
With the screensaver active:
- Move the mouse a lot and get the unlock dialog. Cancel the dialog (by waiting or pressing Esc), it will switch to blank, and 1s later put th...xfce4-screensaver-4.18.2 plus 9df3ad56 running on a Gentoo box.
With the screensaver active:
- Move the mouse a lot and get the unlock dialog. Cancel the dialog (by waiting or pressing Esc), it will switch to blank, and 1s later put the screen to sleep [✓]
- Move the mouse a little, the display wakes up to a black screen, but with no dialog. It will stay in this state and not re-engage DPMS sleep like it should. Wasting energy/battery and/or hurting your sleep quality by being bright :) [❗]
Settings:
- Enable scrensaver: On
- Theme = Blank screen, sleep after 1s, off after 5m
- Activate screensaver when computer is idle: On
- Regard computer as idle after: 15 minutes
- Inhibit for fullscreen: On
- Enable Lock Screen: On
- Lock Screen with screensaver: On, 0 minutes
- Lock Screen with System Sleep: On
- On-screen keyboard: Off
- Session Status messages: Off
- Logout: Off
- User Switching: Off
Thanks!https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/129screen saver will let keyboard keystroke through to application before screen...2023-11-22T08:31:04ZTed Leungscreen saver will let keyboard keystroke through to application before screen unlocks while waking upWhen my machine is screen locked, and my monitors go into sleep mode. Sometimes it takes a long time for the monitors to wake up and the password prompt to show up. (long time being maybe 10-15 seconds). I notice this particularly happen...When my machine is screen locked, and my monitors go into sleep mode. Sometimes it takes a long time for the monitors to wake up and the password prompt to show up. (long time being maybe 10-15 seconds). I notice this particularly happens when external 4k monitors are attached. While it's blank waiting to wake up and prompt me for a password, anything I type goes to what ever application was active. i.e. I've had a web browser open and what ever I typed while it was asleep (usually my password ... ) shows up in the text fields of the web browser. I started just pressing backspace or space bar instead to wake up the machine and I find spaces (or deleted character) in my IDE for what ever text file I had open. Note those were the keystokes that happened before the screen unlock password dialog showed up and before I unlocked the screen.
This is fairly consistently reproducible as it seems to happen almost every time I unlock my machine after the monitors have gone to sleep.
my setup is as follows :
Linux version 6.2.9-300.fc38.x86_64 (mockbuild@38f30b3c0c69453fae61718fc43f33bc) (gcc (GCC) 13.0.1 20230318 (Red Hat 13.0.1-0), GNU ld version 2.39-9
.fc38) #1 SMP PREEMPT_DYNAMIC Thu Mar 30 22:32:58 UTC 2023
xfce4-screensaver.x86_64 4.18.2-1.fc38
Machine is thinkpad p14s (gen 3). This also happens with a thinkpad l380.
I have two 4k monitors attached simultaneously, one is a a phillips 288p, and second is a samsung u28e590ds. They are attached via laptops main plugs, 1 hdmi, 1 usbc
--------
as an additional note... I may have seen this before, this might be the display sleeping before the screen saver has had a chance to lock, and the "long wake up period" might be the machine-un-sleeps, then attempts to continue locking the desktop.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/120build: Improve PAM prefix handling or remove it2023-03-14T20:37:06ZGaël Bonithonbuild: Improve PAM prefix handling or remove itCurrently the PAM prefix can be set at configure time via `--with-pam-prefix`, otherwise it is set to `$sysconfdir` by default. Several problems arise:
* If no install prefix is explicitly provided via `--prefix` and `--sysconfdir` is no...Currently the PAM prefix can be set at configure time via `--with-pam-prefix`, otherwise it is set to `$sysconfdir` by default. Several problems arise:
* If no install prefix is explicitly provided via `--prefix` and `--sysconfdir` is not used either, `PAM_PREFIX` is set to `NONE` because it is set [too soon in `configure.ac`](https://gitlab.xfce.org/apps/xfce4-screensaver/-/blob/c1ef19a7110ab1fcea980919fd45b069df46e7a0/configure.ac#L163).
* When properly set to a value other than `/etc`, it seems not to be usable at least on linux systems, where [only `/etc` is a valid choice](https://gitlab.xfce.org/apps/xfce4-screensaver/-/blob/c1ef19a7110ab1fcea980919fd45b069df46e7a0/data/Makefile.am#L72).
* Incidentally, checks for the presence of PAM configuration files are [hard-coded without regard to this prefix](https://gitlab.xfce.org/apps/xfce4-screensaver/-/blob/c1ef19a7110ab1fcea980919fd45b069df46e7a0/src/gs-auth-pam.c#L703).
If the ability to choose this prefix serves any purpose, it should be improved, otherwise it should just be removed.
Because if this prefix is not correctly set, `/etc/pam.d/xfce4-screensaver` is not correctly installed and locking fails, forcing to kill xfce4-screensaver from a tty to be able to access your session again (the build warning about this can be missed, and anyway it was always displayed before https://gitlab.xfce.org/apps/xfce4-screensaver/-/commit/c1ef19a7110ab1fcea980919fd45b069df46e7a0).https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/118[feature request] Integration with xfce4-notifyd2023-07-30T10:21:15ZDouglas[feature request] Integration with xfce4-notifydGNOME can show notifications on the lock screen. I suppose this would require a standard way of sharing notification data between xfce4-notifyd and this screensaver.
![GNOME lock screen showing one notification](/uploads/a95ed8bb662e263...GNOME can show notifications on the lock screen. I suppose this would require a standard way of sharing notification data between xfce4-notifyd and this screensaver.
![GNOME lock screen showing one notification](/uploads/a95ed8bb662e2635895b3fb531c6bd32/unnamed.jpg)https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/115Suggestion for enhancement on D-bus interface2023-11-22T08:05:47ZAlex MalykhSuggestion for enhancement on D-bus interfaceHello there. It's not formally an issue, but a kind of feature request and/or suggestion for improvement. Is it possible to expose the D-bus interface in more freedesktop-like manner? Say, `org.freedesktop.ScreenSaver` interface on `/org...Hello there. It's not formally an issue, but a kind of feature request and/or suggestion for improvement. Is it possible to expose the D-bus interface in more freedesktop-like manner? Say, `org.freedesktop.ScreenSaver` interface on `/org/freedesktop/ScreenSaver` path under the `org.freedesktop.ScreenSaver` name?
The problem I encountered was that both Chromium browser and VLC player were not able to inhibit the screensaver properly. After some research I had come to the conclusion that `org.xfce.ScreenSaver` is too esoteric for them. I have solved the problem for myself locally, but just wonder why `org.xfce.ScreenSaver` was chosen over `org.freedesktop.ScreenSaver`. I think, it is possible to expose identical D-bus objects alongside to improve compatibility with other FDO-oriented software.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/114Exclude slideshow screensaver from random option during locker2024-02-03T14:41:06ZTimo KönneckeExclude slideshow screensaver from random option during lockerThis is a potential self inflicted security risc imho.
(First time) Users unaware of the slideshow screensaver might just select random to have any screensaver.
On Screen blanking, potentially private or otherwise security sensitive scre...This is a potential self inflicted security risc imho.
(First time) Users unaware of the slideshow screensaver might just select random to have any screensaver.
On Screen blanking, potentially private or otherwise security sensitive screenshots or images might be shown in a supposed safe locker/lock-screen environment without users intention.
This just happened to humble me. Trying xfce4 for some time and selecting random screensaver option, leaving all other options in xfce4-screensaver unchanged. I went afk to come back to my wife being irritated by the laptop showing random screenshots, blown up icons, mixed with holiday pics.
I think it could have hit other users harder, erhm.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/111xfce4-screensaver crash allowing unlock without password2023-11-21T21:09:24Zwes edensxfce4-screensaver crash allowing unlock without passwordThis starts off on the lock screen. there is some issue that causes the monitor to not fully wake up. what happens is that the lock screen flashes for about 1 second before turning black again. when in this state, i will hold a key (TAB)...This starts off on the lock screen. there is some issue that causes the monitor to not fully wake up. what happens is that the lock screen flashes for about 1 second before turning black again. when in this state, i will hold a key (TAB), and start clicking on the lock screen buttons as fast as i can. when i do this for 30 seconds or so xfce4-screensaver will crash and will leave the system logged in without putting in my password. below is a dump of my machine info as well as the error printout that gets generated when i run xfce4-screensaver manually from the command line to see the prints.
i didn't see anything quite like this in existing reports so i hope its not a duplicate. i'll mark as confidential just in case.
thanks,
wes edens
the system i'm running on
```
edenswk1@edenswk1-ld3:~$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
```
```
edenswk1@edenswk1-ld3:~$ uname -a
Linux edenswk1-ld3 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```
```
dialog_process_watch] gs-window-x11.c:1427 (11:02:54.906): Got request for quit
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: [auth_check_idle] xfce4-screensaver-dialog.c:360 (11:02:54.906): Authentication failed, retrying (3)
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output:
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: ** (xfce4-screensaver-dialog:18049): WARNING **: 11:02:54.905: Unable to establish service xfce4-screensaver: Critical error - immediate abort
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output:
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: [do_auth_check] xfce4-screensaver-dialog.c:305 (11:02:54.906): Verify user returned: FALSE
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: [auth_check_idle] xfce4-screensaver-dialog.c:360 (11:02:54.906): Authentication failed, retrying (4)
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output:
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: ** (xfce4-screensaver-dialog:18049): WARNING **: 11:02:54.906: Unable to establish service xfce4-screensaver: Critical error - immediate abort
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output:
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: [do_auth_check] xfce4-screensaver-dialog.c:305 (11:02:54.906): Verify user returned: FALSE
[error_watch] gs-window-x11.c:893 (11:02:54.906): Command output: [auth_check_idle] xfce4-screensaver-dialog.c:363 (11:02:54.906): Authentication failed, quitting (max failures)
(xfce4-screensaver:13077): Gdk-ERROR **: 11:02:54.911: The program 'xfce4-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 35481 error_code 3 request_code 131 (XInputExtension) minor_code 40)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
```https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/110Missing the possibility to set two separate configurations, one for battery a...2023-07-30T10:22:05ZpezcurrelMissing the possibility to set two separate configurations, one for battery and one for ac powerHello,
i think xfce4-screensaver is missing the possibility to set 2 separate configurations for devices like laptops, which can run on battery power: one configuration that applies when the device is running on battery power and anoth...Hello,
i think xfce4-screensaver is missing the possibility to set 2 separate configurations for devices like laptops, which can run on battery power: one configuration that applies when the device is running on battery power and another that applies when it is running on ac power, just like xfce4-power-manager does for display power management (i think it would be ideal if xfce4-power-manager-settings integrated screensaver and screen-locking settings in the "display" tab).https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/107Screen locking should have a blocking option (return when screen is actually ...2023-08-24T15:56:06Zdrws rwxScreen locking should have a blocking option (return when screen is actually locked)`xfce4-screensaver-command --lock` currently sends the screen-lock signal and exits immediately. This is an expected and correct default behavior, however more synchronous execution is sometimes preferred. I'm proposing an additional swi...`xfce4-screensaver-command --lock` currently sends the screen-lock signal and exits immediately. This is an expected and correct default behavior, however more synchronous execution is sometimes preferred. I'm proposing an additional switch that would make `xfce4-screensaver-command --lock` exit when screen is actually locked.https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/106Lock screen Alias2023-07-30T10:28:09ZThomas HansenLock screen AliasWhen typing in `lock screen` into an application search, the xfce4-screensaver should appear, preferably to the lock screen settings.When typing in `lock screen` into an application search, the xfce4-screensaver should appear, preferably to the lock screen settings.