After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648224 - configure key for secure shell -> bad file descriptor, permission denied
configure key for secure shell -> bad file descriptor, permission denied
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
3.0.x
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2011-04-19 14:48 UTC by Adam Dingle
Modified: 2011-09-15 08:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2011-04-19 14:48:17 UTC 
I'm using Seahorse 3.0.0 on Fedora 15 alpha.

When I select an SSH key and choose Remote->Configure Key for Secure Shell, I'm prompted to enter a computer name and login name.  I then click Set Up and I see this:

    Couldn't configure Secure Shell keys on remote computer.

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

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

    ** (process:8832): WARNING **: couldn't open fd 22: Bad file descriptor
    Permission denied (publickey,password).

This looks like the same bug upstream at Ubuntu:

  https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/745245
Comment 1 Asa Zernik 2011-05-02 16:44:59 UTC 
I can confirm this (I am bug reporter from the Ubuntu bug). I am using Seahorse 2.32.0 on Ubuntu Natty. The bug was first introduced between Maverick and Natty, both of which use the same version of Seahorse.

Interesting comparison here - Fedora 15 uses Gnome (and Seahorse) 3, while Ubuntu has stayed with the same version since the Maverick, where configuring SSH keys was working. What's changed in the environment in both distributions? My first guess was Kerberos, given the error messages, but at first glance in the Ubuntu repositories that doesn't seem to have changed from Maverick to Natty. I'll do a more thorough check when I'm at my Maverick box.
Comment 2 Asa Zernik 2011-05-02 17:07:59 UTC 
On further inspection (looking through Ubuntu and Fedora repos) the only common minor version change I'm seeing in the Seahorse dependencies is in libsoup (in Ubuntu from 2.31.92 to 2.34.0, in Fedora from 2.31.90 to 2.34.0).

Unfortunately I don't have debugging symbols installed for Seahorse; anyone know how I could get them?
Comment 3 Stef Walter 2011-06-04 20:25:14 UTC 
Looks like openssh has started closing the file descriptors that we use to communicate with our prompt program.
Comment 4 Aaron Todd 2011-07-03 20:19:56 UTC 
I just did a fresh install of 11.04 with Unity and have this issue. Are there any fixes? I do like using the GUI key management.
Comment 5 Stef Walter 2011-07-05 08:32:10 UTC 
The prompting needs to be rewritten so that it takes place in seahorse-ssh-askpass program. I haven't had time to do this yet.
Comment 6 Stef Walter 2011-09-15 08:40:50 UTC 
Fixed in seahorse master. Will be part of the next seahorse 3.2.