I've got the same problem on Fedora 21, except the GUI to ask for the password *never* seems to start, so as suggested I'm reopening the bug. +++ This bug was initially created as a clone of Bug #921513 +++ Gnome keyring dialog is not open when I try to connect fedora servers with locked ssh keys. gnome-keyring seems to be up. [komat@dhcp129-206 CVS]$ ps axf | grep gnome-keyring 1617 ? Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 3763 pts/0 S+ 0:00 \_ grep --color=auto gnome-keyring --- Additional comment from Martin Stransky on 2013-03-14 07:03:16 EDT --- [komat@dhcp129-206 CVS]$ ssh -v stransky.org OpenSSH_6.1p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /home/komat/.ssh/config debug1: /home/komat/.ssh/config line 6: Applying options for *.fedoraproject.org debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 50: Applying options for * debug1: Connecting to people.fedoraproject.org [2610:28:3090:3001:5054:ff:fedb:7f5a] port 22. debug1: connect to address 2610:28:3090:3001:5054:ff:fedb:7f5a port 22: Network is unreachable debug1: Connecting to people.fedoraproject.org [152.19.134.191] port 22. debug1: Connection established. debug1: identity file /home/komat/.ssh/id_rsa_fedora type 1 debug1: identity file /home/komat/.ssh/id_rsa_fedora-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 07:d4:02:db:9f:70:d5:2d:7f:1b:6a:df:83:73:95:1d debug1: Host 'people.fedoraproject.org' is known and matches the RSA host key. debug1: Found key in /home/komat/.ssh/known_hosts:45 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/komat/.ssh/id_rsa_fedora debug1: Server accepts key: pkalg ssh-rsa blen 279 Agent admitted failure to sign using the key. debug1: Offering RSA public key: komat.redhat.com debug1: Authentications that can continue: publickey debug1: Offering DSA public key: komat@triglav debug1: Authentications that can continue: publickey debug1: Offering RSA public key: komat@localhost debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). --- Additional comment from Martin Stransky on 2013-03-14 07:07:13 EDT --- It looks like a race condition or so. The gnome-keyring dialog is open after 3-5 attempts. --- Additional comment from Stef Walter on 2013-03-19 17:18:54 EDT --- Are you able to test this patch to see if it fixes the issue: https://git.gnome.org/browse/gcr/commit/?id=f25cc328066e7b6a7f960aea38ab6beb6f967a42 --- Additional comment from Fabrice Bellet on 2013-03-27 18:12:14 EDT --- I also notice the same problem : - the bug occurs for me with gnome3 in fallback mode only. - in fallback mode, the bug is specific to gcr-3.6.2-3.fc18 (downgrading to 3.6.2-1 works) - patch from comment #3 doesn't solve the bug --- Additional comment from Peter Meier on 2013-04-13 11:09:52 EDT --- I can confirm this bug. It also affects gpg keys in thunderbird and so on. Usually trying multiple times allow one to workaround the race condition, but it's quite annoying. I haven't tested if the patch works. --- Additional comment from Thomas Moschny on 2013-05-08 07:53:17 EDT --- Same Problem here With gcr-3.6.2-3.fc18, the key was *never* unlocked, regardless how often I tried. Downgrading to 3.6.2-1.fc18 helps in so far, as with the older version trying multiple times eventually helps. --- Additional comment from Fedora End Of Life on 2013-12-21 07:08:27 EST --- This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Fedora End Of Life on 2014-02-05 14:57:31 EST --- Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Partial workaround found via <https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084>: If I set SSH_AUTH_SOCK=0 then SSH will at least prompt me for the keychain password rather than just failing. But it still uses the terminal to prompt me, the GNOME prompter doesn't work.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.