xscreensaver on 18.10 MATE - not starting












1















I have this on two machines with the same problem. This has only recently started happening -- last couple weeks or so with frequent if not daily updates.



An 18.04 machine is working fine.



No errors in any logs.



Requested in comments:



$ dpkg -l | grep ^ii | grep screensaver
ii libopengl-xscreensaver-perl 0.05-1build4 amd64 Perl module for writing OpenGL-based XScreenSaver hacks
ii mate-screensaver-common 1.20.2-1 all MATE screen saver and locker (common files)
ii xscreensaver 5.36-1ubuntu1 amd64 Screensaver daemon and frontend for X11
ii xscreensaver-data 5.36-1ubuntu1 amd64 Screen saver modules for screensaver frontends
ii xscreensaver-data-extra 5.36-1ubuntu1 amd64 Extra screen saver modules for screensaver frontends
ii xscreensaver-gl 5.36-1ubuntu1 amd64 GL(Mesa) screen saver modules for screensaver frontends
ii xscreensaver-gl-extra 5.36-1ubuntu1 amd64 Extra GL(Mesa) screen saver modules for screensaver frontends
ii xscreensaver-screensaver-bsod 5.36-1ubuntu1 amd64 BSOD screen saver module from XScreenSaver
ii xscreensaver-screensaver-dizzy 0.3-3 all Graphics demo that makes you dizzy (XScreenSaver hack)
ii xscreensaver-screensaver-webcollage 5.36-1ubuntu1 amd64 Webcollage screen saver module from XScreenSaver


Update after removing mate-screensaver



On one of the 18.10 machines xscreensaver is now working. At some point, for reasons I've forgotten, I'd created a startup desktop file and a service file so I removed the startup.



On the other 18.10 machine it is not working.



The situation now:



 $ dpkg -l | grep ^ii | grep screensaver | grep -v xscreen
$

