[SOLVED] xscreensaver on Budgie Desktop /Arch

Der Chefkoch · 2021-05-25 15:55:23

I am running Budgie Desktop and while I am very happy with it, the Screensaver is giving me quite some issues (as Budgie is presently only providing a temporary fork of gnome-screensaver etc...)

I had xscreensaver running, with hibernation in principle working fine when I closed the laptop lid.

Following https://man.archlinux.org/man/xscreensaver.1 I followed the point of "Make[ing] GNOME's "Lock Screen" use XScreenSaver." (as Budgie is GNOME-based and lots of tweaks work)

sudo ln -sf /usr/bin/xscreensaver-command \
            /usr/bin/gnome-screensaver-command

However that now seems to interfere with hibernation - in fact now the screen neither locks nor blanks when I close the laptop lid.

I do not have experience in dealing with these types of links - how can I delete/reverse that?

Thx

Last edited by Der Chefkoch (2021-05-27 10:51:42)

seth · 2021-05-25 18:33:13

You can just delete /usr/bin/gnome-screensaver-command

Did you follow the other steps in the manual?
Notably the "Stop GNOME from blocking XScreenSaver's "systemd" integration" part?

Der Chefkoch · 2021-05-25 21:25:35

seth wrote:

You can just delete /usr/bin/gnome-screensaver-command
Did you follow the other steps in the manual?
Notably the "Stop GNOME from blocking XScreenSaver's "systemd" integration" part?

Strange, deleting the symlink as you suggested didn't do anything to hibernation/locking on lid close... seems something else broke it. Hibernation worked before, I implemented it according to https://wiki.archlinux.org/title/Power_ … ibernation

I just executed the respective systemctl command for the masking, however that only worked without root privileges (in the manual its given with sudo)

$ systemctl --user mask gsd-screensaver-proxy.service

Unit gsd-screensaver-proxy.service does not exist, proceeding anyway.
Created symlink /home/christian/.config/systemd/user/gsd-screensaver-proxy.service → /dev/null.

If that worked out correctly, it didnt resolve the issue unfortunately. gsd-screensaver-proxy.service is not active

$ systemctl status gsd-screensaver-proxy.service
○ gsd-screensaver-proxy.service
     Loaded: masked (Reason: Unit gsd-screensaver-proxy.service is masked.)
     Active: inactive (dead)

journalctl -f did not show any actions on lid close and immediate lid open.

Last edited by Der Chefkoch (2021-05-25 22:26:07)

seth · 2021-05-26 05:28:49

Unit gsd-screensaver-proxy.service does not exist, proceeding anyway.

What else did you do besides creating the symlink?
Do you have https://archlinux.org/packages/communit … reensaver/ installed?
/usr/bin/gnome-screensaver-command doesn't exist in the repos anymore (likely gone w/ gnome40)

Please post a complete system journal (sudo journalctl -b) for a boot w/ a failed hibernation attempt.

Der Chefkoch · 2021-05-26 08:36:56

seth wrote:

Unit gsd-screensaver-proxy.service does not exist, proceeding anyway.
What else did you do besides creating the symlink?

Thank you for your input so far seth.

Well that is now hard to say, a blanking screen on lid close is kind of easy to miss. I'm thinking about it but it might turn out it broke some time ago.

I am now running xscreensaver-arch-logo from AUR as opposed to the vanilla version, just in case that makes a difference (its one version behind the vanilla one).

seth wrote:

Do you have https://archlinux.org/packages/communit … reensaver/ installed?
/usr/bin/gnome-screensaver-command doesn't exist in the repos anymore (likely gone w/ gnome40)

No I made sure I uninstalled all other screensavers I played around with before (gnome-screensaver, budgie-screensaver, i3lock)

seth wrote:

Please post a complete system journal (sudo journalctl -b) for a boot w/ a failed hibernation attempt.

I could confirm that hibernation in fact does work - checking with "systemctl hibernate" and then it hibernates and wakes up correctly. Consequently, there is something wrong with triggering hibernation, e.g. on lid close.

EDIT:
... and I found a solution to the hibernation issue under https://wiki.archlinux.org/title/GNOME# … _is_closed

I had - months ago - utilised gnome-tweaks, for some reason on the tab General the switch "Suspend when laptop lid is closed" was turned off. However the article states "To change the lid switch action system-wide, ensure that the setting described above is not turned off and edit the systemd settings in /etc/systemd/logind.conf."

