Sometimes when logging in I get a white screen and have to restart Chrome

jvolk
jvolk
Community Member
edited July 2017 in Browsers (Edge, Chrome, Firefox, etc.)

I this happening for anyone else? I am running Ubuntu 16.04 with the latest version of Chrome. The white screen is where the normal 1Password prompt appears.

If I close and restart Chrome, I can login again and all goes well (until the next time).

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • beyer
    beyer
    1Password Alumni

    Hey @jvolk,

    Unfortunately, this is a confirmed bug which multiple users are experiencing (including myself). However, we have a good idea on what's causing it, so we will hopefully have this resolved sooner than later.

    Until we get this fixed in a future release, you can reset 1Password for Chrome (without relaunching Chrome) by disabling and re-enabling 1Password in Window > Extensions.

    Sorry for the temporary inconvenience, and thanks for taking the time to let us know you're experiencing this issue also. Have a great weekend! :)

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • jvolk
    jvolk
    Community Member

    Thanks for the quick reply

  • beyer
    beyer
    1Password Alumni

    @jvolk: Absolutely! Thank you for using 1Password! <3 :)

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • canstudios_simon
    canstudios_simon
    Community Member
    edited July 2017

    I've just had this for the first time too.
    Not sure if it helps but digging in Extensions -> 1Password... -> Inspect views: 'background page' (with Developer mode enabled) shows the following error:

    background.js:1 Failed to load cached item overviews for secondary accounts. TypeError: Cannot read property 'vaults' of null
    at Promise (background.js:1)
    at Promise ()
    at a.loadAllItemOverviews (background.js:1)
    at Object.l [as loadPopupCache] (background.js:1)
    at e.tabs.performOnActiveTab.t (popup/popup.js:1)
    at Object.chrome.tabs.query.t [as callback] (background.js:1)
    at safeCallbackApply (extensions::uncaught_exception_handler:27)
    at handleResponse (extensions::sendRequest:67)

  • beyer
    beyer
    1Password Alumni

    @canstudios_simon: Sorry about that. We haven't fixed this issue yet, but we do know the cause and it's at the top of our to-do list now that we've reworked adding accounts.

    Thanks for your patience and helping us test 1Password for Chrome. :)

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • canstudios_simon
    canstudios_simon
    Community Member

    No worries, I just disabled and re-enabled the extension as described and was back in business :)

  • beyer
    beyer
    1Password Alumni

    Great, I'm glad that worked for you! :+1: :)

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • dteare
    dteare

    I'm pretty sure I just fixed this on my machine. Assuming there is only one cause, I'm pretty confident I solved the crash shown in @canstudios_simon's stack trace above.

    My changes will be in version 0.8.1 which I hope to release before Monday. Once it's available, please let me know if you see this issue again.

    Thanks again for reporting this! <3

This discussion has been closed.