Synthesis of the seahorse 'asc' bug + bypass + fix + remaining problems

Hash: SHA1


Here is my complete bug report.

Do I still need to enter a bugzilla entry or is this report enough ?
I am not willing to duplicate entry
while, however, some additional material is provided here.

Please provide us with a feed-back specially on the last issues :
the "minor and major remaining problems".




THE 'asc' BUG in seahorse

appears with seahorse version 2.20 on Ubuntu 7.04
appears with version 2.20 on Ubuntu 7.10
appears with last version 2.20.1 on Ubuntu 7.10

This bug is partially described as :
and :
(this synthesis adds a.o. by-passes and fixes)

This report is also published at :
in order to make by-passes and fixes available for the Ubuntu communauty.

By double-clicking on the file, you get a security warning message.
you are invited to change the extension by .pgp.
even then, you are not able to process the file.

Opening the Properties/Open With of the file,
you see the association with "Importer une clé (import a key)".
You cannot add manually an association with seahorse-tool --import
as this probably conflict with the existing entry.

Hopefully enough you can still import the key by launching seahorse.



rename .asc pgp key file into .pkr file
the double-click will import (silently!) the key to your key ring


FIXING THE BUG (for your self only : no need to be root)

in your home directory (you must select to show hidden files),
there is a .local directory.
there you find a share directory.
within share there is a mime directory; else, create it
inside mime there is a packages directory, else create it
within packages, there is a file Override.xml (uppercase O)
If the file does not yet exist create it with the following content :

<?xml version="1.0" encoding="UTF-8"?>
<mime-info xmlns="";>
     <mime-type type="application/pgp-keys">
          <comment>ascii armoured pgp key</comment>
          <glob pattern="*.asc"/>

if the file already existed, simply add the mime-type :

     <mime-type type="application/pgp-keys">
          <comment>ascii armoured pgp key</comment>
          <glob pattern="*.asc"/>

in the console, do the following :
$ update-mime-database ~/.local/share/mime/

a lot of files are now created (or updated) in your ~/.local/share/mime/

double-click on asc file containing an ascii armoured pgp key :
seahorse will silently import the key.
the problem is solved



The key importation is completely silent. So you don't know if the
importation was successfull or not.
However in the message
with subject ANNOUNCEMENT: Seahorse 2.20
the list of Changes between 1.0 and 2.20
announced a.o. "Give more detail for imported keys. [Adam Schreiber]"



The choice, for pgp keys, of the extensions .pkr and .skr instead of
.asc is problematic.
.skr , as suggested by the name, was the extension for the secret key
ring of the windows version of PGP.
.pkr was for public key ring.
(btw, these extensions are not used by gnupg)
.asc is for ascii armoured things. It is widely used to distribute pgp
(or gpg) public keys or to backup
private keys.
The choices expressed in file /usr/share/mime/packages/seahorse.xml
also reflected in file usr/share/mime/packages/
are a really serious problem.
(btw, there is no file : /usr/share/mime-info/seahorse.mime or
seahorse.keys )
Mind that, when exporting a key, seahorse still suggest the extension
.asc (and is right to do so!)
We must find a definitive solution so that a 'normal' user may simply
click on an .asc file
(e.g. freshly downloaded from the web) to import the key.
I suppose the seahorse developers will take the measures after the bug :
will be carried on by


Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]