1password crash after long idle time

bedilbek
bedilbek
Community Member
in Linux

It's been a month and it's really frustrating!

I have been using 1password at least for 2 years on linux ubuntu on the same environment without any issues, and I thought how wonderful one tech company can have such an amazing product. However, it all started around 1 month ago, when I see 1password crash periodically after long idle times of no use. I don't remember what kind of the OS configuration change I have made, but I know that I did some tinkering on the OS configuration, and after that 1password started crashing, I have been continuously sending crash reports, however today I decided to share it after no update from the team about any bugfix realeases recently.

I have been using 1password 8.10.36 before moving to BETA. but issue didn't disappear.
So the 2 possible scenarios where I am getting crash:
1. After OS initialization when I want to access 1password for the first time with a keyboard shortcut or from Chrome extension, it crashes
2. I don't use 1password for several hours and then again want to initialize 1password with a keyboard shortcut or from Chrome extension and again it crashes.

As it is my first time, I don't know which log file to share as it may contain credentials, so I can share anything as long as it doesn't contain anything sensitive to me.

1Password Version: 8.10.38-59.BETA
Extension Version: 2.27.1
OS Version: Ubuntu 22.04.4 LTS Jammy Jellyfish 6.5.0-45-generi
Browser: Version 127.0.6533.88 (Official Build) (64-bit)

Comments

  • bedilbek
    bedilbek
    Community Member
     
    INFO  2024-08-17T07:55:19.751+00:00 ThreadId(9) [1P:foundation/op-log/src/lib.rs:638] Removed 2 old log files
INFO  2024-08-17T07:55:19.758+00:00 ThreadId(9) [client:typescript] Client starting.
ERROR 2024-08-17T07:55:24.875+00:00 tokio-runtime-worker(ThreadId(1)) [1P:ffi/op-core-node/src/lib.rs:65] Attempted to notify uninitialized App
INFO  2024-08-17T07:55:50.635+00:00 ThreadId(9) [1P:op-crash-reporting/src/lib.rs:248] sending crash reports
INFO  2024-08-17T07:55:51.496+00:00 ThreadId(9) [1P:op-crash-reporting/src/lib.rs:275] Crash report and Minidump successfully sent
INFO  2024-08-17T07:55:51.516+00:00 ThreadId(9) [1P:op-crash-reporting/src/crash_handler.rs:276] Started crash handler thread
INFO  2024-08-17T07:55:51.517+00:00 ThreadId(9) [1P:op-localization/src/lib.rs:232] system locale detected as 'en-US'
INFO  2024-08-17T07:55:51.517+00:00 ThreadId(9) [1P:op-localization/src/lib.rs:258] selected translations for EN_US based on detected locale en-US
INFO  2024-08-17T07:55:51.518+00:00 ThreadId(9) [status:app/op-app/src/app.rs:622] App::new(1Password for Linux/81038059 (EN_US), /home/<redacted-username>/.config/1Password)
INFO  2024-08-17T07:55:51.563+00:00 ThreadId(9) [1P:data/op-db/src/common/mod.rs:120] Core DB Table Integrity Check Succeeded
INFO  2024-08-17T07:55:51.564+00:00 ThreadId(9) [1P:data/op-db/src/common/mod.rs:134] Core DB Integrity Check Succeeded
INFO  2024-08-17T07:55:51.564+00:00 ThreadId(9) [1P:data/op-db/src/core_db/db.rs:169] Starting Core DB at version: 32
INFO  2024-08-17T07:55:51.589+00:00 ThreadId(9) [1P:data/op-db/src/common/mod.rs:120] Resources DB Table Integrity Check Succeeded
INFO  2024-08-17T07:55:51.590+00:00 ThreadId(9) [1P:data/op-db/src/common/mod.rs:134] Resources DB Integrity Check Succeeded
INFO  2024-08-17T07:55:51.590+00:00 ThreadId(9) [1P:data/op-db/src/resources_db/db.rs:134] Starting Resources DB at version: 1
INFO  2024-08-17T07:55:51.596+00:00 ThreadId(9) [1P:ssh/op-ssh-config/src/lib.rs:324] agent not configured
INFO  2024-08-17T07:55:51.600+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.600+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.601+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.601+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/chromium/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.601+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.602+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.602+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.602+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.602+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.mozilla/native-messaging-hosts/com.1password.1password.json
INFO  2024-08-17T07:55:51.602+00:00 ThreadId(9) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
INFO  2024-08-17T07:55:51.612+00:00 tokio-runtime-worker(ThreadId(1)) [1P:native-messaging/op-native-core-integration/src/lib.rs:332] Starting IPC listener on 1Password-BrowserSupport
ERROR 2024-08-17T07:55:51.613+00:00 ThreadId(9) [1P:ffi/op-core-node/src/lib.rs:417] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
INFO  2024-08-17T07:55:51.613+00:00 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging/op-native-core-integration/src/lib.rs:344] Active native core integration is awaiting messages
INFO  2024-08-17T07:55:51.617+00:00 tokio-runtime-worker(ThreadId(6)) [1P:ssh/op-agent-controller/src/lib.rs:523] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-08-17T07:55:51.618+00:00 tokio-runtime-worker(ThreadId(6)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:524] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
INFO  2024-08-17T07:56:18.512+00:00 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-native-core-integration/src/lib.rs:369] Extension connecting.
INFO  2024-08-17T07:56:18.512+00:00 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-native-core-integration/src/lib.rs:371] Extension connection accepted.
INFO  2024-08-17T08:08:29.041+00:00 tokio-runtime-worker(ThreadId(8)) [1P:app/op-app/src/app/backend/lock_screen.rs:89] System unlock is enabled: true
  • bedilbek
    bedilbek
    Community Member

    As long as I remember crash window appeared somewhere around 2024-08-17T07:55:24.875+00:00 this time

  • Dave_1P
    Dave_1P

    Hello @bedilbek! 👋

    I'm sorry that 1Password for Linux is crashing on your system. I'd like to ask you to create a diagnostics report from your Mac:

    Sending Diagnostics Reports (Linux)

    Attach the diagnostics to an email message addressed to support+forum@1password.com.

    With your email please include:

    Please send the entire file.

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

    -Dave

  • bedilbek
    bedilbek
    Community Member

    This issue actually disappeared after I upgraded to 1Password 8.10.46 on my Linux machine.

  • GreyM1P
    GreyM1P

    @bedilbek

    That's great! The current version of 1Password for Linux is 8.10.50, so I'd recommend you update to that as soon as you can to stay current, but I'm glad to hear the crashing isn't happening any more.