Package Details: qpdfview-bzr 2070-1

Git Clone URL: https://aur.archlinux.org/qpdfview-bzr.git (read-only, click to copy)
Package Base: qpdfview-bzr
Description: A tabbed PDF viewer using the poppler library. (development version)
Upstream URL: https://launchpad.net/qpdfview
Licenses: GPL2
Conflicts: qpdfview
Submitter: adamreichold
Maintainer: adamreichold
Last Packager: adamreichold
Votes: 8
Popularity: 0.000006
First Submitted: 2012-02-07 20:39 (UTC)
Last Updated: 2018-05-06 13:58 (UTC)

Dependencies (11)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

keren_sky commented on 2018-05-06 12:34 (UTC)

Seeing this and compile fails:

In file included from /usr/include/mupdf/fitz/device.h:7:0, from /usr/include/mupdf/fitz/display-list.h:7, from sources/fitzmodel.cpp:33: /usr/include/mupdf/fitz/colorspace.h:201:85: error: ‘fz_stream’ has not been declared fz_colorspace fz_new_icc_colorspace_from_stream(fz_context ctx, const char name, fz_stream in); ^~~~~~~~~ sources/fitzmodel.cpp: In function ‘qpdfview::Model::Outline {anonymous}::loadOutline(fz_outline*)’: sources/fitzmodel.cpp:58:18: error: ‘fz_outline {aka struct fz_outline_s}’ has no member named ‘dest’; did you mean ‘next’? if(item->dest.kind != FZ_LINK_NONE)

DungeonMaster commented on 2016-12-21 19:11 (UTC)

@adamreichold I removed qpdfview-bzr, replaced the qt5 poppler with the git version in the AUR, had qpdfview-bzr build again and.. it works so *shrug* thank you for the assist.

adamreichold commented on 2016-12-21 17:59 (UTC)

@DungeonMaster I just tried to disable and enable "Decorate pages" using the settings dialog and everything seemed to work as expected, so I can't really tell you much expect to open a bug report on Launchpad and describe exactly what you are doing, what you expect to happen and what happens instead.

DungeonMaster commented on 2016-12-21 10:18 (UTC)

@adamreichold I'm wondering what the deal is with the program. I go to turn off settings like "Decorate Pages" and they don't work. I check settings again and "Decorate Pages" is checked again. Is there something in a build or is it something on my end?

adamreichold commented on 2016-11-03 12:18 (UTC)

@sleeping Please do not flag VCS packages as out-of-date due to an upstream update as makepkg will always fetch the latest trunk revision and update the package version during build.

adamreichold commented on 2016-11-02 11:24 (UTC)

@pmattern I do agree about the hooks and will update both packages as soon as I find the time to do so. (Of course, patches welcome in any case.) Concerning the debug symbols, I concur with @lahwaacz that this should be enabled by each user as necessary. Of course, I would be happy to find a back trace of these recurring crashes in the project's bug tracker on Launchpad.

lahwaacz commented on 2016-10-29 09:50 (UTC)

Enabling debugging symbols in packages is the user's responsibility, just like fetching the latest version of VCS packages whenever necessary. Both tasks are actually equally easy, see https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces In any case, it doesn't make sense to enforce these as defaults in the "upstream" PKGBUILD just because you're having some problems...

pmattern commented on 2016-10-29 09:24 (UTC)

It would make sense to replace the install script with pacman hooks. You'd just have to drop the script and add gtk-update-icon-cache as runtime dependency. This would allow for ditching dependency hicolor-icon-theme which would be pulled by gtk-update-icon-cache. Same goes for package qpdfview. Also, I wonder whether it wouldn't make sense to enable debugging. Right now both stack traces and backtrace tend to be useless one-liners when qpdfview crashes and dumps core. This is a pitty when it comes to chasing down crashes which happen sporadically but cannot be reproduced easily (like one involving opening several PDF files in parallel by clicking links in Firefox I'm seeing since a while here). Given that one main purpose of VCS packages is testing debug symbols should actually always be enabled in these packages, IMHO, as the advantages outweigh disadvantages like higher resource usage or performance penalty in this case.

b52 commented on 2016-10-23 13:49 (UTC)

@adamreichold The screenshot was taken while tiling was disabled. If I however enable tiling in combination with device pixels, I get an even weirder output as shown in https://paste.xinu.at/z105oj/. Note that the quality of the rendered output is very bad without the device pixels option.

adamreichold commented on 2016-10-21 05:13 (UTC)

@b52 The screenshot looks like only the first tile composing the page is rendered (or if the others are rendered they are at least not displayed). Could you please check if things work correctly if tiling is disabled via the Graphics tab of the Settings dialog? If so, please file a bug on Launchpad that tiling and non-unit device pixel ratios are incompatible. Thanks!

« First ‹ Previous 1 2 3 4 5 6 Next › Last »