So I activated that part and now hibernation on lid close works again!

...the one thing that is currently unsolved on my side would be "Stop GNOME from blocking XScreenSaver's "systemd" integration" from the xscreensaver manual. As pointed out by you "Unit gsd-screensaver-proxy.service does not exist, proceeding anyway." That part with masking/unmasking is currently not working.

$ systemctl status gsd-screensaver-proxy.service
Unit gsd-screensaver-proxy.service could not be found.

If this service is not running - could that be Budgie specific compared to native Gnome?

Last edited by Der Chefkoch (2021-05-26 10:52:08)

Der Chefkoch · 2021-05-26 09:26:31

[deleted, edit included above]

Last edited by Der Chefkoch (2021-05-26 10:10:10)

seth · 2021-05-26 11:55:09

Does gnome/budgie block xscreensaver from being activated?
The xscreenaver manual seems to no longer apply to at least gnome40 and neither gnome-screensaver nor gsd-screensaver-proxy.service exist in the repos.

Der Chefkoch · 2021-05-26 13:58:53

seth wrote:

Does gnome/budgie block xscreensaver from being activated?
The xscreenaver manual seems to no longer apply to at least gnome40 and neither gnome-screensaver nor gsd-screensaver-proxy.service exist in the repos.

xscreensaver can be started and is generally working, however there seems to be an issue with systemd (and gsd-screensaver-proxy)

This error message shows when reactivating the xscreensaver service

xscreensaver-systemd: 15:52:56: connection failed: "org.freedesktop.ScreenSaver" in use by pid 1371 (/usr/lib/gsd-screensaver-proxy)
xscreensaver: 15:52:56: pid 3434: xscreensaver-systemd exited unexpectedly with status 1

So while a gsd-screensaver-proxy.service was not found, there is some interference with /usr/lib/gsd-screensaver-proxy

seth · 2021-05-26 14:13:27

There's /etc/xdg/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop which probably starts the offending proxy, you want to shadow or remove that file.
https://wiki.archlinux.org/title/XDG_Autostart
If you remove it, you also want to NoExtract it.

Der Chefkoch · 2021-05-26 19:43:09

seth wrote:

There's /etc/xdg/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop which probably starts the offending proxy, you want to shadow or remove that file.
https://wiki.archlinux.org/title/XDG_Autostart
If you remove it, you also want to NoExtract it.

well, I renamed said file but that had the tiny side effect that the DE crashed on login and i had to chroot into the encrypted root partition from an arch install usb to reverse that, exciting stuff on a work day

Is there something else I could try?

seth · 2021-05-26 19:45:46

Renaming it should™ not do anything (if it remains in that path), but the proper way to deactivate it is explained in the linked wiki article (create a copy in your $HOME and set it hidden)

Also you don't have to chroot from a life system because of this, you can just boot the multi-user.target, see the 2nd link in my signature.

Der Chefkoch · 2021-05-27 08:45:06

seth wrote:

Renaming it should™ not do anything (if it remains in that path), but the proper way to deactivate it is explained in the linked wiki article (create a copy in your $HOME and set it hidden)
Also you don't have to chroot from a life system because of this, you can just boot the multi-user.target, see the 2nd link in my signature.

Pardon my ignorance, I guess that is why I am posting in the newbie corner

So I created a copy in my local autostart director and added Hidden=true - that did the trick. It seems that systemd integration of xscreensaver is now working.

What did you mean with your noextract comment, is that to prevent pacman to update the file in the systemwide autostart?

seth · 2021-05-27 10:43:33

Yes, but that's not required since you shadowed it.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2021-05-25 15:55:23

[SOLVED] xscreensaver on Budgie Desktop /Arch

#2 2021-05-25 18:33:13

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#3 2021-05-25 21:25:35

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#4 2021-05-26 05:28:49

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#5 2021-05-26 08:36:56

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#6 2021-05-26 09:26:31

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#7 2021-05-26 11:55:09

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#8 2021-05-26 13:58:53

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#9 2021-05-26 14:13:27

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#10 2021-05-26 19:43:09

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#11 2021-05-26 19:45:46

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#12 2021-05-27 08:45:06

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

#13 2021-05-27 10:43:33

Re: [SOLVED] xscreensaver on Budgie Desktop /Arch

Board footer