Forum Discussion

Recent_Convert's avatar
Recent_Convert
Occasional Contributor
6 days ago

Change to autostart on Linux in 8.12.12

The new Start at Login option in 8.12.12 places a .desktop file in ~/.config/autostart.  I've always used this to autostart 1Password at login.  The problem is, 1Password now overwrites my file's Exec= with a --silent flag suppressing the window for me to authenticate and unlock my browser.  I've changed permissions on the .desktop file to read-only so that 1Password cannot modify the file but this is not ideal.

I've tried disabling the Start at Login option, which I would presume would then leave my folder alone, but instead it will seek out and delete any 1password.desktop file I place in there every time the application starts.  Please have some option to allow the desktop application to OPEN at login rather than forcing it to start in the background as not all desktop environments have a tray (GNOME being the obvious one) for the user to invoke a backgrounded app in order to authenticate at login.

Though all things being equal I'd really prefer that you not modify files that I create.

linux

2 Replies

  • AJCxZ0's avatar
    AJCxZ0
    Silver Expert
    1 hour ago
    Recent_Convert wrote:

    The new Start at Login option in 8.12.12 places a .desktop file in ~/.config/autostart

    I noticed this when the freshly returned "Unexpected error" window appeared before I had the chance to launch 1Password.

    1Password_Community​ staff, please tell the developers that they do not choose what applications we autostart on our desktops and should never make such changes without our consent. We have the tools to autostart whichever applications we want on our desktop, however it does no harm to offer us this option within the application.
    It would be nice to provide a `1password.desktop` which offers the options to start "silent", etc. Someone already did the work for you (and licensed it for your use) ten months ago.

     

    • Recent_Convert's avatar
      Recent_Convert
      Occasional Contributor
      1 hour ago

      The linked solution would be great but it does lack my preferred method of autostart which is just opening the app for me to authenticate without a flag (though maybe --lock or --toggle does something similar, I didn't check).  The important thing to me would be the ability, either manually or through a UI, to configure the autostart in the way I prefer rather than to chattr on the file to make it work the way I want.