Keyboard shortcut not working [FIXED]

Using the latest beta 3.7.1 beta 1 and the latest extension in safari under Lion and just lost the keyboard shortcut doesn't work. I checked under Keyboard preferences that there isn't a conflict with command-slash. Something's wrong, can't figure out what...help!
«1

Comments

  • mattl wrote:

    Using the latest beta 3.7.1 beta 1 and the latest extension in safari under Lion and just lost the keyboard shortcut doesn't work. I checked under Keyboard preferences that there isn't a conflict with command-slash. Something's wrong, can't figure out what...help!
    Hi Matti,


    I’m sorry about this, many of our users confirmed that if you restart Safari without saving its state on Lion, it’ll fix the issue. Please open Safari, press “Command + Option + Q” to close it without a saved state and then open Safari again, this should fix the keyboard shortcut.

    If not, it is possible that the extension hasn’t been updated in Safari. Please follow the instruction here to update it.

    I hope that helps, please let me know.
  • I'm running the latest beta version of the app (3.7.1.BETA-1) and extension (3.7.b4), and at first I thought the main cmd-\ shortcut wasn't working at all on websites where I had a password stored. I would hit it and nothing would happen. Then I realised that if I hit it twice, it autofills in the expected way. Which seems odd.

    Incidentally I was also unable to use auto-unlock but I realised it was a conflict with Glims, but when I uninstalled and reinstalled Glims it solved that problem.
  • mattl
    mattl
    Community Member
    edited August 2011
    MikeT wrote:

    Hi Matti,


    I’m sorry about this, many of our users confirmed that if you restart Safari without saving its state on Lion, it’ll fix the issue. Please open Safari, press “Command + Option + Q” to close it without a saved state and then open Safari again, this should fix the keyboard shortcut.

    If not, it is possible that the extension hasn’t been updated in Safari. Please follow the instruction here to update it.

    I hope that helps, please let me know.


    Did those things, just updated the 1P application and the extension. Now have extension 3.7b7. Closed Safari without a saved state, still no shortcut. Appreciate any other ideas, will keep updating extension regularly.
  • khad
    khad
    1Password Alumni
    What happens if you change the keyboard shortcut to another key combination in 1Password' preferences? Is the problem with ⌘\ specifically or all keyboard shortcuts? Does ⌥⌘\ open the All Logins section in the browser?

    Could you please try the new Beta release (3.7.1.BETA-2) and see if it fixes this problem? You can do this by going to the 1Password > Preferences window, selecting the Update panel, enable the "Include Beta versions" checkbox, and then click Check Now. Once the update is installed, try again and see if it helps.
  • dweeks
    dweeks
    Community Member
    edited August 2011
    I have problems, too.

    Safari 5.1,the latest 1Password beta 3.71 beta 2, and the latest Safari extension.

    I can't even get Command \ to invoke the logins window. Nothing happens. Same in Firefox 5.
  • mattl
    mattl
    Community Member
    khad wrote:

    What happens if you change the keyboard shortcut to another key combination in 1Password' preferences? Is the problem with ⌘\ specifically or all keyboard shortcuts? Does ⌥⌘\ open the All Logins section in the browser?

    Could you please try the new Beta release (3.7.1.BETA-2) and see if it fixes this problem? You can do this by going to the 1Password > Preferences window, selecting the Update panel, enable the "Include Beta versions" checkbox, and then click Check Now. Once the update is installed, try again and see if it helps.


    I'm using the latest beta, should have posted this in the beta section, perhaps. Also latest extension. I tried to change the shortcuts, but that didn't help. ⌥⌘\ doesn't work either.
  • A User
    edited August 2011
    I had the same problem (even after changing to a new shortcut, uninstalling the extension, etc). Here is how I fixed it.

    [Instruction removed as it was a dangerous procedure and Agilebits do not recommend doing this -MikeT]

    I probably did a bunch of too many things there in an effort to be sure to delete the culprit file, but since simply uninstalling the extension didn't work I figured I would go into the Library folder and delete some stuff :) Looks like it worked.


    A quick note: In Lion, the Library folder is now hidden by default. To unhide it, open Terminal and type
    chflags nohidden ~/Library
    
    .
  • paul7
    paul7
    Community Member
    I was having the same problem running 10.6.8, Safari 5.1, and 1Password extension 3.7.b2. What fixed it was to quit and re-start Safari. Maybe there should be some warning to tell you to quit and restart Safari after installing the extension.
  • mattl
    mattl
    Community Member
    stu wrote:

    Thanks for posting this, it's very strange that you had to go through all of this, as you said just removing the extension and then reinstalling it should just do the trick.

    That said, I think the key step is the one you pointed out here:



    The precise path the extensions should be located in is:

    ~/Library/Safari/Extensions
    


    Make sure Safari is not running at this point, just to be on the safe side. The easiest way to then reinstall the extension is to click the following link to download the extension, then double-click it to install:

    http://cdn.agilebits.com/dist/1P/ext/1PasswordBeta.safariextz



    Another option, which doesn't involve the Terminal, is to go to the 'Go' menu from a Finder window and hold down the Option ⌥ key to reveal 'Library' as one of the choices you can navigate to.

    Matti, could you try the above to see if this does the trick for you?


    Deleting the extension from ~/Library/Safari/Extensions then reinstalling it, then command-option-quitting Safari worked on the MB Air. Will try it on the home iMac to see if that works later tonight.

    Thanks for the help.
  • mattl
    mattl
    Community Member
    stu wrote:

    Thanks for the update, mattl, glad to hear that worked for the MacBook Air (I really need to get one) do keep us posted about how things turn out on the iMac.


    The simple approach that worked on the Air did not work on the iMac. The more thorough approach described by A User did not work either. Still stuck on the iMac. Using the b8 extension now.

    Any further advice appreciated.
  • mattl wrote:

    The simple approach that worked on the Air did not work on the iMac. The more thorough approach described by A User did not work either. Still stuck on the iMac. Using the b8 extension now.

    Any further advice appreciated.


    Please open Console.app and then restart Safari. Do you see any new messages in the "All Messages" or in ~/Library/Logs/1Password/1PasswordAgent.log?
  • mattl
    mattl
    Community Member
    edited August 2011
    roustem wrote:

    Please open Console.app and then restart Safari. Do you see any new messages in the "All Messages" or in ~/Library/Logs/1Password/1PasswordAgent.log?


    just updated to final 3.7.1 and extension 3.7b9. did the option command quit of Safari after replacing the latest extension after trashing the old one. Still doesn't work.

    Console.app output in all messages:


    8/1/11 8:45:52.169 PM Safari: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    8/1/11 8:45:52.169 PM Safari: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    8/1/11 8:45:52.170 PM Safari: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

    in 1PasswordAgent.log:

    [31089] Mon Aug 1 20:45:55 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 20:45:55 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'

    Not much there, but maybe this gives you a clue...
  • Thanks!

    You should see something like this:


    [31089] Mon Aug  1 23:52:23 2011| [SES] Using extension database: '/Users/roustem/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000a.db'
    [31089] Mon Aug  1 23:52:23 2011| [SES] 1Password locked
    [31089] Mon Aug  1 23:52:23 2011| [AES] Starting server on port 6258
    [31089] Mon Aug  1 23:52:23 2011| [AES] didAddClient
    [31089] Mon Aug  1 23:52:23 2011| [AES] Adding client [3A20608D-1348-4568-A4D3-4650EA2D9386]: com.apple.Safari
    [31089] Mon Aug  1 23:52:26 2011| [SES] Using extension database: '/Users/roustem/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000a.db'
    


    Most importantly — a message about starting the server and another message about adding Safari as a client.
  • mattl
    mattl
    Community Member
    roustem wrote:

    Thanks!

    You should see something like this:


    [31089] Mon Aug  1 23:52:23 2011| [SES] Using extension database: '/Users/roustem/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000a.db'
    [31089] Mon Aug  1 23:52:23 2011| [SES] 1Password locked
    [31089] Mon Aug  1 23:52:23 2011| [AES] Starting server on port 6258
    [31089] Mon Aug  1 23:52:23 2011| [AES] didAddClient
    [31089] Mon Aug  1 23:52:23 2011| [AES] Adding client [3A20608D-1348-4568-A4D3-4650EA2D9386]: com.apple.Safari
    [31089] Mon Aug  1 23:52:26 2011| [SES] Using extension database: '/Users/roustem/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000a.db'
    


    Most importantly — a message about starting the server and another message about adding Safari as a client.


    I logged out then back in to my user account, opened Safari

    in 1PasswordAgent.log

    [31089] Mon Aug 1 20:59:27 2011| == Opening log session ==
    [31089] Mon Aug 1 20:59:27 2011| Starting 1PasswordAgent 3.7.1 #31089 built Aug 1 2011 22:39:46
    [31089] Mon Aug 1 20:59:27 2011| Trying to load Localizable.strings [English] from the main bundle
    [31089] Mon Aug 1 20:59:27 2011| Cannot find English version, using English localization for Localizable.strings
    [31089] Mon Aug 1 20:59:31 2011| Initializing AGHtmlDatabase object with path 'file://localhost/Users/matt/Dropbox/1Password.agilekeychain/'.
    [31089] Mon Aug 1 20:59:31 2011| watchProfile
    [31089] Mon Aug 1 20:59:31 2011| reloadAllObjects
    [31089] Mon Aug 1 20:59:31 2011| Database (AGHtmlDatabase:file://localhost/Users/matt/Dropbox/1Password.agilekeychain/) load time [Cache]: 0.216+0.003 (933 objects)
    [31089] Mon Aug 1 20:59:31 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 20:59:31 2011| [SES] 1Password locked
    [31089] Mon Aug 1 20:59:31 2011| [AES] Starting server on port 10191
    [31089] Mon Aug 1 20:59:34 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 20:59:34 2011| [SES] 1Password locked
    [31089] Mon Aug 1 21:02:18 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 21:02:18 2011| [SES] 1Password locked


    In All Messages, same message as in my previous post.
  • I wonder what prevents Safari from connecting to 1PasswordAgent -- there are no connection messages in the logs.

    Please try to open Activity Monitor application and search for 1PasswordAgent:

    20110802-emwupwm1kjxeyp1bycgjjggw24.png

    Select 1PasswordAgent and the click "Quit Process". 1PasswordAgent will restart in a few seconds.

    After that, restart Safari and see if there are any connection messages in the log.

    Thank you!
  • mattl
    mattl
    Community Member
    roustem wrote:

    I wonder what prevents Safari from connecting to 1PasswordAgent -- there are no connection messages in the logs.

    Please try to open Activity Monitor application and search for 1PasswordAgent:

    20110802-emwupwm1kjxeyp1bycgjjggw24.png

    Select 1PasswordAgent and the click "Quit Process". 1PasswordAgent will restart in a few seconds.

    After that, restart Safari and see if there are any connection messages in the log.

    Thank you!


    Here's a clue:
    [31089] Mon Aug 1 21:18:01 2011| == Opening log session ==
    [31089] Mon Aug 1 21:18:01 2011| Starting 1PasswordAgent 3.7.1 #31089 built Aug 1 2011 22:39:46
    [31089] Mon Aug 1 21:18:01 2011| Trying to load Localizable.strings [English] from the main bundle
    [31089] Mon Aug 1 21:18:01 2011| Cannot find English version, using English localization for Localizable.strings
    [31089] Mon Aug 1 21:18:01 2011| Initializing AGHtmlDatabase object with path 'file://localhost/Users/matt/Dropbox/1Password.agilekeychain/'.
    [31089] Mon Aug 1 21:18:01 2011| watchProfile
    [31089] Mon Aug 1 21:18:01 2011| reloadAllObjects
    [31089] Mon Aug 1 21:18:01 2011| Database (AGHtmlDatabase:file://localhost/Users/matt/Dropbox/1Password.agilekeychain/) load time [Cache]: 0.059+0.003 (933 objects)
    [31089] Mon Aug 1 21:18:01 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 21:18:01 2011| [SES] 1Password locked
    [31089] Mon Aug 1 21:18:01 2011| [AES] Starting server on port 10191
    [31089] Mon Aug 1 21:18:04 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 21:18:07 2011| [AES] didAddClient
    [31089] Mon Aug 1 21:18:07 2011| Crypto operation failed: -4301
    [31089] Mon Aug 1 21:18:07 2011| [AES] Invalid socket data. Ignoring
    [31089] Mon Aug 1 21:18:49 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'
    [31089] Mon Aug 1 21:18:49 2011| [SES] Using extension database: '/Users/matt/Library/Safari/Databases/safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0/000000000000000d.db'

    Looks like a problem after the didAddClient.
  • mattl wrote:

    [31089] Mon Aug 1 21:18:07 2011| [AES] didAddClient
    [31089] Mon Aug 1 21:18:07 2011| Crypto operation failed: -4301
    [31089] Mon Aug 1 21:18:07 2011| [AES] Invalid socket data. Ignoring


    Ah, so the plot thickens! Thank you so much for posting this, it is very useful.

    I have a hunch about what has happened. Could you please run this command from Terminal and post the results?

    sqlite3 -line ~/Library/Safari/Databases/Databases.db "select * from Databases where name = 'OnePassword';"
    


    Thank you!
  • mattl
    mattl
    Community Member
    dteare wrote:

    Ah, so the plot thickens! Thank you so much for posting this, it is very useful.

    I have a hunch about what has happened. Could you please run this command from Terminal and post the results?

    sqlite3 -line ~/Library/Safari/Databases/Databases.db "select * from Databases where name = 'OnePassword';"
    


    Thank you!



    guid = 13
    origin = safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0
    name = OnePassword
    displayName = 1Password Database
    estimatedSize = 104857600
    path = 000000000000000d.db


    Hope this helps
  • mattl wrote:

    Hope this helps


    Thanks for the quick reply. This info does indeed help a lot, but it doesn't match my hunch since everything looks perfectly fine.

    It looks like we'll need to add more logging to see what's happening. Please post the updated logs once the new 1Password 3.7.2 beta is released. Likely sometime later today or tomorrow at the latest.
  • Hi Mattl,

    This may not fix it but I’d like you to do the following to at least eliminate it as a possible cause.

    1. Open Safari, go to its Preferences > Extensions
    2. Select 1Password on the left side and press the Uninstall button on the right
    3. Quit Safari with “Command + Option + Q”
    4. Open Finder, go to
      Home > Library > Safari > Databases
      
    5. Confirm for us that you don’t see the following folder:
      safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0
      
    6. If you do, please move this to the desktop
    7. Open 1Password and let it install the Safari 5.1 extension or you can go to the 1Password Menu > Preferences > Browsers to press the “Install Safari extension” button
    8. After Safari finish installing it, wait a few seconds, switch back to 1Password and go to Help > Troubleshooting > Restart Agent
    9. Wait a minute, go back to Safari, quit it with “Command + Option + Q” again and start it up, see if Safari works better now.
  • mattl wrote:

    The simple approach that worked on the Air did not work on the iMac. The more thorough approach described by A User did not work either. Still stuck on the iMac. Using the b8 extension now.


    I just wanted to clarify: you mentioned you are using Lion in the OP, but are both the Air and the iMac running Lion?
  • mattl
    mattl
    Community Member
    dteare wrote:

    I just wanted to clarify: you mentioned you are using Lion in the OP, but are both the Air and the iMac running Lion?


    Yes, running Lion on both. Will look for the next 1P beta and will try the steps above later tonight when I'm back at the home iMac...
  • Hi Harry, welcome to the forums!

    Thanks for letting us know about Glims, we’ll look into that. We just released the update for both the 1Password app and the extension, 3.7.1 and 3.7b9 respectively. Please update both and see if that’ll fix the issue with the keyboard shortcut.

    You do have to unlock the 1Password extension first before the command + \ can respond. We’re looking into fixing this, so that it’d prompt for the password before filling in.

    I hope this helps, please let me know.
  • Sorry, I should have replied to my own post sooner, really; I think one of the updates solved the problem for me. Thanks!

    MikeT wrote:

    Hi Harry, welcome to the forums!

    Thanks for letting us know about Glims, we’ll look into that. We just released the update for both the 1Password app and the extension, 3.7.1 and 3.7b9 respectively. Please update both and see if that’ll fix the issue with the keyboard shortcut.

    You do have to unlock the 1Password extension first before the command + \ can respond. We’re looking into fixing this, so that it’d prompt for the password before filling in.

    I hope this helps, please let me know.
  • MartyS
    MartyS
    Community Member
    mattl wrote:

    Yes, running Lion on both. Will look for the next 1P beta and will try the steps above later tonight when I'm back at the home iMac...


    Thanks for the update! Please let us know what you find out when you have the time.
  • mrtoner
    mrtoner
    Community Member
    edited August 2011
    Using 3.7.1/3.7b9, cmd-\ is unresponsive. Extension seems to work fine otherwise.

    Update: the shortcut is hit-and-miss.
  • mattl
    mattl
    Community Member
    MikeT wrote:

    Hi Mattl,

    This may not fix it but I’d like you to do the following to at least eliminate it as a possible cause.

    1. Open Safari, go to its Preferences > Extensions
    2. Select 1Password on the left side and press the Uninstall button on the right
    3. Quit Safari with “Command + Option + Q”
    4. Open Finder, go to
      Home > Library > Safari > Databases
      
    5. Confirm for us that you don’t see the following folder:
      safari-extension_com.agilebits.onepassword-safari-2bua8c4s2c_0
      
    6. If you do, please move this to the desktop
    7. Open 1Password and let it install the Safari 5.1 extension or you can go to the 1Password Menu > Preferences > Browsers to press the “Install Safari extension” button
    8. After Safari finish installing it, wait a few seconds, switch back to 1Password and go to Help > Troubleshooting > Restart Agent
    9. Wait a minute, go back to Safari, quit it with “Command + Option + Q” again and start it up, see if Safari works better now.



    This did not work.
  • mrtoner wrote:

    Using 3.7.1/3.7b9, cmd- is unresponsive. Extension seems to work fine otherwise.

    Update: the shortcut is hit-and-miss.


    When it doesn't happen, please check you logs to see if you have the same issue as mattl.

    Re: mattl's issue, the changes I needed to make to debug this were bigger than I expected. I'll need a few more days to include it in a new release. Sorry for the delay.
  • mattl
    mattl
    Community Member
    dteare wrote:


    Re: mattl's issue, the changes I needed to make to debug this were bigger than I expected. I'll need a few more days to include it in a new release. Sorry for the delay.


    OK, I have updated to the latest beta and extension. I tried to do the procedure Roustem described that previously showed that Crypto error, but the 1PasswordAgent.log doesn't show anything about the client now or that error. Keyboard shortcut still doesn't' work.

    If there is a different procedure you want me to follow to generate a good log, or if you want the diagnostic report sent in, let me know.

    Not sure it matters, but I have been using 1P for a looooong time on this machine and there are various folders in various places that I think are from older versions. I have not thrown any folders away as I didn't want to remove anything critical and blow up my installation. IF you want me to clear out old garbage and do a fresh install of 1P to clear the decks, I'd be happy to do that. Just let me know what to trash or put outside of key directories to try a fresh install.

    Thanks, Matt
  • bswins
    edited August 2011
    Hey Matt,

    I just wanted to reply to let you know that I passed your message along to Dave. I will let him or another one of our code experts respond with the next requested action.

    In the interim, it will be helpful to know whether you are still experiencing this behavior running our most current releases of 1Password and the Safari extension, which, as of this writing, are 3.7.2 (build 31099) and 3.7.b10, respectively.

    Thank you for your patience and continued efforts to help us troubleshoot this issue. Your input is incredibly valuable, and I am confident that your willingness to help us will eventually help a lot of other users.

    Cheers!

    Brandt
This discussion has been closed.