Forum Discussion

edtpg's avatar
edtpg
New Contributor
11 months ago
Solved

Linux desktop client crashes on startup

Since updating to the latest version of the client, the Linux desktop client consistently crashes on first startup, and sometimes crashes again after already running. I have the browser extension ...
linux
  • 1P_Dave's avatar
    1P_Dave
    8 months ago

    Hello folks, 

    I'm sorry that 1Password for Linux is crashing when you first first boot your device. This is a known issue that our development team is investigating and hopes to fix in a future update to 1Password. While I don't have a timeline on when a fix will be released, the fix will be noted in our release notes as soon as it is available. 

    As noted in this thread, the issue should only affect the first launch after boot and subsequent launches of the 1Password app should work normally. If you're seeing different behaviour then please reach out to support@1Password.com so that we can dig deeper.

    -Dave

xazac's avatar
xazac
Occasional Contributor
10 months ago

I have the same issue on a fresh install of Ubuntu 24.10.
I installed it through Terminal in order to run it outside the sandbox.

It always crashes on startup and I also have another very annoying issue: when I unlock 1Password I got a system prompt to unlock the system keychain.

This is very frustrating, you really need to pay more attention on Linux versions.

  • trondhindenes's avatar
    trondhindenes
    New Contributor
    8 months ago

    Just wanted to report that this is consistently happening to me as well. 

    2025-02-05T11:21:05.351665+01:00 trond-x1 systemd[4127]: Started app-gnome-1password-90293.scope - Application launched by gnome-shell.
2025-02-05T11:21:05.533488+01:00 trond-x1 1password.desktop[90293]: INFO  2025-02-05T10:21:05.533+00:00 ThreadId(1) [1P:foundation/op-log/src/lib.rs:664] Removed 3 old log files
2025-02-05T11:21:05.535153+01:00 trond-x1 1password.desktop[90293]: INFO  2025-02-05T10:21:05.535+00:00 ThreadId(1) [1P:op-settings/src/store/json_store.rs:73] Settings file created @ 2024-09-13 18:38:50.848754642 UTC and last modified @ 2024-11-10 11:49:38.375714569 UTC
2025-02-05T11:21:05.536074+01:00 trond-x1 1password.desktop[90293]: INFO  2025-02-05T10:21:05.536+00:00 ThreadId(1) [client:typescript] Client starting.
2025-02-05T11:21:09.277899+01:00 trond-x1 1password.desktop[90293]: [90293:0205/112109.277080:ERROR:browser_main_loop.cc(283)] GLib-GObject: ../../../gobject/gsignal.c:2685: instance '0x1e64000f8090' has no handler with id '1358'

    If I try starting it again, in syslog I can see:

    2025-02-05T11:21:11.713750+01:00 trond-x1 systemd[4127]: Started app-gnome-1password-90449.scope - Application launched by gnome-shell.
2025-02-05T11:21:11.891735+01:00 trond-x1 1password.desktop[90449]: INFO  2025-02-05T10:21:11.891+00:00 ThreadId(14) [1P:op-settings/src/store/json_store.rs:73] Settings file created @ 2024-09-13 18:38:50.848754642 UTC and last modified @ 2024-11-10 11:49:38.375714569 UTC
2025-02-05T11:21:11.893193+01:00 trond-x1 1password.desktop[90449]: INFO  2025-02-05T10:21:11.893+00:00 ThreadId(14) [client:typescript] 1Password is already running, closing.
2025-02-05T11:21:11.893522+01:00 trond-x1 1password.desktop[90293]: #033[38;5;196mERROR#033[0m #033[38;5;196m2025-02-05T10:21:11.893+00:00#033[0m runtime-worker(ThreadId(3)) [1P:ffi/op-core-node/src/lib.rs:66] #033[38;5;196mAttempted to notify uninitialized App#033[0m

    After having tried a couple of times (usually 3-4) the app will open. Its terribly annoying.