change KDE screen locker












4














How can I change whatever program KDE5 uses for screen
locking to slock? AFAICS there is no such option in the
system settings.










share|improve this question



























    4














    How can I change whatever program KDE5 uses for screen
    locking to slock? AFAICS there is no such option in the
    system settings.










    share|improve this question

























      4












      4








      4


      1





      How can I change whatever program KDE5 uses for screen
      locking to slock? AFAICS there is no such option in the
      system settings.










      share|improve this question













      How can I change whatever program KDE5 uses for screen
      locking to slock? AFAICS there is no such option in the
      system settings.







      kde screen-lock






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 14 '17 at 9:10









      phgphg

      644517




      644517






















          1 Answer
          1






          active

          oldest

          votes


















          0














          There is no built-in way in KDE5. You'll have to disable the KDE screen locker, then manually run something to trigger slock. The method is similar to my answer here, but I'll summarise below.



          You can use something like xss-lock to automatically trigger the screensaver. You can start this automatically on login, by creating the following file at ~/.config/autostart/xss-lock.desktop



          [Desktop Entry]
          Exec=xss-lock -- /path/to/slock &
          Type=Application
          Terminal=false
          Name=slock_trigger


          To change the timeout value, use



          $ xset s TIME_IN_SECONDS TIME_IN_SECONDS


          replacing TIME_IN_SECONDS with the number of seconds of idleness before you want it to activate. I don't entirely understand why you need to enter it twice, but that's what worked for me.





          share





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f385999%2fchange-kde-screen-locker%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









            0














            There is no built-in way in KDE5. You'll have to disable the KDE screen locker, then manually run something to trigger slock. The method is similar to my answer here, but I'll summarise below.



            You can use something like xss-lock to automatically trigger the screensaver. You can start this automatically on login, by creating the following file at ~/.config/autostart/xss-lock.desktop



            [Desktop Entry]
            Exec=xss-lock -- /path/to/slock &
            Type=Application
            Terminal=false
            Name=slock_trigger


            To change the timeout value, use



            $ xset s TIME_IN_SECONDS TIME_IN_SECONDS


            replacing TIME_IN_SECONDS with the number of seconds of idleness before you want it to activate. I don't entirely understand why you need to enter it twice, but that's what worked for me.





            share


























              0














              There is no built-in way in KDE5. You'll have to disable the KDE screen locker, then manually run something to trigger slock. The method is similar to my answer here, but I'll summarise below.



              You can use something like xss-lock to automatically trigger the screensaver. You can start this automatically on login, by creating the following file at ~/.config/autostart/xss-lock.desktop



              [Desktop Entry]
              Exec=xss-lock -- /path/to/slock &
              Type=Application
              Terminal=false
              Name=slock_trigger


              To change the timeout value, use



              $ xset s TIME_IN_SECONDS TIME_IN_SECONDS


              replacing TIME_IN_SECONDS with the number of seconds of idleness before you want it to activate. I don't entirely understand why you need to enter it twice, but that's what worked for me.





              share
























                0












                0








                0






                There is no built-in way in KDE5. You'll have to disable the KDE screen locker, then manually run something to trigger slock. The method is similar to my answer here, but I'll summarise below.



                You can use something like xss-lock to automatically trigger the screensaver. You can start this automatically on login, by creating the following file at ~/.config/autostart/xss-lock.desktop



                [Desktop Entry]
                Exec=xss-lock -- /path/to/slock &
                Type=Application
                Terminal=false
                Name=slock_trigger


                To change the timeout value, use



                $ xset s TIME_IN_SECONDS TIME_IN_SECONDS


                replacing TIME_IN_SECONDS with the number of seconds of idleness before you want it to activate. I don't entirely understand why you need to enter it twice, but that's what worked for me.





                share












                There is no built-in way in KDE5. You'll have to disable the KDE screen locker, then manually run something to trigger slock. The method is similar to my answer here, but I'll summarise below.



                You can use something like xss-lock to automatically trigger the screensaver. You can start this automatically on login, by creating the following file at ~/.config/autostart/xss-lock.desktop



                [Desktop Entry]
                Exec=xss-lock -- /path/to/slock &
                Type=Application
                Terminal=false
                Name=slock_trigger


                To change the timeout value, use



                $ xset s TIME_IN_SECONDS TIME_IN_SECONDS


                replacing TIME_IN_SECONDS with the number of seconds of idleness before you want it to activate. I don't entirely understand why you need to enter it twice, but that's what worked for me.






                share











                share


                share










                answered 3 mins ago









                SparhawkSparhawk

                9,34663991




                9,34663991






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2funix.stackexchange.com%2fquestions%2f385999%2fchange-kde-screen-locker%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

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震