Run script on Awesome WM startup





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I'm trying to run a script on Awesome WM start after the login screen (not on the awesome --replace or awesome.restart()).



Does anyone knows the way? No matter is it some kind of /etc/rc.* script or the ~/.config/awesome/rc.lua solution.



Thanks!










share|improve this question































    1















    I'm trying to run a script on Awesome WM start after the login screen (not on the awesome --replace or awesome.restart()).



    Does anyone knows the way? No matter is it some kind of /etc/rc.* script or the ~/.config/awesome/rc.lua solution.



    Thanks!










    share|improve this question



























      1












      1








      1








      I'm trying to run a script on Awesome WM start after the login screen (not on the awesome --replace or awesome.restart()).



      Does anyone knows the way? No matter is it some kind of /etc/rc.* script or the ~/.config/awesome/rc.lua solution.



      Thanks!










      share|improve this question
















      I'm trying to run a script on Awesome WM start after the login screen (not on the awesome --replace or awesome.restart()).



      Does anyone knows the way? No matter is it some kind of /etc/rc.* script or the ~/.config/awesome/rc.lua solution.



      Thanks!







      scripts startup awesome lua






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 13 hours ago







      KhaimovMR

















      asked 16 hours ago









      KhaimovMRKhaimovMR

      566




      566






















          1 Answer
          1






          active

          oldest

          votes


















          1














          As a workaround, adding those signals handlers into ~/.config/awesome/rc.lua:



          awesome.connect_signal(
          'exit',
          function(args)
          awful.util.spawn('touch ~/.awesome-restart')
          end
          )

          awesome.connect_signal(
          'startup',
          function(args)
          awful.util.spawn('bash -c "rm ~/.awesome-restart || ~/script-to-run-on-startup.sh"')
          end
          )


          Explaining:
          - on the exit signal, that performs only on awesome restart we're creating a flag file, that tells to the startup signal that this startup is going immediately after the awesome restart
          - on the startup signal fired we're removing this flag and if it doesn't remove successfully (doesn't exist) - we're running our startup-only script.



          PS: Checked - the exit signal doesn't fire on sudo reboot, so it won't be inappropriately fired on full system restart.






          share|improve this answer


























            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%2f1133769%2frun-script-on-awesome-wm-startup%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














            As a workaround, adding those signals handlers into ~/.config/awesome/rc.lua:



            awesome.connect_signal(
            'exit',
            function(args)
            awful.util.spawn('touch ~/.awesome-restart')
            end
            )

            awesome.connect_signal(
            'startup',
            function(args)
            awful.util.spawn('bash -c "rm ~/.awesome-restart || ~/script-to-run-on-startup.sh"')
            end
            )


            Explaining:
            - on the exit signal, that performs only on awesome restart we're creating a flag file, that tells to the startup signal that this startup is going immediately after the awesome restart
            - on the startup signal fired we're removing this flag and if it doesn't remove successfully (doesn't exist) - we're running our startup-only script.



            PS: Checked - the exit signal doesn't fire on sudo reboot, so it won't be inappropriately fired on full system restart.






            share|improve this answer






























              1














              As a workaround, adding those signals handlers into ~/.config/awesome/rc.lua:



              awesome.connect_signal(
              'exit',
              function(args)
              awful.util.spawn('touch ~/.awesome-restart')
              end
              )

              awesome.connect_signal(
              'startup',
              function(args)
              awful.util.spawn('bash -c "rm ~/.awesome-restart || ~/script-to-run-on-startup.sh"')
              end
              )


              Explaining:
              - on the exit signal, that performs only on awesome restart we're creating a flag file, that tells to the startup signal that this startup is going immediately after the awesome restart
              - on the startup signal fired we're removing this flag and if it doesn't remove successfully (doesn't exist) - we're running our startup-only script.



              PS: Checked - the exit signal doesn't fire on sudo reboot, so it won't be inappropriately fired on full system restart.






              share|improve this answer




























                1












                1








                1







                As a workaround, adding those signals handlers into ~/.config/awesome/rc.lua:



                awesome.connect_signal(
                'exit',
                function(args)
                awful.util.spawn('touch ~/.awesome-restart')
                end
                )

                awesome.connect_signal(
                'startup',
                function(args)
                awful.util.spawn('bash -c "rm ~/.awesome-restart || ~/script-to-run-on-startup.sh"')
                end
                )


                Explaining:
                - on the exit signal, that performs only on awesome restart we're creating a flag file, that tells to the startup signal that this startup is going immediately after the awesome restart
                - on the startup signal fired we're removing this flag and if it doesn't remove successfully (doesn't exist) - we're running our startup-only script.



                PS: Checked - the exit signal doesn't fire on sudo reboot, so it won't be inappropriately fired on full system restart.






                share|improve this answer















                As a workaround, adding those signals handlers into ~/.config/awesome/rc.lua:



                awesome.connect_signal(
                'exit',
                function(args)
                awful.util.spawn('touch ~/.awesome-restart')
                end
                )

                awesome.connect_signal(
                'startup',
                function(args)
                awful.util.spawn('bash -c "rm ~/.awesome-restart || ~/script-to-run-on-startup.sh"')
                end
                )


                Explaining:
                - on the exit signal, that performs only on awesome restart we're creating a flag file, that tells to the startup signal that this startup is going immediately after the awesome restart
                - on the startup signal fired we're removing this flag and if it doesn't remove successfully (doesn't exist) - we're running our startup-only script.



                PS: Checked - the exit signal doesn't fire on sudo reboot, so it won't be inappropriately fired on full system restart.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 13 hours ago

























                answered 15 hours ago









                KhaimovMRKhaimovMR

                566




                566






























                    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%2f1133769%2frun-script-on-awesome-wm-startup%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

                    GameSpot

                    connect to host localhost port 22: Connection refused

                    Getting a Wifi WPA2 wifi connection