This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Chrome extension ceases
I apologise in advance if this topic will seem a little vague, but I can't reproduce this issue at will.
I leave my PC on 24/7 with Chrome open, and maybe about once or twice a week, 1Password will stop responding in Chrome. When this happens, pressing CTRL+\ does nothing, and clicking the icon fails to bring up anything.
I have to close Chrome and start it again for the extension to become operable.
Unfortunately, I haven't noticed any pattern to the issue occurring. It just happened to me today, so I've just restarted Chrome now. When it happens next time, I'll try to remember to update this forum thread.
I leave my PC on 24/7 with Chrome open, and maybe about once or twice a week, 1Password will stop responding in Chrome. When this happens, pressing CTRL+\ does nothing, and clicking the icon fails to bring up anything.
I have to close Chrome and start it again for the extension to become operable.
Unfortunately, I haven't noticed any pattern to the issue occurring. It just happened to me today, so I've just restarted Chrome now. When it happens next time, I'll try to remember to update this forum thread.
Flag
0
Comments
-
I have noticed this issue occasionally as well, however it seems to have stopped once I switched back to Chrome Stable (I was on Dev before, which 1Password doesn't officially support). Note, I did a total uninstall of Chrome and reinstalled with a clean profile etc.
When the problem occurred, I could fix it by going to Chrome->Tools->Extensions and clicking Reload for the 1Password extension. This would fix the issue and keep me from needing to close and re-open Chrome.Flag 0 -
[quote name='DBrown' timestamp='1307291914' post='28533']
Thanks for the follow-up, Lightwave!
I hope that additional information will help us track down the problem.
[/quote]
I haven't restarted Chrome or reloaded the plugin, in case there's anything else you want me to do or check that might also help. Let me know.Flag 0 -
[quote name='Lightwave' timestamp='1307907026' post='29059']
I've now upgraded to Chrome 12 this morning (restart required) so I'll post again with an update if this issue persists in the new browser, unless you let me know otherwise.
[/quote]
Thanks for the update, Lightwave, please do let us know how things go with Chrome 12 and 1Password for Windows, we'll do our best to help if any issues crop up.Flag 0 -
[quote name='stu' timestamp='1308178742' post='29276']
Thanks for the update, Lightwave, please do let us know how things go with Chrome 12 and 1Password for Windows, we'll do our best to help if any issues crop up.
[/quote]
The plugin has stopped working again. 5 days roughly. Again, I'll leave Chrome as it is for now in case you want me to do or check anything and report back. Let me know!Flag 0 -
Hi Lightwave,
Could you try the latest Beta of 1Password for Windows by going to Preferences > Updates from within 1Password itself and checking the 'Include Beta Versions' option and then clicking 'Check Now' to get our latest Beta which should resolve the issue with Chrome.
Please let me know how it turns out,
[quote name='Lightwave' timestamp='1308308237' post='29399']
The plugin has stopped working again. 5 days roughly. Again, I'll leave Chrome as it is for now in case you want me to do or check anything and report back. Let me know!
[/quote]Flag 0 -
[quote name='stu' timestamp='1308416170' post='29477']
Hi Lightwave,
Could you try the latest Beta of 1Password for Windows by going to Preferences > Updates from within 1Password itself and checking the 'Include Beta Versions' option and then clicking 'Check Now' to get our latest Beta which should resolve the issue with Chrome.
Please let me know how it turns out,
[/quote]
Hi Stu, I am having this issue too. It seems to have started when Chrome went to v12 stable. I am running Chrome beta, which 1Password lists as supported and the Chrome extension is very flaky and won't work most of the time. I can always try going to Chrome stable, but haven't had this issue before with Chrome beta and 1Password. I am running the latest 1Password beta for Windows. Every time I open preferences, Chrome is unticked under browsers. If I tick it, it works once and then stops working. I open 1Password again and, surprise, it's unticked again.
Regards,
CurbedFlag 0 -
[quote name='stu' timestamp='1308416170' post='29477']
Hi Lightwave,
Could you try the latest Beta of 1Password for Windows by going to Preferences > Updates from within 1Password itself and checking the 'Include Beta Versions' option and then clicking 'Check Now' to get our latest Beta which should resolve the issue with Chrome.
Please let me know how it turns out,
[/quote]
I'll try upgrading 1Password for Windows to the latest beta and give Chrome a restart and try again... I'll do that now, so we'll see how it goes. Thanks for the suggestion, Stu. Will post with an update perhaps in a week-or-so, pending no reboots or browser restarts.
[quote name='CurbedEnthusiasm' timestamp='1308577294' post='29627']
Hi Stu, I am having this issue too. It seems to have started when Chrome went to v12 stable. I am running Chrome beta, which 1Password lists as supported and the Chrome extension is very flaky and won't work most of the time. I can always try going to Chrome stable, but haven't had this issue before with Chrome beta and 1Password. I am running the latest 1Password beta for Windows. Every time I open preferences, Chrome is unticked under browsers. If I tick it, it works once and then stops working. I open 1Password again and, surprise, it's unticked again.
Regards,
Curbed
[/quote]
Sounds like a slightly different issue to me. My 1Password and Chrome (neither are beta so far) are quite stable, until Chrome has been open for about 60 hours, and the 1Password plugin becomes unresponsive. Pressing CTRL+\ or clicking the 1Password browser plugin icon both do nothing until I restart the plugin or the browser.Flag 0 -
[quote name='Lightwave' timestamp='1308671445' post='29763']
I'll try upgrading 1Password for Windows to the latest beta and give Chrome a restart and try again... I'll do that now, so we'll see how it goes. Thanks for the suggestion, Stu. Will post with an update perhaps in a week-or-so, pending no reboots or browser restarts.
Sounds like a slightly different issue to me. My 1Password and Chrome (neither are beta so far) are quite stable, until Chrome has been open for about 60 hours, and the 1Password plugin becomes unresponsive. Pressing CTRL+\ or clicking the 1Password browser plugin icon both do nothing until I restart the plugin or the browser.
[/quote]
Actually that does sound different. I noticed an update for 1P today in relation to Chrome 13, so hope that fixes both issues.Flag 0 -
[url="http://aws.cachefly.....6.BETA-199.exe/"]1P4Windows BETA-199[/url]Flag 0
-
Ok, I was on 1.0.5.190 and I've just this minute upgraded to 1.0.6.BETA-199 and restarted Chrome.
This license apparently runs out in 8 days, so hopefully we'll see if the plugin fails by then or not. Under normal circumstances I would expect it to do so within 8 days.
I guess I'll keep you posted!
My Chrome version, for reference, is: 12.0.742.100Flag 0 -
Thanks for the update!
I look forward to hearing how it works for you.Flag 0 -
[quote name='DBrown' timestamp='1308847987' post='30154']
On the Updates tab of 1Password preferences, enable the [b]Include Beta versions[/b] option, and click the [b]Check Now[/b] button.
[/quote]
Thanks David. Well, it's past 10pm and my beta runs out today. No Chrome restarts since my last post, and 1Password is still up and performing. I'm afraid it's time to cut this stage of the experiment short as I need to upgrade to the new beta, but I'll get Chrome going again, and we'll take now as the new starting point.
So far so good though. [img]http://forum.agile.ws/public/style_emoticons/default/smile.gif[/img]
(Just upgrading to 1.0.7.BETA-203)Flag 0 -
I've gone back from the beta to the latest full release (v 1.0.7.211) and the issue is back. I guess whatever fixed it isn't in the full release yet. It also doesn't seem to take nearly as long for the extension to stop working now - maybe 24-48 hours.
I'm just resetting my extension as I post this, so if it happens again I guess I'll update here to let you know how long it's been.Flag 0 -
I'm confused, Lightwave—why would you be running such an old version of 1Password? The current version is 1.0.8.215, which is not a Beta build.
Please make sure you're using the latest version of 1Password at all times by following the instructions in [url="http://help.agilebits.com/1Password_Windows/software-updates.html"][i]Keeping 1Password up to date[/i][/url] in the [i]FAQ[/i] section of the user's guide.
(I'd recommend enabling the [b]Include Beta versions[/b] option, too, but that's up to you. If you try a Beta build and decide to go back to non-Beta, for some reason, you can download any version from the site linked in the "[url="http://forum.agilebits.com/index.php?/topic/102-link-to-1password-for-windows-and-the-change-log-history/"]Link to 1Password for Windows and the Change Log History[/url]" topic pinned at the top of this forum.)
Also, please make sure you're also using the current non-Beta version of Chrome (13.x, as I write this).
Then let us know if you still see the problem.Flag 0 -
Yes, that's weird. It's set to automatically check for updates weekly and says the last check was 22 August.
Have I found another problem with 1Password? When does a "check for updates" get triggered? I've had 1Password open without closing it for... more than a week.
Anyway, yes, I'll manually check for updates and try the latest version. Thanks Dave. I wondered why there was still no Firefox 6 compatibility!Flag 0 -
Well, that's the problem, lightwave.
You have to launch 1Password to get it to check whether it's time (based on your selected frequency preference) to check for a new version.
I wish that were not so. I filed an enhancement request months ago on behalf of 1Password users like me who leave it running for extended periods.
I hope we'll see that change in a future version of 1Password...but we'll have to exit and relaunch it every now and then to see that a new version is available. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/wink.png' class='bbc_emoticon' alt=';)' />Flag 0 -
[quote name='DBrown' timestamp='1314894341' post='43814']I hope we'll see that change in a future version of 1Password...but we'll have to exit and relaunch it every now and then to see that a new version is available. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/wink.png' class='bbc_emoticon' alt=';)' />
[/quote]
Gotcha! For now, anyway, I'm up-to-date and running again, to test if this Chrome extension ceases. I'll keep you posted.Flag 0 -
[quote name='DBrown' timestamp='1314894341' post='43814']
You have to launch 1Password to get it to check whether it's time (based on your selected frequency preference) to check for a new version.
[/quote]
This is how most software is doing it (including our Mac version)
[quote name='DBrown' timestamp='1314894341' post='43814']
I hope we'll see that change in a future version of 1Password...but we'll have to exit and relaunch it every now and then to see that a new version is available.
[/quote]
There is always this: [i]Help > Check for New Version[/i]Flag 0
![[Deleted User]](https://wd.vanillicon.com/v2/d67898e43981d615d2bad887d3056ef6.svg)
![[Deleted User]](https://w3.vanillicon.com/v2/347e7921d8fe973d8142aaba842f1419.svg)
