After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 754468 - Make it possible to install evince plugins
Make it possible to install evince plugins
Product: evince
Classification: Core
Component: general
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on: 759497
Reported: 2015-09-02 14:57 UTC by Bastien Nocera
Modified: 2018-05-22 16:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Bastien Nocera 2015-09-02 14:57:29 UTC
1. Install a stock Fedora 22 with evince included
2. Try to open a DjVu file (plenty of them at
3. Evince opens and says:
File type DjVu image (image/vnd.djvu) is not supported

Instead, I should be asked whether I want to install the evince-djvu package in gnome-software.
Comment 1 Bastien Nocera 2015-09-02 14:58:53 UTC
This might also be a problem in gnome-books, when DjVu support is added (see bug 745327).
Comment 2 Richard Hughes 2016-02-22 20:34:23 UTC
Does this work better in F23?
Comment 3 Nerijus Baliunas 2016-02-22 22:03:43 UTC
Same message "File type DjVu image (image/vnd.djvu) is not supported".
Comment 4 Marek Kašík 2016-02-23 09:44:11 UTC
I've tried to fix this as Bastien suggested but I encountered the #759497.
Comment 5 Richard Hughes 2016-02-23 10:02:24 UTC
Ohh, Evince shows the message... I thought the message was in gnome-software. I think evince should be installing by mimetype and not by package name and then just watching for the mimetype to show up async.
Comment 6 Marek Kašík 2016-02-23 10:07:12 UTC
I'm reassigning this to evince.
Comment 7 GNOME Infrastructure Team 2018-05-22 16:20:07 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: