Chrome extension after standby sometimes not recognized.

Sharpner
Sharpner
Community Member
edited April 2015 in Mac

Heya,

I did not find an issue tracker for 1password so I thought I'll ask here:

When I send my mac to standby with /System/Library/CoreServices/Menu\ Extras/User.menu/Contents/Resources/CGSession -suspend
it sometimes happens (maybe about 1/3 times) that after I resume, and chrome is still open, that 1password shows me to install the chrome extension.

After I completely close chrome, and restart it, the extension is recognized again.

Any workaround?

Thanks in advance.

Comments

  • sjk
    sjk
    1Password Alumni

    Hi @Sharpner,

    The issue tracker for 1Password is only internal but we do publish extensive Release Notes. You've come to the right place to ask about this. :)

    So far I haven't been able to reproduce what you've reported. After resuming your login session, what are steps you do before the message sometimes appears? Is it this Add Chrome Extension… one in 1Password mini (used by the extension) that you're seeing?

    Can you also make it happen if you enable the fast user switching menu (Apple article), select Login Window… from that menu, then later resume your login session? And does the message go away if you wait longer instead of restarting Chrome right away?

    Thanks in advance for the answers to help you get this resolved!

  • Sharpner
    Sharpner
    Community Member

    Hi @sjk, thanks for you response.

    Sorry it took me awhile, but now here we go:

    After the resume I need to login, and then when I go to a website I press cmd + # so that 1password mini opens.
    And yeah, that's when I see the screenshot you provided.

    I yet need to try the normal fast user switch. Will report after I used it for a week or so.
    Thanks for the help ! =)

  • Sharpner
    Sharpner
    Community Member
    edited April 2015

    Maybe one additional note:

    It happens mostly after a the laptop slept for a while. It happens almost every time after lunch... really strange.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Sharpner,

    The kicker with this type of thing is trying to reproduce it given time seems to be a factor. It makes it the sort of thing that is probably aggravating for you and a swine for us to reliably replicate. It could take us a while (sorry).

    There are a couple of things worth trying though.

    The easiest would be in 1Password for Mac to use the following drop down menu option, Help > Troubleshooting > Restart 1Password mini.

    Does that help at all?

    The next would be to see if disabling the 1Password Chrome Extension and then re-enabling resets the lost connection. You can do this by going to Window > Extensions in Google Chrome and un-ticking the Enabled checkbox against the 1Password Extension and then ticking it again.

    Does that make a difference?

    Obviously both are intended as workarounds while we try and figure out why this is happening. The advantage I see either of these having is neither requires closing down all of your Chrome windows and losing whatever tabs you have open.

    Please do let us know if either help :smile:

  • Sharpner
    Sharpner
    Community Member

    hey @littlebobbytables !

    yeah I do understand that this bug is absolutely hard to reproduce. It's even hard to report since I have actually no idea which information of my system might be relevant e.g. encrypted filesystem.

    Is there maybe a "dev" mode for 1password which introduces logging?

    Otherwise I got no clue how to ever find a reproducable scenario.

    Will keep trying though!

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @Sharpner,

    We do have the ability to create a diagnostic report but I'm not sure it will supply anything useful given the error seems to be about the extension reconnecting with 1Password mini. My gut feeling is because we don't have an extension log we might not be able to discern anything.

    Of course we can always look and see. My recommendation would be to wait for the issue to happen again and just for good measure try my two suggestions. After that I would like you to create the following Diagnostic Report.

    Then attach everything to an email to us: support+ forum@agilebits.com

    Please do not post your Diagnostics Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report in our inbox.

    Once you've sent the Report a post here with the ticket ID will help us to keep an eye out for it. :)

This discussion has been closed.