Announcement

Collapse
No announcement yet.

Kubuntu 25.10 Xscreensaver no Autostart

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [RESOLVED] Kubuntu 25.10 Xscreensaver no Autostart

    I searched for it on the Internet, but couldn't find a solution.

    Is there a way to install Xscreensaver in Kubuntu?

    If you install Xscreensaver via Synaptic Package Manager, you won't be able to start this screensaver.
    โ€‹
    ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
    ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
    ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
    ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

    โ€‹

    #2

    It has taken extra work to use screensavers in at least Gnome and KDE for quite a number of years now.

    https://www.jwz.org/xscreensaver/man1.html see the KDE section

    It does not specify if you still need to use an xorg session for this but it seems logical.

    Now, if you just use a slideshow , you can configure this as the lock screen wallpaper.
    Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
    HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
    HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linuxโ€‹

    Comment


      #3
      And I found this, which may be useful:

      https://store.kde.org/p/2318884/

      https://invent.kde.org/dos/plasma-wallpaper-application#installation
      Last edited by claydoh; Jan 15, 2026, 06:00 PM.
      Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
      HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
      HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linuxโ€‹

      Comment


        #4

        โ€‹Does not work after restarting.
        โ€‹
        Last edited by greenster; Feb 05, 2026, 03:18 PM.
        ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
        ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
        ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
        ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

        โ€‹

        Comment


          #5
          Does not work after restarting.
          โ€‹
          Last edited by greenster; Feb 05, 2026, 03:18 PM.
          ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
          ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
          ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
          ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

          โ€‹

          Comment


            #6
            Xscreensaver still works on my Windows 11, even though it was last updated in 2015. ๐Ÿฅณ๐Ÿฅณ๐Ÿฅณ

            โ€‹
            Click image for larger version

Name:	XScreenSaver for Windows v0.78-Stephan Gruner 05-02-2026ย  21_21_01.jpg
Views:	156
Size:	102.8 KB
ID:	690207โ€‹
            ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
            ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
            ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
            ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

            โ€‹

            Comment


              #7
              I added Xscreensaver to autostart, but this error is displayed:

              Click image for larger version

Name:	Bildschirmfoto_20260206_090431.png
Views:	151
Size:	268.2 KB
ID:	690226



              โ€‹I also tried to start Xscreensaver via the console, but this error was displayed:

              Click image for larger version

Name:	Bildschirmfoto_20260206_085041.png
Views:	155
Size:	27.9 KB
ID:	690227

              โ€‹
              Very kindly asked, how can these errors be eliminated?
              โ€‹

              โ€‹

              โ€‹
              ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
              ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
              ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
              ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

              โ€‹

              Comment


                #8
                I found the solution: I have to select the โ€œPlasma (X11)โ€ workspace session when logging in. But because I selected automatic login when installing Kubuntu, Kubuntu does not remember that it should start with Plasma (X11).

                How do I disable automatic login?


                Click image for larger version  Name:	20260206_141135.jpg Views:	0 Size:	63.6 KB ID:	690232โ€‹






                โ€‹
                ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                โ€‹

                Comment


                  #9
                  Go to System Settings then click on Colors & Themes then Login Screen (SDDM) then at the top of the window, click on Behavior... and then uncheck Automatically log in: then click on Apply.
                  Windows no longer obstruct my view.
                  Using Kubuntu Linux since March 23, 2007.
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmesโ€‹

                  Comment


                    #10
                    Snowhog Thank you very much for your help. It works well.

                    Now XScreensaver starts. But it requires you to start display โ€œ:0โ€. But how do you make XScreensaver do this automatically and start minimized when Kubuntu starts?



                    Click image for larger version

