Ubuntu
seahorse package

mime descriptor file missing from Seahorse package

Bug #150654 reported by Martin Meyer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seahorse
Fix Released
Medium
seahorse (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: seahorse

I've filed bug 42473 upstream in Gnome's bugzilla against Seahorse (http://bugzilla.gnome.org/show_bug.cgi?id=424473). The issue I am seeing is that I can't import my ssh private key into seahorse, and it appears that the cause is a missing file in the seahorse package. The file is:

/usr/share/mime/packages/seahorse.xml

which tells nautilus how to identify ssh keys and assign their mime type. Since seahorse uses mime types to control key importing, this functionality currently fails for me. Can we get seahorse repackaged to include this xml file?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report.

Changed in seahorse:
importance: Undecided → Low
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in seahorse:
status: Unknown → Fix Released
Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. I was wondering whether this is still an issue for you. Is it possible for you to try with latest Ubuntu release? I was unable to reproduce the bug on Hardy.

If it is indeed still an issue, please provide us your current version of both seahorse and the shared-mime-info package.

Thanks in advance. I'm setting the seahorse (Ubuntu) task of this bug to 'Incomplete' to indicate we need more information to reproduce the bug.

Changed in seahorse:
status: Confirmed → Incomplete
Revision history for this message
Martin Meyer (elreydetodo) wrote :

shared-mime-info 3.39-1ubuntu1
seahorse 2.22.2-0ubuntu1

I don't think this has been fixed, but the issue may be moot. It seems that Seahorse doesn't do SSH key management anymore, it's now the responsibility of gnome-keyring[1] and there doesn't seem to be a UI for it. This mime info may still be needed, but I don't think it's needed by Seahorse. Should we ask the Seahorse and/or gnome-keyring devs to confirm this?

[1] http://live.gnome.org/GnomeKeyring/Ssh

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

From the Seahorse help I understand that importing is done for public keys only: "To import keys choose Key > Import and select, from the file chooser, a file containing at least one ASCII armored public key.".

From that I would not expect importing private SSH keys to work anymore. And it would indeed be an indication that some mime info is not needed by Seahorse. You can ask the Seahorse developers for confirmation if you like (some ubuntu developers from the changelog file might know too).

Public ASCII armored keys are recognized in the file chooser when importing. Can you confirm that?

Importing public SSH keys gives an error message, but I'd say that should be fixed in the help text by excluding them there. Do you agree with that? If so, I will file a separate bug for that.

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

I filed bug 252288 for the documentation issue.

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

the issue should be fixed closing the bug, feel free to reopen if you still get the issue though

Changed in seahorse:
status: Incomplete → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in seahorse:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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