Description of problem ====================== xscreensaver-demo or xscreensaver-settings fails to start when executed from a xmonad session, which prevents user to configure it directly Version-Release number of selected component ============================================ ``` $ rpm -qa 'xscreensaver*' xscreensaver-gl-base-6.06-3.fc37.x86_64 xscreensaver-extras-base-6.06-3.fc37.x86_64 xscreensaver-gl-extras-6.06-3.fc37.x86_64 xscreensaver-base-6.06-3.fc37.x86_64 xscreensaver-extras-6.06-3.fc37.x86_64 xscreensaver-6.06-3.fc37.x86_64 $ rpm -q xorg-x11-server-Xorg xorg-x11-server-Xorg-1.20.14-21.fc37.x86_64 ``` How reproducible ================ 100% Steps to Reproduce ================== 1. select xmonad as a window manger and login 2. try to run xscreensaver-settings or xscreensaver-demo Actual results ============== ``` $ xscreensaver-settings xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:71:44: Invalid number for color value xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:72:44: Invalid number for color value xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:74:53: Invalid number for color value xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:75:53: Invalid number for color value xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:76:56: Invalid number for color value xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:77:65: Invalid number for color value xscreensaver-settings: 23:29:21.11: X error: xscreensaver-settings: Failed request: BadMatch (invalid parameter attributes) xscreensaver-settings: Major opcode: 42 (X_SetInputFocus) xscreensaver-settings: Resource id: 0x3000007 xscreensaver-settings: Serial number: 454 / 456 ``` Expected results ================ xscreensaver-settings starts without any error Additional info =============== Fortunately `xscreensaver-command -lock` works without any problems.
Currently I don't want to test this unless you can provide the "exact" way to reproduce this. (e.g. You seem to be using xmonad, however in my recognition none of the live spin provided by Fedora is using xmonad by default. and it seems xmonad needs some user configuration. So please provide the very detailed procedure how you set up your xmonad environment, how you launched xscreensaver-settings, etc. i.e. I have never used xmonad. )
At least this issue is not reproducible on LXDE or XFCE.
Now I've tried * freshly install LXDE 38 live spin * reboot * sudo dnf config-manager --set-disabled \*modular\* * sudo dnf config-manager --set-enabled updates updates-testing * sudo dnf upgrade * sudo dnf install xmonad redhat-rpm-config xscreensaver-extras * reboot * login to xmonad sesssion * press alt-shift-return * on the terminal, $ xscreensaver-settings And xscreensaver-settings works on xmonad session, i.e. unreproducible to me. As no response from the reporter is received, closing.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
I can confirm this with mwm in Fedora 39. Kernel modules: rtsx_pci m@localhost:~$ xscreensaver-settings xscreensaver-settings: 20:09:33.36: X error: xscreensaver-settings: Failed request: BadMatch (invalid parameter attributes) xscreensaver-settings: Major opcode: 42 (X_SetInputFocus) xscreensaver-settings: Resource id: 0xc00007 xscreensaver-settings: Serial number: 447 / 449 m@localhost:~$ m@localhost:~$ rpm -qa 'xscreensaver*' xscreensaver-extras-base-6.08-1.fc39.x86_64 xscreensaver-gl-base-6.08-1.fc39.x86_64 xscreensaver-gl-extras-6.08-1.fc39.x86_64 xscreensaver-base-6.08-1.fc39.x86_64 xscreensaver-extras-6.08-1.fc39.x86_64 xscreensaver-6.08-1.fc39.x86_64 m@localhost:~$ If you need more information, please let me know.
To reproduce it: Install Fedora Server Edition, choose minimal installation. Install xorg-x11-server-Xorg, xterm, xinit. Install mwm, add it to .Xclients. Run startx and run xscreensaver-demo. Another minor problem: It needs libvulkan.so.1, but doesn't install vulkan-loader as dependency.
Again at least this issue is not reproducible on LXDE or XFCE. The original reporter uses xmonad, so anyway I don't handle the issue on mwm on this ticket.
(In reply to Mamoru TASAKA from comment #7) > Again at least this issue is not reproducible on LXDE or XFCE. > The original reporter uses xmonad, so anyway I don't handle the issue on mwm > on this ticket. I have now opened https://bugzilla.redhat.com/show_bug.cgi?id=2257043 with mwm and steps to reproduce.
It seems that this is the error I already had in Debian. They released a patch for it. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%231030909#219