Can't open DjVu document

[Peter Passchier]

Have installed qpdfview plus ps & djvu plugins through the Ubuntu 18.04 repositories:

qpdfview 0.4.14
PDF support using Poppler 0.62.0
PS support using libspectre 0.2.8
DjVu support using DjVuLibre 3.5.27
Printing support using CUPS 2.2.7

I tried opening 2 DjVu documents, on both got the message that it could not be opened. Atril (Evince) was able to open it fine.
Sample doc: http://www.nzdl.org/custom/iarchive/collect/ebooks/index/assoc/HASHeb05.dir/___king.djvu

[Adam Reichold (adamreichold)]

Hello Peter,

thank you for taking the time to report this! The document you link opens fine here so I suspect something in qpdfview's setup not working quite right. Could you please try to open one such document by starting qpdfview from a terminal to check if any additional messages are logged? Also running file --mime-type against one of those documents would be helpful. Thanks!

Best regards,
Adam

[Adam Reichold (adamreichold)]

You could also give the daily builds from [1] a try as I found

* Fixed an incompatibility with FDo's shared MIME type database that broke opening DjVu documents.

in the CHANGES for 0.4.16.

[1] https://code.launchpad.net/~adamreichold/+archive/ubuntu/qpdfview-dailydeb

[Peter Passchier (peter-passchier)]

Thank you for telling me about the dailydebs. I installed the updated version (it removed the ps and djvu plugins, but I installed them again), and then it worked!

[Peter Passchier (peter-passchier)]

It (apt) also complained about a conflict with qpdfview-translations, so I had to manually remove that for the updated install to complete. I have re-installed qpdfview-translations, and that went without a problem.

[Peter Passchier (peter-passchier)]

Just for completeness sake, the new qpdfview wasn't actually installed after I deleted qpdfview-translations; the general update left qpdfview alone, and so it actually started working with 0.14.14. I now have upgraded to qpdfview 0.4.18beta1 (and it still works great). Not sure why the plugins automatically got marked for deletion; I could reinstall them without any problems or messages.

The conflicting file with qpdfview-translations: /usr/share/qpdfview/help_az.html
(I now can't install it.) It is a strange document, partly Azeri(??) partly English.

[Peter Passchier (peter-passchier)]

Afterthought: because I always have qpdfview open, I might have forgotten to restart it after installing the DjVu-plugin... So when I did (when I thought the new version was installed) it started working as it was supposed to.

I now only have qpdfview 0.4.18beta1 installed, no plugins (or translations), and both viewing ps files and djvu work, so I'm happy to stay with this. I know you are very conscientious with your work, so I don't have a problem trusting the dailydebs.

Just to say: it might not have been a bug in the first place! (But I'm not going to check now, unless you want me to.)

[Adam Reichold (adamreichold)]

Hello again,

the dailydebs do not use split packages for the plugins and translations. So I think you should only install the "qpdfview" package from the dailydebs and nothing else.

> and so it actually started working with 0.14.14.

This I do not really understand. My guess is you were affected by the MIME type issue. So could you maybe try to switch back to plain 0.4.14 from the Ubuntu repos again to make sure it does not work, install all qpdfview packages and install the dailydeb and check that it does work.

Otherwise I am hesitant to close without properly understanding the underlying issue.

Best regards,
Adam

[Peter Passchier (peter-passchier)]

OK, I uninstalled qpdfview, disabled the dailydebs and did apt-update, and installed qpdfview qpdfview-djvu-plugin qpdfview-ps-plugin qpdfview-translations.

Unfortunately, it seemed to have forgotten all my opened documents... But not my settings nor the Recent documents. Both DjVu and ps work. Not sure about the mime type issue, my versions are all back to the original report.

So I'm afraid this is yet another invalid report...
Would you recommend staying with this, or can I go back to the dailydebs?

[Adam Reichold (adamreichold)]

> So I'm afraid this is yet another invalid report...

Don't worry about it. Better safe than sorry. Personally, I very much prefer invalid reports that are followed up than actual bugs I cannot resolve because the reporter is unable to help diagnose the issue.

> Would you recommend staying with this, or can I go back to the dailydebs?

I actually recommend going with the dailydebs for now as I seem to have quite the problem of actually getting a release out and into the distribution archives. Hence, the dailydebs are probably more stable than what most distributions ship ATM. (I hope your recently opened documents will come back with this as well, as starting with 0.4.18beta1 did migrate the internal database schema to the newest version. Sorry for not thinking about that before asking you to downgrade again.)