Seahorse cannot set up SSH keys for login servers

Bug #745245 reported by Asa Zernik
108
This bug affects 21 people
Affects Status Importance Assigned to Milestone
seahorse
Fix Released
Medium
seahorse (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: seahorse

I just updated to the Natty Alpha. When I try creating an SSH key and setting it up, I get an error on the set-up (putting the public key on the server) stage. The error message is as follows:

Couldn't configure Secure Shell keys on remote computer.

** (process:29153): WARNING **: couldn't open fd 23: Bad file descriptor

** (process:29154): WARNING **: couldn't open fd 23: Bad file descriptor

** (process:29155): WARNING **: couldn't open fd 23: Bad file descriptor
Permission denied (gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: seahorse 2.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Tue Mar 29 13:45:09 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/seahorse
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Asa Zernik (asaz989) wrote :
Revision history for this message
Mathias Bøhn Grytemark (mboehn) wrote :

I have the same problem.
Using Natty beta 1.

** (process:2508): WARNING **: couldn't open fd 23: Bad file descriptor
Permission denied, please try again.

** (process:2509): WARNING **: couldn't open fd 23: Bad file descriptor
Permission denied, please try again.

** (process:2510): WARNING **: couldn't open fd 23: Bad file descriptor
Permission denied (publickey,password,keyboard-interactive).

This happens before I'm asked for the password.

Package: seahorse 2.32.0-0ubuntu3
Architecture: i386

Revision history for this message
Paul Ni (nikulinpi-gmail) wrote :

Can reproduce

Revision history for this message
cmosetick (cmosetick) wrote :

I have the same issue on a clean install of Natty beta 2.

Revision history for this message
Adam Dingle (adam-yorba) wrote :

I'm seeing this too (on Fedora 15, actually). I've filed a bug upstream here:

https://bugzilla.gnome.org/show_bug.cgi?id=648224

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, thanks Adam for sending it to GNOME

Changed in seahorse (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in seahorse:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Michael Saunders (usalabs14) wrote :

Above shows "Could't open fd 23", mine show as "Couldn't open fd 27", but all is the same error.

I upgraded from 10.10 to 11.04. 10.10 had no problems with seahorse.

Revision history for this message
Lionel FELICITE (deogracia) wrote :

Hi,
I'm on 11.04 and I've got this issue too.

You can use the "ssh-copy-id" as a workaround until it's fixed

For example : ssh-copy-id "user@server -p $PORT$"

-p $PORT$ is necessary if you don't use the default port (22)

Revision history for this message
Atasa Rossios (atasa-rossios) wrote :

I have the same problem with natty official release... I also did everything via command line (ssh-copy-id) and the problem now is that can't login to remote server...
It is OK to the same procedure from another machine with maverick though

Revision history for this message
Human Ashrafi (human-ashrafi) wrote :

I had exactly the same error. I solved it by reinstall gnome-keyring since the autostart applications where somehow messed up.

dpkg --force-all -P gnome-keyring
aptitude install gnome-keyring

So I got my startup file /etc/xdg/autostart/gnome-keyring-ssh.desktop back and gnome-session-properties showed gnome-keyring-ssh in the list again.

What I did before was to manually add the gnome-keyring-ssh with "/usr/bin/gnome-keyring-daemon --start --components=ssh" as exec command with use of gnome-session-properties. This command seemed to work well since I saw that gnome-keyring-daemon --start reported SSH_AUTH_SOCK=/tmp/keyring-IzvzoK/ssh.
I have no idea why that didn't work and reinstalling gnome-keyring with the missing autostart scripts worked. I guess I must have missed some extra Options like "X-GNOME-Autostart-Phase=Initialization", hence the ssh-agent was registered to the system too late within the startup progress. And i don't know why the files were missing in first place either.

Revision history for this message
Christopher Stevens (stevens-chrisj) wrote :

I have tried this resolution on two Ubuntu 11.04 Desktop x64 machines with no success. I ran:

sudo dpkg --force-all -P gnome-keyring
sudo aptitude install gnome-keyring

Is there something else that must be done?

Changed in seahorse:
status: New → Confirmed
Changed in seahorse:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.