Authenticate to unlock 1Password frozen prompt on Ubuntu 20.04

nazavo
nazavo
Community Member
edited April 2022 in Linux

After the system goes into the sleep mode most of the time after an unlock I get this prompt. There's nothing that can be done with it though. The window is completely frozen so you can't dismiss it in any way. To get rid of it I resort to killing gnome shell by running following command: pkill -9 "gnome-shell".

Below are logs from today that have been collected:

INFO  2022-04-09T07:59:58.580 ThreadId(19) [1P:op-auto-lock/src/linux.rs:379] X screensaver event detected
INFO  2022-04-09T08:00:28.593 ThreadId(19) [1P:op-auto-lock/src/linux.rs:379] X screensaver event detected
INFO  2022-04-09T08:01:02.204 ThreadId(19) [1P:op-auto-lock/src/linux.rs:379] X screensaver event detected
INFO  2022-04-09T08:01:38.386 tokio-runtime-worker(ThreadId(3)) [1P:native-messaging/op-native-core-integration/src/lib.rs:305] Extension connecting.
INFO  2022-04-09T08:01:38.387 tokio-runtime-worker(ThreadId(3)) [1P:native-messaging/op-native-core-integration/src/lib.rs:307] Extension connection accepted.
INFO  2022-04-09T08:02:06.403 tokio-runtime-worker(ThreadId(3)) [1P:op-data-layer/src/load.rs:136] loaded 1210 items in 4 vaults for account: FTXJSFO4TFAIVNFNGLK6UWNFTQ
INFO  2022-04-09T08:02:06.410 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/unlock.rs:86] Lock state changed: Unlocked
INFO  2022-04-09T08:02:06.427 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/frontend.rs:24] Front end event: window closed
ERROR 2022-04-09T08:02:06.536 tokio-runtime-worker(ThreadId(3)) [1P:op-app/src/app/backend/sync.rs:78] Failed to sync account FTXJSFO4TFAIVNFNGLK6UWNFTQ. Error: SyncFailed(HttpError(/builds/dev/core/core/op-b5-client/src/internal/server_connection.rs:78, IoError(IoError(connect error))))
ERROR 2022-04-09T08:02:06.536 tokio-runtime-worker(ThreadId(3)) [1P:op-app/src/app/backend/sync.rs:92] Failed to sync account FTXJSFO4TFAIVNFNGLK6UWNFTQ. Retry on reconnect.
INFO  2022-04-09T08:02:40.084 tokio-runtime-worker(ThreadId(4)) [1P:op-b5-client/src/internal/unauthorized_session.rs:768] Verifying MFA with server...
INFO  2022-04-09T08:02:40.473 tokio-runtime-worker(ThreadId(3)) [1P:op-b5-client/src/internal/unauthorized_session.rs:438] Server verification successful
WARN  2022-04-09T08:02:40.474 tokio-runtime-worker(ThreadId(3)) [1P:op-b5-client/src/internal/unauthorized_session.rs:454] Server did not give us a dsecret
INFO  2022-04-09T08:02:40.837 tokio-runtime-worker(ThreadId(3)) [1P:op-syncer/src/sync_job.rs:276] synced account FTXJSFO4TFAIVNFNGLK6UWNFTQ (0.363386162s)
INFO  2022-04-09T08:02:40.838 tokio-runtime-worker(ThreadId(3)) [1P:op-data-layer/src/file.rs:608] find_and_complete_pending_uploads: 'FTXJSFO4TFAIVNFNGLK6UWNFTQ'
ERROR 2022-04-09T08:02:45.488 tokio-runtime-worker(ThreadId(3)) [1P:/builds/dev/core/core/op-notification-listener/src/lib.rs:247] ConnectionError(Io(Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }))
ERROR 2022-04-09T08:02:49.626 tokio-runtime-worker(ThreadId(2)) [1P:/builds/dev/core/core/op-notification-listener/src/lib.rs:247] ConnectionError(Io(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }))
ERROR 2022-04-09T08:03:05.641 tokio-runtime-worker(ThreadId(2)) [1P:/builds/dev/core/core/op-notification-listener/src/lib.rs:247] ConnectionError(Io(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }))
INFO  2022-04-09T08:04:15.879 tokio-runtime-worker(ThreadId(2)) [1P:op-data-layer/src/sync.rs:512] The B5 Notifier for (FTXJSFO4TFAIVNFNGLK6UWNFTQ) has connected, now monitoring for events.
INFO  2022-04-09T09:32:50.688 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/lock.rs:72] Lock state changed: Locked
INFO  2022-04-09T09:32:50.688 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/lock.rs:94] Locked. Reason: Automatic(ScreenSaverActivated).
INFO  2022-04-09T09:32:50.728 ThreadId(19) [1P:op-auto-lock/src/linux.rs:379] X screensaver event detected
INFO  2022-04-09T09:35:03.030 ThreadId(19) [1P:op-auto-lock/src/linux.rs:379] X screensaver event detected
INFO  2022-04-09T09:39:46.045 tokio-runtime-worker(ThreadId(4)) [1P:op-data-layer/src/load.rs:136] loaded 1210 items in 4 vaults for account: FTXJSFO4TFAIVNFNGLK6UWNFTQ
INFO  2022-04-09T09:39:46.053 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/unlock.rs:86] Lock state changed: Unlocked
INFO  2022-04-09T09:39:46.063 op_executor:invocation_loop(ThreadId(13)) [1P:op-app/src/app/backend/frontend.rs:24] Front end event: window closed
INFO  2022-04-09T09:39:48.475 tokio-runtime-worker(ThreadId(3)) [1P:op-b5-client/src/internal/unauthorized_session.rs:768] Verifying MFA with server...
INFO  2022-04-09T09:39:48.799 tokio-runtime-worker(ThreadId(3)) [1P:op-b5-client/src/internal/unauthorized_session.rs:438] Server verification successful
WARN  2022-04-09T09:39:48.799 tokio-runtime-worker(ThreadId(3)) [1P:op-b5-client/src/internal/unauthorized_session.rs:454] Server did not give us a dsecret
INFO  2022-04-09T09:39:49.152 tokio-runtime-worker(ThreadId(4)) [1P:op-syncer/src/sync_job.rs:276] synced account FTXJSFO4TFAIVNFNGLK6UWNFTQ (0.352676921s)
INFO  2022-04-09T09:39:49.152 tokio-runtime-worker(ThreadId(2)) [1P:op-data-layer/src/file.rs:608] find_and_complete_pending_uploads: 'FTXJSFO4TFAIVNFNGLK6UWNFTQ'
INFO  2022-04-09T09:39:49.999 tokio-runtime-worker(ThreadId(5)) [1P:op-data-layer/src/sync.rs:512] The B5 Notifier for (FTXJSFO4TFAIVNFNGLK6UWNFTQ) has connected, now monitoring for events.

