Bug#627027: evince-gtk: registers unsupported image/* (e.g., image/jpeg) MIME type with high priority

[Jonathan Nieder]

Package: evince-gtk
Version: 3.0.0-3
Severity: important
Justification: breaks run-mailcap, as used by e.g. mutt
Files: /usr/lib/mime/packages/evince-gtk

Hi,

Whenever I try to open a jpeg attachment in mutt, I get an evince
window with

	Unable to open document

	File type JPEG image (image/jpeg) is not supported

Seems weird --- why is mutt (meaning "run-mailcap --action=view")
asking for evince, then?

| $ grep jpeg /etc/mailcap
| image/jpeg; /usr/bin/xli -quiet '%s'; test=test -n "$DISPLAY"; description=JPEG Image; nametemplate=%s.jpg
| image/jpeg; display 'jpeg:'%s''; test=test -n "$DISPLAY"
| image/pjpeg; display 'jpeg:'%s''; test=test -n "$DISPLAY"

Checking under /usr/lib/applications, it seems xli registers
image/jpeg with a priority of 3, and imagemagick uses a priority of 2.
But evince-gtk has, in /usr/lib/mime/packages/evince-gtk:

	image/*; evince %s; test=test -n "$DISPLAY"; nametemplate=%s.dummy; priority=5

If I remember correctly, evince 2 did support JPEGs, making this entry
less harmful then.  Known problem?  Any way I can help?

This is related to but not identical to Bug#619564, which discusses
the mailcap priority from the time when evince did support displaying
such typical images.