1Password thinks a keyboard shortcut is not available when it is

harliv

On all of my existing machines which were updated to Lion I am using command-space to autofill password in the web browser. On my new Lion system I get a message that the shortcut is already being used and to go to the keyboard prefs to change it on the Mac. Spotlight is changed to control-space and nothing else is using command-space on this system that I can find.



Any ideas where else I can look? I'm having a hard time getting used to a new key combo after working with this configuration for so long.

Ben

Hi harliv,



Welcome to the forums. Sorry for the delayed reply, honestly I was hoping one of our forum members might have come up with a better answer for you. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/skype_sweating.png' class='bbc_emoticon' alt='(sweat)' />



Unfortunately the only thing I can think of is to use a different keyboard shortcut that doesn't conflict. You've already looked in the only place I can think of for conflicts. I've never had anything but trouble trying to remap cmd+space (I used to try and use it for QuickSilver, but now have switched to opt+space).



Sorry I don't have a better answer for you.

Ben

harliv

I'm going to try moving my user directory and doing a time machine restore of my user account from my laptop where everything is working and see if that gets me around it.



Thanks anyways!



Probably something odd with Lion thinking that shortcuts is still in use when it isn't

Ben

Please let us know how it goes. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

harliv

I finally got around to doing this today. Importing my user from my laptop backup where this was still working did resolve the issue.



I guess something in Lion is saying the keyboard shortcut is still in use when its not so I can't select it but when it is already configured that way it is fine.

Ben

Thanks for the update. Glad you were able to track down the cause of the problem. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />