Xscreensaver not working properly

[wirr]

hey there,
i have the same problem with the settings not opening at all like in this thread

XScreensaver settings not opening

Hello not sure if this is the right place but in trying to install XScreensaver I have the problem with not being able to access the settings menu it try I see it pop up in the dock jumping up and down and then it goes away and doesn’t load was wonder if any would know how to fix this. I will also add that the xscreensaver itself does work meaning it will start after 10 minutes but I can’t get into settings. I’ve looked everywhere and all I get is info from 1 or more years ago and this problem …

and also there are some games where the screensaver seems to ignore the controller input and activates while playing … from the wikipage of the thread above, i figure it has to do something with the d-bus , but there ends my understanding and i have no clue where to change what to (de?)activate this d-bus … for the controller or for the games? (already tried to reinstall xscreensaver, but no change)

would be nice if someone could tell me what i’d need to do to fix that, thanks

garuda-inxi
System:
Kernel: 6.12.15-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=b3328148-480b-42c9-9425-ff822289ea26 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma v: 6.3.1 tk: Qt v: N/A info: frameworks v: 6.11.0
wm: kwin_wayland tools: xscreensaver,xscreensaver-systemd vt: 1 dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B650E-E GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3207 date: 02/08/2025
Battery:
Device-1: hidpp_battery_0 model: Logitech G604 Wireless Gaming Mouse
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 4
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA60120C
Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 12 MiB
desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3006 min/max: 545/5733 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3006 2: 3006 3: 3006
4: 3006 5: 3006 6: 3006 7: 3006 8: 3006 9: 3006 10: 3006 11: 3006 12: 3006
13: 3006 14: 3006 15: 3006 16: 3006 17: 3006 18: 3006 19: 3006 20: 3006
21: 3006 22: 3006 23: 3006 24: 3006 bogomips: 225255
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 570.86.16 alternate: nouveau,nvidia_drm
non-free: 550/565.xx+ status: current (as of 2025-01; EOL~2026-12-xx)
arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie:
gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
active: none off: HDMI-A-2 empty: DP-2, DP-3, DP-4, HDMI-A-3
bus-ID: 01:00.0 chip-ID: 10de:2216 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
empty: DP-1,HDMI-A-1,Writeback-1 bus-ID: 0d:00.0 chip-ID: 1002:164e
class-ID: 0300 temp: 52.0 C
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: HDMI-A-2 model: HISENSE serial: <filter> built: 2023 res:
mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 68 gamma: 1.2
size: 1428x804mm (56.22x31.65") diag: 1639mm (64.5") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: radeonsi gbm: drv: kms_swrast surfaceless:
drv: nvidia wayland: drv: nvidia x11: drv: nvidia
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.86.16
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
memory: 9.77 GiB display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 13 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3080 driver: N/A device-ID: 10de:2216
surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:164e
surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.1 chip-ID: 1002:1640
class-ID: 0403
Device-3: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3
chip-ID: 0b05:1a52 class-ID: 0300
Device-4: Logitech [G533 Wireless Headset Dongle]
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 5-1:2 chip-ID: 046d:0a66 class-ID: 0300
API: ALSA v: k6.12.15-1-lts status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 06:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp6s0 state: down mac: <filter>
Device-3: Microsoft Xbox Wireless Adapter for Windows driver: xone-dongle
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:10
chip-ID: 045e:02fe class-ID: 0000 serial: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:7
chip-ID: 0489:e0e2 class-ID: e001 serial: <filter>
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
rfk-block: hardware: no software: no address: see --recommends
Drives:
Local Storage: total: 5.15 TiB used: 2.82 TiB (54.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: OWC model: Aura P12 Pro 2.0TB
size: 1.75 TiB block-size: physical: 4096 B logical: 4096 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: ECFM15.1 temp: 28.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 58.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-08WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: MBR
ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 020 scheme: GPT
ID-6: /dev/sdd maj-min: 8:48 vendor: SanDisk model: SD8SBBU240G1122
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 6000 scheme: MBR
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 103.51 GiB (22.2%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:3
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 103.51 GiB (22.2%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 103.51 GiB (22.2%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 103.51 GiB (22.2%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.51 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 24
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 61.6 C mobo: 50.2 C gpu: amdgpu temp: 52.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.51 GiB used: 6.05 GiB (19.8%)
Processes: 560 Power: uptime: 6h 56m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.11 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1907 libs: 574 tools: octopi,paru pm: flatpak
pkgs: 0 Compilers: gcc: 14.2.1 Shell: garuda-inxi default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.37
Garuda (2.6.26-1.1):
System install date:     2023-04-15
Last full system update: 2025-02-22
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

╭─wirr@wirr in ~ took 2s

[Duke187]

hello wirr,

with KDE you need to set up right.

Did you read this section ?

Like GNOME, KDE also decided to re-invent the wheel. To replace the KDE screen saver with XScreenSaver, do the following:

**1: Turn off KDE's built-in blanking.**
In *System Settings*, un-check the following items, as these are controlled by [xscreensaver-settings(1)](https://man.archlinux.org/man/xscreensaver-settings.1.en) now:

"*Workspace Behavior / Screen Locking / Lock automatically*"
"*Workspace Behavior / Screen Locking / After waking from sleep*"
"*Workspace Behavior / Screen Locking / Keyboard shortcut*"
"*Hardware / Power Management / Screen Energy Saving*"
"*Hardware / Power Management / Suspend session*"
"*Hardware / Power Management / Laptop lid closed" = Do Nothing*

If there are multiple tabs, you may need to change these settings on all three of them: "On AC power", "Battery" and "Low Battery".

**2: Launch XScreenSaver at login.**
Copy the file */usr/share/applications/xscreensaver.desktop* into the directory *~/.config/autostart/*
**3: Make KDE's "Lock" icon use XScreenSaver.**
Find the "*kscreenlocker_greet*" program. It might be in "*/usr/lib/*/libexec/*", or it might be somewhere else. Delete that file and replace it with a file containing these two lines. Make it executable (chmod a+x).

#!/bin/sh xscreensaver-command --lock &

This change will get blown away when you upgrade.
**4: Turn off KDE's built-in locking on suspend, even harder.**
Even after disabling KDE's screen locking, above, it is *possible* that KDE will still use its built-in locker when you close your laptop's lid. If that is happening, double-check the settings above, but if those are correct, try the following. First, ensure you are running KDE 5.21 or newer. Next, enable *"systemd user sessions"* for KDE so that you can edit the parameters for *ksmserver:*

kwriteconfig5 --file startkderc --group General \ --key systemdBoot true

Log out and back in.

Next, edit the *plasma-ksmserver* service to change how *ksmserver* is launched:

systemctl edit --user plasma-ksmserver.service

Replace the contents of the file that lets you edit with this:

[Service] ExecStart= ExecStart=/usr/bin/ksmserver --no-lockscreen

Then log out and back in *again*.```

[Duke187]

found here and here:

https://wiki.archlinux.org/title/XScreenSaver
https://man.archlinux.org/man/xscreensaver.1#INSTALLING_XSCREENSAVER_ON_KDE

[wirr]

hey thanks for the fast reply

, well i did read that wiki page, but to be honest, i didnt understand much … from the link to installing_xscreen i’m reading it would be possible to set that through the settings box, but that one wont open when i click it at startup …

so i need to search for the override-config at screensaver folder and there need to add that service-exec part ? just somewhere?

[Duke187]

can you start xscreensaver with the terminal and see that error output?
copy and paste it too in here.

i dont have it installed and im not sure is some changes in the new kde 6 version.

maybe i try to install it to see errors.

[wirr]

you mean this?

wirr@wirr in ~ took 2s
╰─λ xscreensaver

xscreensaver: 15:09:35: WARNING: Wayland is not supported.

xscreensaver: 15:09:35:     Under Wayland, idle-detection fails when non-X11
xscreensaver: 15:09:35:     programs are selected, meaning the screen may
xscreensaver: 15:09:35:     blank prematurely.  Also, locking is impossible.
xscreensaver: 15:09:35:     See the manual for instructions on configuring
xscreensaver: 15:09:35:     your system to use X11 instead of Wayland.

xscreensaver: 15:09:35: already running on display :1 (window 0x1200001)
from process 7824 (wirr@wirr-sys)

(PS: idle-detection is the word, so for my understanding, that is off for games or for the controller? do i need to activate it for all games individualy or can i change it for the controller and that works for all or so? )

[Duke187]

so i will try to install and reproduce the issue.

which games you mean and which game launcher you are using?

i dont have an error here

[wirr]

well, i cant open that “xss”-app , it just shows me this box on startup

but when i click on settings, nothing will happen

[Duke187]

yes its laggy ive have same result try in cmd

xscreensaver-settings to open it.

but its no settings for games . i will look arround in the wiki

[wirr]

there it prompts this:

wirr@wirr in ~
╰─λ xscreensaver-settings
xscreensaver-settings: 15:33:13: Gdk: gdk_x11_window_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed

[Duke187]

ive seen your on the lts kernel and i am on the zen kernel so maybe you try other kernels but your games have a comandline parameter to set settings before starting games.

[wirr]

mhm, i switched from zen to lts, because the xone-controllers didnt work there at all , dont know if that is fixed by now, but i can try …

for the commandline parameters, you mean i have to add in steam-command line the part – no lockscreen ?!

[wirr]

okay, i booted the zen kernel … xone is working, but its the same issue wit the screensaver

─wirr@wirr in ~
╰─λ xscreensaver-settings
xscreensaver-settings: 15:45:24: Gdk: gdk_x11_window_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed

╭─wirr@wirr in ~ took 0s

[nepti]

@wirr

wm: kwin_wayland tools: xscreensaver,xscreensaver-systemd

@wirr

Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland

@wirr

wirr@wirr in ~ took 2s
╰─λ xscreensaver

xscreensaver: 15:09:35: WARNING: Wayland is not supported.

xscreensaver: 15:09:35:     Under Wayland, idle-detection fails when non-X11
xscreensaver: 15:09:35:     programs are selected, meaning the screen may
xscreensaver: 15:09:35:     blank prematurely.  Also, locking is impossible.
xscreensaver: 15:09:35:     See the manual for instructions on configuring
xscreensaver: 15:09:35:     your system to use X11 instead of Wayland.

xscreensaver:

xscreensaver
Screen saver and locker for the X Window System

XScreenSaver is the standard screen saver collection shipped on most Linux and Unix systems running the X11 Window System, since its first release in 1992.
On X11 systems, XScreenSaver is two things: it is both a large collection of screen savers; and it is also the framework for blanking and locking the screen. 

Switch to an x11 session and check if it works without issues.

[SGS]

DR’TL

You boot in to wayland and use X11 stuff.

@wirr

wm: kwin_wayland

@wirr

Under Wayland, idle-detection fails when non-X11

@wirr

your system to use X11 instead of Wayland.

[Duke187]

i dont have steam games running because lost of phone and no login anymore.

i do a new account and check for free games and try with xscreensaver and look for the steam setting where to change it for fully game play with no issue =)

[wirr]

how do i do that ?
i remember choosing something at installation, but since i dont know much about it, it was but a random choice …

but i looked through the garuda-assistent/gamer/settings but didnt find that checkbox for the ui

[Duke187]

logout and below the login you see session wayland click on it and choose plasma x11

[wirr]

AYY, that did work for the settings … gonna try a game to see if that is fixed too

[wirr]

ok, no, the screensaver still activates ingame … (atm it is cult of the lamb via steam, but had the same problem with steam heist and others i think … )