"Fill Login or show 1Password" sometimes not working in locked state

lumarellumarel
edited February 14 in Windows Beta

Hey all,

The experience got insanely better with the drag and drop function, since it is built in I used it nearly everywhere, instead of copying and pasting. This is so fast in contrast :chuffed:

But sometimes the "Fill Login or show 1Password" function is just even faster.
So it happened since 7.4 more than once that I tried to fill some logins with this while it is in the locked state.
The unlocking window appears, the password is entered but then nothing happens and the function has to be triggered a second time.
At least then it works flawlessly! (also the 1Pmini window does not appear if there are more than one option)

So, have you already encountered this problem?
It also doesn't happen every time (I'm currently in the process of tracking down this in the debug log but wasn't successful up to now), so kind of hard to reproduce...
(Update)
18056 2020-02-14 15:27:49 0.000s INFO opw_app::app:201 > process 13156 starting unlock role
19916 2020-02-14 15:27:57 0.000s INFO opw_app::app:189 > process 13156 starting local sync role for vault 2
19916 2020-02-14 15:27:57 0.185s WRN opw_opvault::backup:201 > backup "2020-02-13-21-09-17.zip" already created within 24 hours for vault id 2
19916 2020-02-14 15:27:57 0.192s INFO opw_opvault::sync:456 > Sync 1, actions: 17, vault: 2, path: %dropboxdir_changed%\1Password\Testvault.opvault, time: 13ms
14772 2020-02-14 15:27:57 0.000s INFO opw_app::app:189 > process 13156 starting local sync role for vault 3
14772 2020-02-14 15:27:57 0.163s WRN opw_opvault::backup:201 > backup "2020-02-13-21-09-16.zip" already created within 24 hours for vault id 3
14772 2020-02-14 15:27:57 0.169s INFO opw_opvault::sync:456 > Sync 1, actions: 300, vault: 3, path: %dropboxdir_changed%\1Password\Work.opvault, time: 81ms
3656 2020-02-14 15:27:57 0.000s INFO opw_app::app:189 > process 13156 starting local sync role for vault 1
3656 2020-02-14 15:27:57 0.176s WRN opw_opvault::backup:201 > backup "2020-02-13-21-09-17.zip" already created within 24 hours for vault id 1
3656 2020-02-14 15:27:57 0.183s INFO opw_opvault::sync:456 > Sync 1, actions: 556, vault: 1, path: %dropboxdir_changed%\1Password\1Password.opvault, time: 208ms
13156 2020-02-14 15:27:49 1149.981s INFO opw_app::roles::main:471 > Unlock: No new updater file found for Beta channel
13156 2020-02-14 15:27:56 1151.298s INFO opw_app::roles::main::unlock:72 > app unlocked with master password
13156 2020-02-14 15:27:56 1158.737s INFO opw_network::proxy_util:29 > loaded AutoDetect proxy - address: false, username: false, password: false
13156 2020-02-14 15:27:56 1158.754s INFO opw_app::watchtower::compromised_sites:33 > loaded 4886 compromised websites in 5ms
13156 2020-02-14 15:27:56 1158.762s INFO opw_app::watchtower::mfa_sites:34 > loaded 585 websites with MFA in 0ms
13156 2020-02-14 15:27:56 1158.766s INFO opw_app::roles::main:471 > Unlock: No new updater file found for Beta channel
13156 2020-02-14 15:27:56 1158.769s INFO opw_network::proxy_util:95 > network connection test successful
13156 2020-02-14 15:27:56 1158.922s INFO opw_network::proxy_config:101 > AutoDetect network proxy detection enabled
13156 2020-02-14 15:27:56 1158.923s INFO opw_app::managers::local_sync_manager:223 > starting sync for local vault 3
13156 2020-02-14 15:27:57 1159.000s INFO opw_app::managers::local_sync_manager:223 > starting sync for local vault 2
13156 2020-02-14 15:27:57 1159.000s INFO opw_app::api:704 > FillKey is used to fill in firefox browser.
13156 2020-02-14 15:27:57 1159.001s INFO opw_app::managers::local_sync_manager:223 > starting sync for local vault 1
13156 2020-02-14 15:27:57 1159.001s INFO opw_app::managers::local_sync_manager:245 > local vault 2 synced in 449ms
13156 2020-02-14 15:27:57 1159.450s INFO opw_app::managers::local_sync_manager:245 > local vault 3 synced in 532ms
13156 2020-02-14 15:27:57 1159.533s INFO opw_app::managers::local_sync_manager:245 > local vault 1 synced in 676ms
As you can see nothing really shows that the fill wasn't successful, this is the whole log from the unlock and fill process :unamused:

~lumarel


1Password Version: 7.4.741
Extension Version: 4.7.6.1
OS Version: Windows 10 1909 Build 18363.592
Sync Type: Dropbox

Comments

  • MikeTMikeT Agile Samurai

    Team Member

    Hi @lumarel,

    Thanks for reporting this.

    Does it happen more often on sites where you only have one Login item for it, which bypasses the 1Password mini UI and fills directly?

  • Hey @MikeT,

    I used it the most with internal pages, which only have one login item, so yes it happened more on these ones.
    But in testing I could also trigger it, on other pages where I have multiple.
    Maybe it appears at single-item pages as often as on ones with multiple, but I can't really say.

  • MikeTMikeT Agile Samurai

    Team Member

    I haven't seen this yet, it would be helpful if we can narrow it down.

    Which browser are you using?

  • lumarellumarel
    edited February 14

    I'm using Firefox (72.0.2) in that case.
    (Update) Could also trigger it in the new Chromium Edge (Version 80).

    I will also try to find a pattern which brings up this problem.
    But of what I'm completely sure is, my window selection is definitely on the browser window. (it might loose that while filling)

    (Update)
    And it doesn't have anything to do with the first launch of the application, was able to trigger it now more than once in a row (lock 1P, restart browser, trigger fill/unlock/doesn't work, second trigger/works, lock 1P, logout , trigger fill/unlock/doesn't work, and so on)

    Maybe its again because of my ...not so small local Vaults :unamused:

  • MikeTMikeT Agile Samurai

    Team Member

    Hi @lumarel,

    But of what I'm completely sure is, my window selection is definitely on the browser window

    For direct filling, that is expected. We only take the focus away when 1Password mini is finished rendering first.

    Maybe its again because of my ...not so small local Vaults

    That doesn't explain why it doesn't show up at all, your log shows all three vaults were done syncing in less than a second. Even if it was due to sync, which is not likely since we've moved it out into its own separate process, the 1Password mini should still show up and/or fill after a second that it took to finish the sync.

    I think this may be a new ultra-rare race condition issue that we're tracking down that is causing 1Password to freeze for a while, it was introduced in 1Password 7.4.741 beta. We're still investigating it and hope to have a new beta update soon with a fix.

    Can you recall if it has happened before the 741 update?

  • Hey @MikeT,

    I think this may be a new ultra-rare race condition issue that we're tracking down that is causing 1Password to freeze for a while, it was introduced in 1Password 7.4.741 beta. We're still investigating it and hope to have a new beta update soon with a fix.

    Okay that sounds promising, let's see if it gets better. :+1:

    I actually created this discussion right after the upgrade to 741, so yes this was already happening in 740, I'm not sure about 738 though.

  • MikeTMikeT Agile Samurai

    Team Member

    Okay, thanks for the details. We believe it was made more visible due to a change we made in 741 but the bug is in there since 738.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file