Name:	Bildschirmfoto_20260206_173302.png
Views:	149
Size:	283.0 KB
ID:	690241โ€‹




                    โ€‹
                    โ€‹โ€‹
                    ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                    ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                    ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                    ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                    โ€‹

                    Comment


                      #11
                      This may be helpful.

                      AI Overview

                      The message "The XScreenSaver daemon doesn't seem to be running" appears when you try to launch the
                      xscreensaver settings, but the background process (daemon) is inactive. KDE Plasma uses its own screen locking system by default, which can conflict with XScreenSaver.
                      To resolve this and use XScreenSaver, you generally need to ensure the KDE screen locker is disabled and the xscreensaver daemon is set to launch automatically at startup.

                      Option 1: Launch the Daemon Now
                      If you want to use XScreenSaver just for the current session, simply click "Yes" or "Launch it Now" in the dialog box. This will start the daemon for your current session, and you can configure its settings via the xscreensaver-demo application.

                      Option 2: Configure XScreenSaver as your permanent screensaver
                      For a permanent solution where XScreenSaver is used instead of the default Plasma screen locker, follow these steps:
                      • Disable the default KDE screen locker:
                        • Open System Settings in KDE.
                        • Navigate to Workspace > Screen Locking (or Desktop Behavior > Screen Locking in older versions).
                        • Turn off or disable automatic screen locking in these settings. You may also need to check Power Management settings and disable "Turn off screen" options there to prevent conflicts.
                      • Set XScreenSaver to Autostart:
                        • In System Settings, go to Startup and Shutdown > Autostart.
                        • Click Add Application or Add Login Script.
                        • In the command field, type xscreensaver --no-splash.
                        • Make sure the entry is enabled.
                      • Log out and Log back in:
                        • Logging out and then logging back in will ensure the changes take effect and the xscreensaver daemon starts with your session.
                      • Configure XScreenSaver settings:
                        • After logging back in, you can run the xscreensaver-demo command (e.g., by pressing Alt+F2 and typing the command) to access the settings and choose your desired screensavers.
                      This configuration will prevent the warning message from appearing in the future and allow XScreenSaver to manage your screen blanking and locking behavior.


























                      โ€‹
                      Windows no longer obstruct my view.
                      Using Kubuntu Linux since March 23, 2007.
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmesโ€‹

                      Comment


                        #12
                        I did everything as you described. After restarting, I ran the โ€œxscreensaver-demoโ€ command and the Xscreensaver settings opened, but the Xcreensaver again requested to start โ€œDisplay โ€:0".


                        I did that.

                        Now I logged out and back in, but the Xscreensaver does not start on its own.


                        I open the Xcreensaver settings again and am asked to start the command โ€œDisplay โ€:0" again.

                        ๐Ÿ“Œ So shouldn't this command be added to the command field in the Xscreensaver autostart?๐Ÿ“Œ



                        Click image for larger version

Name:	Bildschirmfoto_20260206_191436.png
Views:	145
Size:	81.4 KB
ID:	690245โ€‹








                        โ€‹
                        ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                        ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                        ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                        ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                        โ€‹

                        Comment


                          #13
                          Autostart shows that Xscreensaver failed to start automatically. (Without the command โ€œDisplay โ€:0").
                          โ€‹

                          Click image for larger version

Name:	Bildschirmfoto_20260206_192618.png
Views:	141
Size:	43.2 KB
ID:	690247โ€‹
                          ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                          ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                          ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                          ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                          โ€‹

                          Comment


                            #14
                            The autostart of XScreensaver looks like this:
                            โ€‹

                            Click image for larger version

Name:	1. Bildschirmfoto_20260206_192641.png
Views:	139
Size:	74.8 KB
ID:	690249โ€‹ Click image for larger version

Name:	2. Bildschirmfoto_20260206_192703.png
Views:	141
Size:	60.6 KB
ID:	690250Click image for larger version

Name:	5. Bildschirmfoto_20260206_192835.png
Views:	145
Size:	81.6 KB
ID:	690253โ€‹Click image for larger version

Name:	4. Bildschirmfoto_20260206_192749.png
Views:	136
Size:	66.1 KB
ID:	690252โ€‹Click image for larger version

Name:	3. Bildschirmfoto_20260206_192726.png
Views:	141
Size:	65.3 KB
ID:	690251โ€‹โ€‹
                            ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                            ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                            ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                            ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                            โ€‹

                            Comment


                              #15
                              This error was actually easy to fix, but first I had to figure it out...

                              The user @Krovikan from the KDE Discuss Forum helped me with this.

                              In the autostart folder of Xscreensaver,

                              I had entered "xscreensaver-settings" instead of "xscreensaver" as the programme name.

                              Now Xscreensaver works flawlessly in Kubuntu 25.10 KDE Plasma.



                              Click image for larger version

Name:	fiesta3.gif
Views:	109
Size:	1.3 KB
ID:	690300โ€‹
                              ๐Ÿ€Kubuntu 26.04 LTS KDE Plasma X11๐Ÿ€
                              ๐Ÿ€Intel Core i7-14700K (28 CPUs), ~3.4GHz, 32 GB RAM, 1 TB SSD, 8 TB HDD ๐Ÿ€
                              ๐Ÿ€Samsung Galaxy A 54 5G | Android 16๐Ÿ€
                              ๐Ÿ€Vivaldi Browser Work Spaces changed my Work Flow๐Ÿ€โ€‹

                              โ€‹

                              Comment

                              Users Viewing This Topic

                              Collapse

                              There are 0 users viewing this topic.

                              Working...
                              X