• RoyaltyInTraining@lemmy.world
    link
    fedilink
    arrow-up
    57
    arrow-down
    2
    ·
    2 days ago

    Weird that it doesn’t work. The usual way to run scripts on startup is through systemd units though. That has the added benefits of automatically logging all output and letting you control it through commands like systemctl enable <unit name>. It’s a really neat system, and I highly recommend learning it if you see yourself doing this kind of automation more often.

    • ulterno
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      I do that when I want it running with root privileges.
      In case of user privileges though, the autostart is a better idea.

      • dbx12
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        You was m can use user units too if you want them scoped to your user.

    • MonkderVierte@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      2 days ago

      The usual way to run scripts on startup is through systemd units though.

      Even worse than via some utility of your window manager