1password GUI fails to launch
Hello, I'm trying to run 1Password in a new installation of Pop! OS, installed from the .deb package downloaded from the website. It worked initially, but after running some more software installs and rebooting a couple times, I tried to launch 1Password again and it would display the tray icon, but I couldn't get it to open the application or the quick launch window. I tried to open it from terminal and received an error about not being able to open the ssh config file (which didn't exist yet on my very new installation), so I created that, but still received the following error:
seckert@pop-os:~$ 1password
INFO 2022-07-04T21:37:00.190 ThreadId(14) [client:typescript] Client starting.
INFO 2022-07-04T21:37:00.264 tokio-runtime-worker(ThreadId(11)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Starting IPC listener on 1Password-BrowserSupport
INFO 2022-07-04T21:37:00.265 ThreadId(14) [1P:op-localization/src/lib.rs:236] system locale detected as 'en_US'
INFO 2022-07-04T21:37:00.265 ThreadId(14) [1P:op-localization/src/lib.rs:262] selected translations for EN_US based on detected locale en-US
INFO 2022-07-04T21:37:00.265 ThreadId(14) [status:op-app/src/app.rs:354] App::new(1Password for Linux/80703002 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO 2022-07-04T21:37:00.265 tokio-runtime-worker(ThreadId(10)) [1P:native-messaging/op-native-core-integration/src/lib.rs:293] Active native core integration is awaiting messages
INFO 2022-07-04T21:37:00.265 ThreadId(14) [1P:op-db/src/db.rs:120] Starting DB at version: 25
INFO 2022-07-04T21:37:00.266 ThreadId(14) [1P:ssh/op-ssh-config/src/lib.rs:231] agent not configured
ERROR 2022-07-04T21:37:00.266 ThreadId(14) [1P:ffi/core-node/src/lib.rs:65] Attempted to notify uninitialized App
INFO 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [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 2022-07-04T21:37:00.267 op_executor:invocation_loop(ThreadId(19)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
[7962:0704/213700.272648:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[7915:0704/213700.309460:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
^CINFO 2022-07-04T21:37:06.146 op_executor:invocation_loop(ThreadId(19)) [1P:op-app/src/app/backend/frontend.rs:27] Front end event: window closed
INFO 2022-07-04T21:37:06.146 op_executor:invocation_loop(ThreadId(19)) [1P:op-app/src/app/backend/frontend.rs:66] Front end event: app will quit
So, two issues to report, one that I was able to resolve myself, and one that is ongoing:
- Application launched to system tray, but wouldn't open GUI when no ~/.ssh/config file existed (resolved by creating the file)
- After creating that file, I'm still getting an "Attempted to notify uninitialized app" error on launch. I can see the 1password icon in the system tray, but can't open any GUI elements.
Confirmed that this is happening in both 8.7.3 and the new 8.8.0 beta. I suspect this is still related to the SSH functionality, but I'm not too sure. Any input would be appreciated.
Thanks!
1Password Version: 8.8.0, 8.7.3
Extension Version: Not Provided
OS Version: Pop OS 22.04
Browser:_ Not Provided
Comments
-
Ahoy, @stevethepirate. Sorry you've encountered this problem.
Here's quick idea which I hope will prove informative:
- Pop open a terminal on your OS.
- Run the command
1password --disable-gpu
Does that improve the situation at all? I'll be interested to learn the result of this - let me know and we'll be happy to follow up with you! 👋
0 -
I am having the same situation, 1password launches, creates systray icon, but window is grayed out,
with --disable-gpu i get:INFO 2022-07-08T00:15:52.550 ThreadId(10) [client:typescript] Client starting.
INFO 2022-07-08T00:15:52.629 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Starting IPC listener on 1Password-BrowserSupport
INFO 2022-07-08T00:15:52.629 ThreadId(10) [1P:op-localization/src/lib.rs:236] system locale detected as 'en_US'
INFO 2022-07-08T00:15:52.629 ThreadId(10) [1P:op-localization/src/lib.rs:262] selected translations for EN_US based on detected locale en-US
INFO 2022-07-08T00:15:52.629 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging/op-native-core-integration/src/lib.rs:293] Active native core integration is awaiting messages
INFO 2022-07-08T00:15:52.629 ThreadId(10) [status:op-app/src/app.rs:357] App::new(1Password for Linux/80800165 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO 2022-07-08T00:15:52.630 ThreadId(10) [1P:op-db/src/db.rs:120] Starting DB at version: 25
INFO 2022-07-08T00:15:52.631 ThreadId(10) [1P:ssh/op-ssh-config/src/lib.rs:231] agent not configured
ERROR 2022-07-08T00:15:52.631 ThreadId(10) [1P:ffi/core-node/src/lib.rs:65] Attempted to notify uninitialized App
INFO 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
[838134:0708/001552.635176:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[838093:0708/001552.684611:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[838093:0708/001552.805710:ERROR:browser_main_loop.cc(269)] Gdk: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
^CINFO 2022-07-08T00:16:49.792 op_executor:invocation_loop(ThreadId(15)) [1P:op-app/src/app/backend/frontend.rs:27] Front end event: window closed
INFO 2022-07-08T00:16:49.792 op_executor:invocation_loop(ThreadId(15)) [1P:op-app/src/app/backend/frontend.rs:66] Front end event: app will quitThis is with me deleting all 1password config files ~/*.1pass and ~/.config/1Password (I think that is all..)
I am able to trigger "sign in" in the gui through browser exstensions, and my systray icon is able to launch settings.
Signing in though always ends in a a spinning wheel of death (not beachball, not macos..) - which ends in some error message about not being able to sign on. I have not yet gone to the length of wiresharking the network traffic, as I suspect something else is wrong, as the GUI is .. grey..0 -
Hey Peter, thanks for your response. I tried that and got the same behavior. "Attempted to notify uninitialized app" error in the terminal, and no GUI can be opened.
One new thing I noticed was that when I try to open the 1password window from the system tray icon, the terminal is outputting "INFO 2022-07-07T20:28:32.003 tokio-runtime-worker(ThreadId(10)) [1P:op-app/src/app/backend/unlock.rs:242] System unlock was attempted but we cannot use it."
Let me know if there's anything else I can try here for you.
0 -
I am having the same situation, 1password launches, creates systray icon, but window is grayed out,
with --disable-gpu i get:INFO 2022-07-08T00:15:52.550 ThreadId(10) [client:typescript] Client starting.
INFO 2022-07-08T00:15:52.629 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Starting IPC listener on 1Password-BrowserSupport
INFO 2022-07-08T00:15:52.629 ThreadId(10) [1P:op-localization/src/lib.rs:236] system locale detected as 'en_US'
INFO 2022-07-08T00:15:52.629 ThreadId(10) [1P:op-localization/src/lib.rs:262] selected translations for EN_US based on detected locale en-US
INFO 2022-07-08T00:15:52.629 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging/op-native-core-integration/src/lib.rs:293] Active native core integration is awaiting messages
INFO 2022-07-08T00:15:52.629 ThreadId(10) [status:op-app/src/app.rs:357] App::new(1Password for Linux/80800165 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO 2022-07-08T00:15:52.630 ThreadId(10) [1P:op-db/src/db.rs:120] Starting DB at version: 25
INFO 2022-07-08T00:15:52.631 ThreadId(10) [1P:ssh/op-ssh-config/src/lib.rs:231] agent not configured
ERROR 2022-07-08T00:15:52.631 ThreadId(10) [1P:ffi/core-node/src/lib.rs:65] Attempted to notify uninitialized App
INFO 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.632 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [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 2022-07-08T00:15:52.633 op_executor:invocation_loop(ThreadId(15)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
[838134:0708/001552.635176:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[838093:0708/001552.684611:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[838093:0708/001552.805710:ERROR:browser_main_loop.cc(269)] Gdk: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
^CINFO 2022-07-08T00:16:49.792 op_executor:invocation_loop(ThreadId(15)) [1P:op-app/src/app/backend/frontend.rs:27] Front end event: window closed
INFO 2022-07-08T00:16:49.792 op_executor:invocation_loop(ThreadId(15)) [1P:op-app/src/app/backend/frontend.rs:66] Front end event: app will quitThis is with me deleting all 1password config files ~/*.1pass and ~/.config/1Password (I think that is all..)
I am able to trigger "sing in" in the gui through browser exstensions, and my systray icon is able to launch settings.
Signing in though always ends in a a spinning wheel of death (not beachball, not macos..) - which ends in some error message about not being able to sign on. I have not yet gone to the length of wiresharking the network traffic, as I suspect something else is wrong, as the GUI is .. grey..Another point of information is that I use a physical 2FA device - may be a factor
0 -
Hi folks,
sorry for the delay in response, and thanks for sharing the additional info on this.
Is anyone besides @epicpass using 2FA as well? If so, I'm curious what happens if you disable that temporarily.
In the meantime, we're going to troubleshoot this internally and see if we can both produce the problem and track down a solution. I hope to have more for you shortly!
0 -
I am still uanble to unlock - maybe it's a problem in the communication between 1pass and my yubikey.
0 -
actually, it seems that 1password could not query the yubikey for auth when some of my nfs mounts was bugging - fixing those mounts suddenly gave me yubikey prompt in 1password. No log scouring could have guessed that - other than my experience that nfs bugging lags a whole linux system..
0