Cannot import SSH key (import button greyed out)

Bug #1889258 reported by Ricky Hewitt
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
seahorse
New
Unknown
seahorse (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Ubuntu 20.04.1 LTS

seahorse:
  Installed: 3.36-1

When importing an SSH key the option to complete the import is disabled / greyed out.

The import cannot be completed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: seahorse 3.36-1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 28 15:45:16 2020
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2020-07-24 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)

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

Thank you for your bug report. Could you give some detail on the type of key you try to import and what action you do exactly to trigger the import?
Do you have any warning on the command line or in the 'journalctl -b 0' log at the time of the import?

Changed in seahorse (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ricky Hewitt (rickyhewitt) wrote :

Hi Sebastien,

The type of key is a 2048-bit RSA key.

Additional notes:

- The issue occurs with both password & passwordless keys.
- The issue only occurs when importing. (Creating a new SSH key via the Seahorse UI works fine)

There are no warnings or journalctl output.

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

Thanks, it's probably better if you could report it directly to the software writers on

https://gitlab.gnome.org/GNOME/seahorse/-/issues

Changed in seahorse (Ubuntu):
status: Incomplete → New
information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Ricky Hewitt (rickyhewitt) wrote :

Thanks, it looks like it has already been reported upstream.

I have added a remote bug watch.

https://gitlab.gnome.org/GNOME/seahorse/-/issues/205

Revision history for this message
Ricky Hewitt (rickyhewitt) wrote :

For anyone interested in a workaround:

It looks like if you import both the public and private key manually into ~/.ssh (may also need to sudo systemctl restart gdm) and then run seahorse again, they should show up.

Changed in seahorse (Ubuntu):
status: New → Triaged
Changed in seahorse:
status: Unknown → New
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.