Seahorse is not associated with application/pgp-signature
In Tails 2.0 rc1. Reported by user, confirmed by me:
Steps to reproduce:
- Download ISO and signature to some folder
- Open folder from Places or similar
- Double click on signature file
The file opens with Gedit (the default app)
Before Jessie, the default app was the Seahorse-Nautilus verification process.
Related to Tails -
#2 Updated by intrigeri 2016-01-15 14:41:34
- Subject changed from Seahorse-Nautilus: Double click on .sig file does not trigger ISO verification to Seahorse is not associated with application/pgp-signature
- Status changed from Confirmed to In Progress
- Assignee set to intrigeri
- Target version set to Tails_2.0
- % Done changed from 0 to 10
Confirmed. GNOME Files correctly tells me that the .sig file is a “detached OpenPGP signature (application/pgp-signature)”, but it’s not associated with whatever Seahorse utility it should be.
Workaround, in case it blocks the documentation update process: add
I’ll try to fix that in time for 2.0. It looks like all Seahorse file associations are gone, so while I’m at it, I’ll check if I can cheaply fix them for a few more MIME types.
#4 Updated by intrigeri 2016-01-15 15:14:20
It would be interesting to understand why the association is not effective on Tails, while it seems to work fine on my Debian sid, and on Tails 2.0~rc1:
$ grep seahorse /usr/share/applications/mimeinfo.cache application/pgp-encrypted=seahorse-pgp-encrypted.desktop; application/pgp-keys=seahorse-pgp-keys.desktop; application/pgp-signature=seahorse-pgp-signature.desktop;
I wonder if this would happen if we were not modifying
config/chroot_local-hooks/59-file_associations. One could try customizing file associations via
config/chroot_local-includes/etc/skel/.local/share/applications/mimeapps.list only, and leave