** Changed in: seahorse
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889258
Title:
Cannot import SSH key (import button greyed out)
To manage notifications about thi
** Changed in: seahorse (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889258
Title:
Cannot import SSH key (import button greyed out)
To manage notifications
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
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
** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #205
https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
** Also affects: seahorse
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
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.
--
You received this b
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)
Importan
