Package Details: qpdfview 0.4.17beta1-2

Git Clone URL: https://aur.archlinux.org/qpdfview.git (read-only)
Package Base: qpdfview
Description: A tabbed PDF viewer using the poppler library.
Upstream URL: https://launchpad.net/qpdfview
Licenses: GPL2
Submitter: adamreichold
Maintainer: adamreichold
Last Packager: adamreichold
Votes: 200
Popularity: 2.738233
First Submitted: 2012-02-08 13:11
Last Updated: 2016-11-20 18:43

Dependencies (10)

Required by (0)

Sources (1)

Latest Comments

bilthekid commented on 2017-07-22 14:43

@adamreichold Thank you very much. That was the problem. Nevertheless, I did not try to recover the database (just deleted it) since my concern had to do with getting back 'restore tab' functionality.

adamreichold commented on 2017-07-22 14:37

@bilthekid The Qt4- and Qt5-based versions do not share a database which is why one is affected but not the other. From the error message, it sounds like qpdfview's database usually stored in ~/.local/share/data/qpdfview/qpdfview/database for the Qt5-version got corrupted. You can try to rename this file and check if things work afterwards. You can also try if you can recover the data [1].

[1] https://stackoverflow.com/questions/18259692/how-to-recover-a-corrupt-sqlite3-database

bilthekid commented on 2017-07-22 14:13

I get the following message: QSqlError("11", "Unable to execute statement", "database disk image is malformed"). I did google it but did not find anything useful. And yes, the qpdfview-bzr package is affected too. Moreover, I checked the qpdfview-qt4 and everything works as it was supposed to.

adamreichold commented on 2017-07-22 14:02

@bilthekid Can you please run qpdfview from a terminal and see if any messages are logged? If this does not yield any information, could you try running the qpdfview-bzr package whether the current trunk is still affected? Thanks.

bilthekid commented on 2017-07-22 13:41

In current version of qpdfview, tab restoring functionality does not work at all. When I close the app and reopen it, all previously opened tabs has disappeared; and I do have the 'restore tabs' box checked. I do not know exactly when did this happened and if it is a problem related to qt5. However, is anyone aware of this problem, its cause and maybe a way to restore the functionality?

emulti commented on 2017-07-14 13:45

To answer my previous comment, setting
QT_QPA_PLATFORMTHEME=gtk2
in .xinitrc produces correct behaviour. I therefore think this issue is due to a bug or issue in qt5ct.

emulti commented on 2017-07-13 16:49

I found the Qt5 version of qpdfview does not seem to completely pick up platform theme settings via qt5ct (on XFCE 4.12) Although the theme (gtk2 in my case) is picked up from qt5ct, (and message 'qt5ct: using qt5ct plugin' is shown) the file open/save dialogs revert to QfileDialog, with no filesystem bookmarks shown.
Using "qpdfview --platformtheme gtk2" to run from terminal does use the gtk2 dialogs however.
Why could this be?

The qpdfview-qt4 AUR package that someone has kindly made does however pick up the settings in qtconfig-qt4 correctly.

adamreichold commented on 2017-06-17 13:13

Hello Alad,

Sorry for taking some time to answer your question: I am not sure adding the signature is worth it, as makepkg will complain about the missing key, since it is my personal one which is in no way affiliated with the Arch Linux key ring. Also, since I have very few signatures on this key, users will be basically be forced to import this key and trust it directly. Hence the added credibility on top of the plain checksum is minimal, but it will make first time installation more complicated...

Best regards, Adam.

Alad commented on 2017-06-09 00:36

Since you're the author, would you mind adding a GPG signature for the source tarball?

EDIT: there's already one on launchpad:

https://launchpad.net/qpdfview/trunk/0.4.17beta1/+download/qpdfview-0.4.17beta1.tar.gz.asc

in that case, please add it to the pkgbuild. :)

idomeneo1 commented on 2016-11-27 19:45

It's possible I may have forgotten to change the poppler support, as it's what I'm using now...

I also attempted to compile other frontends for mupdf, and they're broken, too. You'd think that, given the size of mupdf, it would be filled with backward compatibility!
Unfortunately, I'm not enough of a hack to sort out mupdf's incompatibilities :(

All comments