Bug 1308628 - djvu support doesn't work for names without extension
Summary: djvu support doesn't work for names without extension
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 16:14 UTC by vvs
Modified: 2016-03-26 18:19 UTC (History)
3 users (show)

Fixed In Version: evince-3.18.2-4.fc23 evince-3.18.2-5.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-12 11:49:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description vvs 2016-02-15 16:14:05 UTC
Description of problem:

I can't view djvu documents in evince. The evince-djvu support package is installed.

Version-Release number of selected component (if applicable):

evince-djvu-3.18.2-3

How reproducible:

Always

Steps to Reproduce:
1. Try to open djvu document in evince

Actual results:

File type DjVu document (image/vnd.djvu+multipage) is not supported

Expected results:

It should work.

Additional info:

Comment 1 Marek Kašík 2016-02-15 16:19:55 UTC
I can open djvu files on my F23 just fine. Maybe it is related to a specific djvu. Could you point us to one showing the problem?

Comment 2 vvs 2016-02-15 16:51:15 UTC
As it turned out that happens when a file name doesn't have an extension. In other case it opened the file and then crashed. That seems to happen with any djvu file I've tried.

Comment 3 vvs 2016-02-15 17:26:30 UTC
The crash seems to be random and I can't reproduce it. The only problem is a missing file name extension.

Comment 4 vvs 2016-02-15 18:41:38 UTC
This patch fixed the problem:

--- djvudocument.evince-backend~	2015-12-15 19:13:05.000000000 +0200
+++ djvudocument.evince-backend	2016-02-15 20:37:26.587773218 +0200
@@ -80,4 +80,4 @@
 TypeDescription[zh_HK]=DjVu 文件
 TypeDescription[zh_TW]=DjVu 文件
 TypeDescription[zu]=Amadokhumende we-DjVu
-MimeType=image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;
+MimeType=image/vnd.djvu;image/vnd.djvu+multipage;application/x-ext-djv;application/x-ext-djvu;

Comment 5 Marek Kašík 2016-02-16 11:17:00 UTC
Thank you for the hint. This is currently discussed in this upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=754467

Comment 6 Marek Kašík 2016-03-08 17:01:18 UTC
I've pushed a fix for this to F23, F24 and rawhide.

Comment 7 Fedora Update System 2016-03-08 17:04:25 UTC
evince-3.18.2-4.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c0bdac228d

Comment 8 Fedora Update System 2016-03-08 17:04:29 UTC
evince-3.18.2-5.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cf8c54609f

Comment 9 Fedora Update System 2016-03-09 22:56:17 UTC
evince-3.18.2-4.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c0bdac228d

Comment 10 Fedora Update System 2016-03-10 01:57:16 UTC
evince-3.18.2-5.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cf8c54609f

Comment 11 Fedora Update System 2016-03-12 11:49:35 UTC
evince-3.18.2-4.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2016-03-26 18:19:03 UTC
evince-3.18.2-5.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.