$ systemctl --user status xscreensaver
● xscreensaver.service - XScreenSaver
Loaded: loaded (/home/stephen/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-02-03 18:00:25 PST; 14h ago
Main PID: 1264 (xscreensaver)
CGroup: /user.slice/user-1000.slice/user@1000.service/xscreensaver.service
└─1264 /usr/bin/xscreensaver -nosplash









share|improve this question





























    1















    I have this on two machines with the same problem. This has only recently started happening -- last couple weeks or so with frequent if not daily updates.



    An 18.04 machine is working fine.



    No errors in any logs.



    Requested in comments:



    $ dpkg -l | grep ^ii | grep screensaver
    ii libopengl-xscreensaver-perl 0.05-1build4 amd64 Perl module for writing OpenGL-based XScreenSaver hacks
    ii mate-screensaver-common 1.20.2-1 all MATE screen saver and locker (common files)
    ii xscreensaver 5.36-1ubuntu1 amd64 Screensaver daemon and frontend for X11
    ii xscreensaver-data 5.36-1ubuntu1 amd64 Screen saver modules for screensaver frontends
    ii xscreensaver-data-extra 5.36-1ubuntu1 amd64 Extra screen saver modules for screensaver frontends
    ii xscreensaver-gl 5.36-1ubuntu1 amd64 GL(Mesa) screen saver modules for screensaver frontends
    ii xscreensaver-gl-extra 5.36-1ubuntu1 amd64 Extra GL(Mesa) screen saver modules for screensaver frontends
    ii xscreensaver-screensaver-bsod 5.36-1ubuntu1 amd64 BSOD screen saver module from XScreenSaver
    ii xscreensaver-screensaver-dizzy 0.3-3 all Graphics demo that makes you dizzy (XScreenSaver hack)
    ii xscreensaver-screensaver-webcollage 5.36-1ubuntu1 amd64 Webcollage screen saver module from XScreenSaver


    Update after removing mate-screensaver



    On one of the 18.10 machines xscreensaver is now working. At some point, for reasons I've forgotten, I'd created a startup desktop file and a service file so I removed the startup.



    On the other 18.10 machine it is not working.



    The situation now:



     $ dpkg -l | grep ^ii | grep screensaver | grep -v xscreen
    $

    $ systemctl --user status xscreensaver
    ● xscreensaver.service - XScreenSaver
    Loaded: loaded (/home/stephen/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
    Active: active (running) since Sun 2019-02-03 18:00:25 PST; 14h ago
    Main PID: 1264 (xscreensaver)
    CGroup: /user.slice/user-1000.slice/user@1000.service/xscreensaver.service
    └─1264 /usr/bin/xscreensaver -nosplash









    share|improve this question



























      1












      1








      1


      0






      I have this on two machines with the same problem. This has only recently started happening -- last couple weeks or so with frequent if not daily updates.



      An 18.04 machine is working fine.



      No errors in any logs.



      Requested in comments:



      $ dpkg -l | grep ^ii | grep screensaver
      ii libopengl-xscreensaver-perl 0.05-1build4 amd64 Perl module for writing OpenGL-based XScreenSaver hacks
      ii mate-screensaver-common 1.20.2-1 all MATE screen saver and locker (common files)
      ii xscreensaver 5.36-1ubuntu1 amd64 Screensaver daemon and frontend for X11
      ii xscreensaver-data 5.36-1ubuntu1 amd64 Screen saver modules for screensaver frontends
      ii xscreensaver-data-extra 5.36-1ubuntu1 amd64 Extra screen saver modules for screensaver frontends
      ii xscreensaver-gl 5.36-1ubuntu1 amd64 GL(Mesa) screen saver modules for screensaver frontends
      ii xscreensaver-gl-extra 5.36-1ubuntu1 amd64 Extra GL(Mesa) screen saver modules for screensaver frontends
      ii xscreensaver-screensaver-bsod 5.36-1ubuntu1 amd64 BSOD screen saver module from XScreenSaver
      ii xscreensaver-screensaver-dizzy 0.3-3 all Graphics demo that makes you dizzy (XScreenSaver hack)
      ii xscreensaver-screensaver-webcollage 5.36-1ubuntu1 amd64 Webcollage screen saver module from XScreenSaver


      Update after removing mate-screensaver



      On one of the 18.10 machines xscreensaver is now working. At some point, for reasons I've forgotten, I'd created a startup desktop file and a service file so I removed the startup.



      On the other 18.10 machine it is not working.



      The situation now:



       $ dpkg -l | grep ^ii | grep screensaver | grep -v xscreen
      $

      $ systemctl --user status xscreensaver
      ● xscreensaver.service - XScreenSaver
      Loaded: loaded (/home/stephen/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
      Active: active (running) since Sun 2019-02-03 18:00:25 PST; 14h ago
      Main PID: 1264 (xscreensaver)
      CGroup: /user.slice/user-1000.slice/user@1000.service/xscreensaver.service
      └─1264 /usr/bin/xscreensaver -nosplash









      share|improve this question
















      I have this on two machines with the same problem. This has only recently started happening -- last couple weeks or so with frequent if not daily updates.



      An 18.04 machine is working fine.



      No errors in any logs.



      Requested in comments:



      $ dpkg -l | grep ^ii | grep screensaver
      ii libopengl-xscreensaver-perl 0.05-1build4 amd64 Perl module for writing OpenGL-based XScreenSaver hacks
      ii mate-screensaver-common 1.20.2-1 all MATE screen saver and locker (common files)
      ii xscreensaver 5.36-1ubuntu1 amd64 Screensaver daemon and frontend for X11
      ii xscreensaver-data 5.36-1ubuntu1 amd64 Screen saver modules for screensaver frontends
      ii xscreensaver-data-extra 5.36-1ubuntu1 amd64 Extra screen saver modules for screensaver frontends
      ii xscreensaver-gl 5.36-1ubuntu1 amd64 GL(Mesa) screen saver modules for screensaver frontends
      ii xscreensaver-gl-extra 5.36-1ubuntu1 amd64 Extra GL(Mesa) screen saver modules for screensaver frontends
      ii xscreensaver-screensaver-bsod 5.36-1ubuntu1 amd64 BSOD screen saver module from XScreenSaver
      ii xscreensaver-screensaver-dizzy 0.3-3 all Graphics demo that makes you dizzy (XScreenSaver hack)
      ii xscreensaver-screensaver-webcollage 5.36-1ubuntu1 amd64 Webcollage screen saver module from XScreenSaver


      Update after removing mate-screensaver



      On one of the 18.10 machines xscreensaver is now working. At some point, for reasons I've forgotten, I'd created a startup desktop file and a service file so I removed the startup.



      On the other 18.10 machine it is not working.



      The situation now:



       $ dpkg -l | grep ^ii | grep screensaver | grep -v xscreen
      $

      $ systemctl --user status xscreensaver
      ● xscreensaver.service - XScreenSaver
      Loaded: loaded (/home/stephen/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
      Active: active (running) since Sun 2019-02-03 18:00:25 PST; 14h ago
      Main PID: 1264 (xscreensaver)
      CGroup: /user.slice/user-1000.slice/user@1000.service/xscreensaver.service
      └─1264 /usr/bin/xscreensaver -nosplash






      mate xscreensaver






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 4 at 16:56







      Stephen Boston

















      asked Feb 3 at 19:05









      Stephen BostonStephen Boston

      8252720




      8252720






















          1 Answer
          1






          active

          oldest

          votes


















          1














          At first you should remove other screensavers (MATE Screen Saver in your case) from system to prevent interference:



          sudo apt purge mate-screensaver mate-screensaver-common


          Then enable XScreeSaver autostart via systemd user's service:



          systemctl --user enable xscreensaver.service
          systemctl --user start xscreensaver.service


             Note: for debugging you can use systemctl --user status xscreensaver.service.



          Then wait for timeout and screensaver activation.






          share|improve this answer
























          • I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

            – Stephen Boston
            Feb 4 at 16:58













          • I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

            – N0rbert
            Feb 4 at 19:57











          • Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

            – Stephen Boston
            Feb 4 at 20:41











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115332%2fxscreensaver-on-18-10-mate-not-starting%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          At first you should remove other screensavers (MATE Screen Saver in your case) from system to prevent interference:



          sudo apt purge mate-screensaver mate-screensaver-common


          Then enable XScreeSaver autostart via systemd user's service:



          systemctl --user enable xscreensaver.service
          systemctl --user start xscreensaver.service


             Note: for debugging you can use systemctl --user status xscreensaver.service.



          Then wait for timeout and screensaver activation.






          share|improve this answer
























          • I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

            – Stephen Boston
            Feb 4 at 16:58













          • I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

            – N0rbert
            Feb 4 at 19:57











          • Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

            – Stephen Boston
            Feb 4 at 20:41
















          1














          At first you should remove other screensavers (MATE Screen Saver in your case) from system to prevent interference:



          sudo apt purge mate-screensaver mate-screensaver-common


          Then enable XScreeSaver autostart via systemd user's service:



          systemctl --user enable xscreensaver.service
          systemctl --user start xscreensaver.service


             Note: for debugging you can use systemctl --user status xscreensaver.service.



          Then wait for timeout and screensaver activation.






          share|improve this answer
























          • I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

            – Stephen Boston
            Feb 4 at 16:58













          • I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

            – N0rbert
            Feb 4 at 19:57











          • Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

            – Stephen Boston
            Feb 4 at 20:41














          1












          1








          1







          At first you should remove other screensavers (MATE Screen Saver in your case) from system to prevent interference:



          sudo apt purge mate-screensaver mate-screensaver-common


          Then enable XScreeSaver autostart via systemd user's service:



          systemctl --user enable xscreensaver.service
          systemctl --user start xscreensaver.service


             Note: for debugging you can use systemctl --user status xscreensaver.service.



          Then wait for timeout and screensaver activation.






          share|improve this answer













          At first you should remove other screensavers (MATE Screen Saver in your case) from system to prevent interference:



          sudo apt purge mate-screensaver mate-screensaver-common


          Then enable XScreeSaver autostart via systemd user's service:



          systemctl --user enable xscreensaver.service
          systemctl --user start xscreensaver.service


             Note: for debugging you can use systemctl --user status xscreensaver.service.



          Then wait for timeout and screensaver activation.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 3 at 20:00









          N0rbertN0rbert

          23.5k650112




          23.5k650112













          • I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

            – Stephen Boston
            Feb 4 at 16:58













          • I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

            – N0rbert
            Feb 4 at 19:57











          • Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

            – Stephen Boston
            Feb 4 at 20:41



















          • I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

            – Stephen Boston
            Feb 4 at 16:58













          • I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

            – N0rbert
            Feb 4 at 19:57











          • Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

            – Stephen Boston
            Feb 4 at 20:41

















          I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

          – Stephen Boston
          Feb 4 at 16:58







          I've added more info to the question. The service was enabled on both machines. I removed the mate screensaver. It was installed to only one of the machines and removing it has not fixed that machine.

          – Stephen Boston
          Feb 4 at 16:58















          I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

          – N0rbert
          Feb 4 at 19:57





          I'm sorry, but I have clean VM, and I can't reproduce your issue on it. Consider to check system integrity with debsums, and/or create clean new user profile and test here...

          – N0rbert
          Feb 4 at 19:57













          Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

          – Stephen Boston
          Feb 4 at 20:41





          Nope. Logged in as other user makes no difference. Oh well. Maybe I'll try switching back to mate-screensaver on this machine. I really just want the blanking.

          – Stephen Boston
          Feb 4 at 20:41


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115332%2fxscreensaver-on-18-10-mate-not-starting%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