Any ideas where this screen can be coming from and how to get rid of it permanently?

1Password Version: 8.6.1
Extension Version: 2.3.2
OS Version: Ubuntu 20.04

Comments

  • illsorted
    illsorted
    Community Member

    I have this exact same issue. Ubuntu 20.04. 1password 8.6.1.

  • PeterG_1P
    PeterG_1P
    edited April 2022

    Hello @navazo and @illsorted, I'm sorry to learn you've encountered this issue. I'll be happy to follow up on this for you internally.

    In the meantime: are you using any VPNs, proxies, or anything like that which might affect how your 1Password app connects to our servers?

    Thanks, and I'll look forward to helping sort this out 👍

    ref: dev/core/core#14434

  • illsorted
    illsorted
    Community Member

    I use a VPN.

  • Mathieu_1P
    Mathieu_1P

    I'm so sorry you are encountering this frustrating issue.

    This looks exactly like an issue in gnome-shell that has since been resolved. Unfortunately, Ubuntu hasn't yet backported that fix into 20.04. The Ubuntu issue tracker suggests restarting gnome shell via Alt + F2 => r to clear that stray window but that's not ideal if you have open work. It looks like the first release of Ubuntu that has this bug fixed is currently Hirsute (21.04).

    I wish I had a better answer for you, please let me know if something doesn't line up.

    References:

This discussion has been closed.