1Password Desktop Auto-Start on Omarchy

[lifeiscontent]

This walkthrough documents how to run the 1Password desktop client as a user-level systemd service on Arch Linux. It was verified on a workstation running systemd 255 and 1Password 8.10.40.

1. Verify the 1Password installation

ls /opt/1Password/1password

If the binary is missing, install the latest Arch build from the official download page.

2. Create the systemd user unit

Save the following unit file to ~/.config/systemd/user/1password.service (create the directory tree if it does not exist):

[Unit]
Description=1Password Linux desktop client
Documentation=https://support.1password.com/
Wants=graphical-session.target
After=graphical-session.target
ConditionEnvironment=DISPLAY

[Service]
Type=simple
ExecStart=/opt/1Password/1password
Restart=on-abnormal
RestartSec=5s
OOMPolicy=continue
KeyringMode=inherit

[Install]
WantedBy=xdg-desktop-autostart.target

graphical-session.target is available in the user manager on Arch, so it avoids the "Unit display-manager.service not found" error that appears when the user instance cannot see the system-level display-manager.service dependency.

3. Reload and enable the service

systemctl --user daemon-reload
systemctl --user enable --now 1password.service

systemctl stores the enablement symlink under ~/.config/systemd/user/xdg-desktop-autostart.target.wants/, so the service starts automatically on login.

4. Confirm the service is running

systemctl --user status 1password.service --no-pager

You should see an "active (running)" status and one or more 1password processes under your user slice.

5. Troubleshooting

• Collect service logs: journalctl --user-unit 1password.service -b
• If 1Password updates, the service restarts automatically. To trigger a manual restart run systemctl --user restart 1password.service.
• Ensure DISPLAY is exported in your login environment. The ConditionEnvironment=DISPLAY guard prevents the unit from starting in non-graphical sessions.

With this setup the desktop client will launch as soon as your graphical session starts and inherit access to the login keyring via PAM.