1password on Linux "Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure" (Full logs included below)

TheZentester
TheZentester
Community Member

Hello,

I recently installed 1password on my Debian system, it was working as expected. However, in the past 24 hours it seems to no longer stay open when I launch the program. When I launch the program from the command line, I get the following INFO/error logs. I don't know if its related to me trying to enable the SSH key feature - shortly after which I tried to disable due to it not functioning as expected. At the moment, all I'm trying to do is get 1password back up and running.

A few other odd specifics, while it will crash the standalone app and it will not run, when I try to open the vault from the browser extension unlock and load passwords. However, it typically will crash shortly after a single set of credentials are provided and then require reauthentication. It also previously had prompted me to login to the 1password.com website and authenticate with my 3 creds (username, Key, password).

At the moment, all I'm looking for is to get the program back up and running. Any idea what's going on?

INFO  2023-01-12T16:04:02.929 ThreadId(10) [client:typescript] Client starting.
INFO  2023-01-12T16:04:03.049 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Starting IPC listener on 1Password-BrowserSupport
INFO  2023-01-12T16:04:03.049 ThreadId(10) [1P:op-localization/src/lib.rs:241] system locale detected as 'en-US'
INFO  2023-01-12T16:04:03.049 ThreadId(10) [1P:op-localization/src/lib.rs:267] selected translations for EN_US based on detected locale en-US
INFO  2023-01-12T16:04:03.049 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/lib.rs:293] Active native core integration is awaiting messages
INFO  2023-01-12T16:04:03.049 ThreadId(10) [status:op-app/src/app.rs:406] App::new(1Password for Linux/80910043 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO  2023-01-12T16:04:03.049 ThreadId(10) [1P:op-db/src/db.rs:120] Starting DB at version: 26
[1;38;5;196mERROR[0m [1;38;5;196m2023-01-12T16:04:03.050[0m ThreadId(10) [1P:op-app/src/app.rs:491] [1;38;5;196mFailed to read password expiry duration setting: Error("EOF while parsing a value", line: 1, column: 0)[0m
[1;38;5;196mERROR[0m [1;38;5;196m2023-01-12T16:04:03.050[0m ThreadId(10) [1P:ssh/op-ssh-config/src/lib.rs:153] [1;38;5;196mCould not open ssh config file in ~/.ssh/config[0m
[1;38;5;196mERROR[0m [1;38;5;196m2023-01-12T16:04:03.050[0m ThreadId(10) [1P:ffi/op-core-node/src/lib.rs:65] [1;38;5;196mAttempted to notify uninitialized App[0m
[1;38;5;196mERROR[0m [1;38;5;196m2023-01-12T16:04:03.051[0m ThreadId(10) [1P:/builds/dev/core/core/ssh/op-ssh-config/src/lib.rs:140] [1;38;5;196mFailed to start ssh config file watcher: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })[0m
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/chromium/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.051 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.052 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.mozilla/native-messaging-hosts/com.1password.1password.json
INFO  2023-01-12T16:04:03.052 op_executor:invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
INFO  2023-01-12T16:04:03.052 tokio-runtime-worker(ThreadId(8)) [1P:ssh/op-agent-controller/src/desktop.rs:374] SSH Agent has started.
[775333:0112/160403.097520:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed

(1password:775333): Gtk-WARNING **: 16:04:03.230: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Yaru/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Yaru/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)

1Password Version: 8.9.10
Extension Version: 2.5.1
OS Version: Ubuntu 20.04.5 LTS
Browser:_ Firefox

Comments

  • TheZentester
    TheZentester
    Community Member

    I should also mention I installed 1password from downloading the 1password-latest.deb from the website, and running sudo apt install 1password-latest.deb. I also tried to uninstall and reinstall using the same method, but no success.

    Reading the contents of the file in question (image-missing.png), it looks as if the file exists, and is in PNG format:

    ❯ ls -al /usr/share/icons/Yaru/16x16/status/image-missing.png
    -rw-r--r-- 1 root root 535 May 28  2021 /usr/share/icons/Yaru/16x16/status/image-missing.png
    ❯ file /usr/share/icons/Yaru/16x16/status/image-missing.png
    /usr/share/icons/Yaru/16x16/status/image-missing.png: PNG image data, 16 x 16, 8-bit colormap, non-interlaced
    
  • Hey @TheZentester, thanks for reaching out to us. This may not be a 1Password issue specifically. In the provided logs I can see:

    (1password:775333): Gtk-WARNING **: 16:04:03.230: Could not load a pixbuf from icon theme.
    This may indicate that pixbuf loaders or the mime database could not be found.
    

    Could you try updating your mime database and see whether that resolves the issue for you?

    You can do so using sudo update-mime-database /usr/share/mime

    Let me know how that goes!

    Ali

  • TheZentester
    TheZentester
    Community Member

    Thanks for the tip @AliH1P! I actually can't troubleshoot further, as the issue seems to resolved itself. For issue tracking purposes, its hard to pin point what was actually completed, as I experienced a few installs of other 3rd party software, and restarted the system a few times as well. I assume the former action might've updated that database you had mentioned.

  • Hey @TheZentester, you're most welcome. I'm glad to hear the issue seems to have resolved itself 😄

This discussion has been closed.