Start 1password as a background service

Options
richbai90
richbai90
Community Member

I just installed the latest 1Password linux beta to use the new SSH features -- which I'm also struggling with but that's for a different post. Instead of starting 1Password at startup, I want to run it as a background process. I have tried to create a unit file to start 1password at startup but for some reason it keeps crashing. From what I can tell it looks like it's catching the fork signal and exiting, but I don't know why it would do that.

This is my unit file:

[Unit]
Description=1Password Password Manager

[Service]
Type=exec
ExecStart=1password --debug --silent
User=rich

[Install]
WantedBy=user.target

And here is the output when I start the service:

× 1password.service - 1Password Password Manager
     Loaded: loaded (/usr/lib/systemd/system/1password.service; enabled; vendor preset: disabled)
     Active: failed (Result: signal) since Fri 2022-05-20 16:04:15 MDT; 10min ago
    Process: 12748 ExecStart=1password --debug --silent (code=killed, signal=TRAP)
   Main PID: 12748 (code=killed, signal=TRAP)
        CPU: 267ms

May 20 16:04:15 richbaird.local systemd[1]: Starting 1Password Password Manager...
May 20 16:04:15 richbaird.local systemd[1]: Started 1Password Password Manager.
May 20 16:04:15 richbaird.local 1password[12748]: INFO  2022-05-20T16:04:15.335 ThreadId(18) [client:typescript] Client starting.
May 20 16:04:15 richbaird.local systemd[1]: 1password.service: Main process exited, code=killed, status=5/TRAP
May 20 16:04:15 richbaird.local systemd[1]: 1password.service: Failed with result 'signal'.

The logs don't provide any additional information:

INFO  2022-05-20T16:24:08.872 ThreadId(18) [client:typescript] Client starting.

1Password Version: 8.8.0-94.BETA
Extension Version: Not Provided
OS Version: OpenSuse Tumbleweed

Comments

  • richbai90
    richbai90
    Community Member
    Options

    Okay I got this working by adding an autostart entry in my xsession startup instead.

  • Thank you for letting us know what worked for you, @richbai90!

This discussion has been closed.