I *was* having the same problem here in Jaunty. This should be a bug, and should be fixed. It was not a mime-type issue for me (though I saw the same /symptoms/ as others report).
Copying the public key line out of authorized_keys2 and creating id_dsa.pub, then running seahorse, there was not even a need to import the key! It just magically shows up in the list (though it's not 'unlocked', mind you, as you have not been challenged yet). And - of course - now when I try 'ssh other-host', /usr/bin/gnome- keyring-daemon prompts in X with the system modal window, as it should, instead of the text prompt (which does not store it in the agent....meaning every 'ssh' command from a different pty requires the password again). It was hard to understand as strace of 'ssh' looked the same except for text prompt vs X11 prompt........turns out now that seahorse would not load the contents of the private key file unless the pub key was on disk. Note that I did not strace the daemon, just the ssh command. I'm glad to have found a workaround, but this should be fixed - at least give the message that the pub key file is not found, so everyone else can have an AH-HA moment rather than seeming to not support DSA keys :-) -- import failure: Invalid file format https://bugs.launchpad.net/bugs/372608 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
