Bug #10943

Seahorse is not associated with application/pgp-signature

Added by emmapeel 2016-01-15 07:40:01 . Updated 2016-01-27 13:31:35 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_2.0
Start date:
2016-01-15
Due date:
% Done:

100%

Feature Branch:
bugfix/10943-seahorse-associations
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

Related issues

Related to Tails - Bug #10941: seahorse-tool --import does not import keys completely Resolved 2016-01-14

History

#1 Updated by emmapeel 2016-01-15 07:42:23

  • related to Bug #10941: seahorse-tool --import does not import keys completely added

#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 application/pgp-signature=seahorse-pgp-signature.desktop to /etc/gnome/defaults.list.

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.

#3 Updated by intrigeri 2016-01-15 14:42:02

  • Priority changed from Normal to Elevated

#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 /etc/gnome/defaults.list with config/chroot_local-hooks/10-tbb and 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 /etc/gnome/defaults.list untouched.

#5 Updated by intrigeri 2016-01-15 16:15:25

  • Feature Branch set to bugfix/10943-seahorse-associations

#6 Updated by intrigeri 2016-01-15 16:57:44

  • Assignee changed from intrigeri to anonym
  • % Done changed from 10 to 50
  • QA Check changed from Dev Needed to Ready for QA

#7 Updated by anonym 2016-01-18 02:47:17

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:92dcefe0810a2945749729cd5f2ecdcf5a1ab111.

#8 Updated by anonym 2016-01-18 03:02:05

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#9 Updated by anonym 2016-01-27 13:31:35

  • Status changed from Fix committed to Resolved