Cannot save password of favorite connection in keychain

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Write or paste a password into the SSH / MySQL password field
2. Unfocus field

What is the expected output? What do you see instead?

Error screenshot attached

What version of Sequel Pro are you using? 0.9.9 build 3348
What version of MySQL are you connecting to on the server? 5.1.41

Please provide any additional information below.

It happens either in the "quick connection" and in favorite preferences.
Worked good with previous release.
My keychain has a different password than my account's. I can still use 
favorites, they ask me (as before) for keychain password and connect 
successfully.

Original issue reported on code.google.com by ekino...@gmail.com on 4 Jul 2011 at 11:11

Attachments:

• error.tiff

[GoogleCodeExporter]

That error code is an odd one, and normally one we see when the application 
can't authorise enough against the keychain to be able to talk to it.  You 
could try the following three fixes:

1) Quit and open Sequel Pro a couple of times.  This sometimes seems to be 
enough for the keychain to allow it!

2) In the Keychain Access window, there's a lock at the top left.  Click on it 
once to lock the keychain, then again to unlock the keychain.  You'll be asked 
for your password - this seems to resolve permission errors.

3) Open up Keychain Access.app (in /Applications/Utilities), then go to the 
"Keychain Access" menu and choose "Keychain First Aid".  Type in your password, 
and try a verify/repair.

Hopefully that'll kick it into action...

Original comment by rowanb@gmail.com on 4 Jul 2011 at 11:38

[GoogleCodeExporter]

I've tried steps 2 and 3 before posting the issue but didn't think of simply 
restart the app. This resolved my issue... Thanks !

Original comment by ekino...@gmail.com on 4 Jul 2011 at 11:49

[GoogleCodeExporter]

Heh.  Thanks for the update.

We've only seen one report of this before (I think) and it seems to be related 
to updating the app - it probably won't happen again for you.  Intermittent 
issues, always the best!

I'll mark this as "WontFix" for now as I don't think there's anything we can do 
from our side (other than perhaps updating the error message)

Original comment by rowanb@gmail.com on 4 Jul 2011 at 12:08

• Changed state: WontFix