How do you make a systemd service for autostarting RemoteLauncher at boot?












0















I want RemoteLauncher to autostart at boot so I can do things like start/stop/control Kodi on 18.10.



RemoteLauncher is here.



An old method to autostart it is here. (I believe this method has been replaced by Systemd.)



I've tried doing something like this.



The old method does start the java and the service. I can see them running in the System Monitor. But the launcher to start Kodi doesn't start Kodi on the screen. I see Kodi running for less than a minute in the System Monitor, then it disappears.



Starting the service manually in a terminal with /usr/bin/remote-launcher-server does start java and the service, and allows the launcher to start Kodi properly so I can see it on-screen. Another launcher can kill it. But the goal is to have this capability working automatically after booting.



I cannot get the last Systemd method to even get java and the service running after boot. I am at a dead-end, and am not savvy enough with Ubuntu or Systemd to figure it out. I'd really appreciate any help.










share|improve this question





























    0















    I want RemoteLauncher to autostart at boot so I can do things like start/stop/control Kodi on 18.10.



    RemoteLauncher is here.



    An old method to autostart it is here. (I believe this method has been replaced by Systemd.)



    I've tried doing something like this.



    The old method does start the java and the service. I can see them running in the System Monitor. But the launcher to start Kodi doesn't start Kodi on the screen. I see Kodi running for less than a minute in the System Monitor, then it disappears.



    Starting the service manually in a terminal with /usr/bin/remote-launcher-server does start java and the service, and allows the launcher to start Kodi properly so I can see it on-screen. Another launcher can kill it. But the goal is to have this capability working automatically after booting.



    I cannot get the last Systemd method to even get java and the service running after boot. I am at a dead-end, and am not savvy enough with Ubuntu or Systemd to figure it out. I'd really appreciate any help.










    share|improve this question



























      0












      0








      0








      I want RemoteLauncher to autostart at boot so I can do things like start/stop/control Kodi on 18.10.



      RemoteLauncher is here.



      An old method to autostart it is here. (I believe this method has been replaced by Systemd.)



      I've tried doing something like this.



      The old method does start the java and the service. I can see them running in the System Monitor. But the launcher to start Kodi doesn't start Kodi on the screen. I see Kodi running for less than a minute in the System Monitor, then it disappears.



      Starting the service manually in a terminal with /usr/bin/remote-launcher-server does start java and the service, and allows the launcher to start Kodi properly so I can see it on-screen. Another launcher can kill it. But the goal is to have this capability working automatically after booting.



      I cannot get the last Systemd method to even get java and the service running after boot. I am at a dead-end, and am not savvy enough with Ubuntu or Systemd to figure it out. I'd really appreciate any help.










      share|improve this question
















      I want RemoteLauncher to autostart at boot so I can do things like start/stop/control Kodi on 18.10.



      RemoteLauncher is here.



      An old method to autostart it is here. (I believe this method has been replaced by Systemd.)



      I've tried doing something like this.



      The old method does start the java and the service. I can see them running in the System Monitor. But the launcher to start Kodi doesn't start Kodi on the screen. I see Kodi running for less than a minute in the System Monitor, then it disappears.



      Starting the service manually in a terminal with /usr/bin/remote-launcher-server does start java and the service, and allows the launcher to start Kodi properly so I can see it on-screen. Another launcher can kill it. But the goal is to have this capability working automatically after booting.



      I cannot get the last Systemd method to even get java and the service running after boot. I am at a dead-end, and am not savvy enough with Ubuntu or Systemd to figure it out. I'd really appreciate any help.







      java launcher systemd autostart kodi






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 16 at 19:58







      ticotexas

















      asked Jan 15 at 22:03









      ticotexasticotexas

      385




      385






















          1 Answer
          1






          active

          oldest

          votes


















          0














          What worked was just adding /usr/bin/remote-launcher-server as a Startup Application. (I don't know why I was making it so hard.)






          share|improve this answer
























          • This will run the application when you log in, not when the machine boots.

            – PerlDuck
            Jan 17 at 19:01











          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%2f1110076%2fhow-do-you-make-a-systemd-service-for-autostarting-remotelauncher-at-boot%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














          What worked was just adding /usr/bin/remote-launcher-server as a Startup Application. (I don't know why I was making it so hard.)






          share|improve this answer
























          • This will run the application when you log in, not when the machine boots.

            – PerlDuck
            Jan 17 at 19:01
















          0














          What worked was just adding /usr/bin/remote-launcher-server as a Startup Application. (I don't know why I was making it so hard.)






          share|improve this answer
























          • This will run the application when you log in, not when the machine boots.

            – PerlDuck
            Jan 17 at 19:01














          0












          0








          0







          What worked was just adding /usr/bin/remote-launcher-server as a Startup Application. (I don't know why I was making it so hard.)






          share|improve this answer













          What worked was just adding /usr/bin/remote-launcher-server as a Startup Application. (I don't know why I was making it so hard.)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 17 at 17:07









          ticotexasticotexas

          385




          385













          • This will run the application when you log in, not when the machine boots.

            – PerlDuck
            Jan 17 at 19:01



















          • This will run the application when you log in, not when the machine boots.

            – PerlDuck
            Jan 17 at 19:01

















          This will run the application when you log in, not when the machine boots.

          – PerlDuck
          Jan 17 at 19:01





          This will run the application when you log in, not when the machine boots.

          – PerlDuck
          Jan 17 at 19:01


















          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%2f1110076%2fhow-do-you-make-a-systemd-service-for-autostarting-remotelauncher-at-boot%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á

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