• 𝕸𝖔𝖘𝖘
    link
    fedilink
    English
    1082 days ago

    I’ve found out the hard way: Running the script during startup, and running it using the proper user authorization, are two different things.

      • @[email protected]OP
        link
        fedilink
        English
        322 days ago

        You’re right and I’m dumb. I forgot to absolute-ify one of the paths, which caused the script to be dependent on my user environment, which isn’t loaded by the desktop file.

      • @[email protected]OP
        link
        fedilink
        English
        202 days ago

        Knowing that the environment is finicky, I made sure to only use absolute paths to all files and executables.

        But thanks for the hint.

        • @ogeist
          link
          72 days ago

          What are you using as a Desktop Environment? Certain with DEs the Autostart programs need to be added in the config file.

            • @ogeist
              link
              2
              edit-2
              2 days ago

              According to the Arch Wiki you need to place the .desktop file in:

              ~/.config/autostart/*****.desktop
              

              You also need to add the following line to the .desktop file:

              X-GNOME-Autostart-enabled=true
              

              But that’s probably the hard way to do it, I think the settings panel should also have a Startup Application tab.

              • @[email protected]OP
                link
                fedilink
                English
                22 days ago

                Thanks for looking that up. That’s where my desktop file is located. And it has the X-GNOME-Autostart-enabled=true line. The settings panel does have a Startup Application tab, and that’s what I used. It created the .desktop file in the appropriate location.

                • @ogeist
                  link
                  22 days ago

                  surprised_pikachu_face.jpeg

                  Check your journald and/or make your script log it’s actions.

                  Script > ~/script.log
                  
                  • @[email protected]OP
                    link
                    fedilink
                    English
                    52 days ago

                    Thank for your help. Upon looking at it again I noticed the one filepath that relied on my profile being loaded. Corrected that. Works now.

                    Trés stupide