Red Hat Bugzilla – Bug 843298
Import failed: no user has logged in
Last modified: 2013-08-01 00:13:23 EDT
Seahorse displays the message "Import failed: no user has logged in" when I attempt to import an SSH key, and prompts me to "cancel" or "import". If I select "import" again it prompts me for the label, when I enter the label and hit "ok", the screen disappears and the key is not displayed in seahorse.
Package version 3.4.1-1.fc17
Absolutely reproducable. Only tried with SSH private key. Duplicate of this bug over at Ubuntu's launchpad by the looks of it: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1017210
Adding external tracker.
Created attachment 654312 [details]
sample ssh keypair came from /tmp/id_rsa /tmp/id_rsa.pub
The password for the attached private key is redhat.
Copy the attached public key to /tmp/id_rsa.pub and the private key to /tmp/id_rsa.
Try to import the private key using seahorse
Receive an error: Import failed, no user has logged in.
Private key import only seems to work if
a) Private key is stored under ~/.ssh/ directory
b) Corresponding public key with the same name (.pub suffix) is also in that dir.
(In reply to comment #3)
> Private key import only seems to work if
> a) Private key is stored under ~/.ssh/ directory
> b) Corresponding public key with the same name (.pub suffix) is also in that
I have the private and pub keys in .ssh, and I still get the import error:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.