Summary: | okular/KF5 support for 'v4 YCC-RGB' and 'v2 GBR' ICC profiles is broken | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Ralf Habacker <ralf.habacker> |
Component: | PDF backend | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | luigi.toscano, m.weghorn, oliver.sander |
Priority: | NOR | ||
Version: | 1.4.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot
Screenshot (OK) on Debian testing Test PDF file being used |
Description
Ralf Habacker
2018-07-11 10:40:58 UTC
Created attachment 113885 [details]
Screenshot (OK) on Debian testing
It looks just fine for me here on Debian testing with either Okular 1.3.2 shipped by Debian or the current self-compiled development version from git, s. screenshot (attachment 113885 [details]). Is this maybe a problem with some other component/library on your system?
Created attachment 113886 [details]
Test PDF file being used
(Attaching the PDF file being used to make sure it will continue to work independent of the current URL.)
That's odd. I can reproduce the bug with a hand-compiled poppler (no Okular involved) on an up-to-date Debian testing. The problem shows both with the splash and arthur backends (tested using test-render-to-file-qt5). It does not show when using the cairo backend (tested using pdftocairo). Would I need an additional poppler build dependency to get those profiles working? (In reply to Oliver Sander from comment #4) > That's odd. I can reproduce the bug with a hand-compiled poppler (no Okular > involved) on an up-to-date Debian testing. The problem shows both with the > splash and arthur backends (tested using test-render-to-file-qt5). It does > not show when using the cairo backend (tested using pdftocairo). Would I > need an additional poppler build dependency to get those profiles working? Does the output of your cmake command show anything that's missing? At first glance, "lcms2" looks most "suspicious", since it has to do with ICC profiles, but I did not have any closer look so far. Or, you can also just try "sudo apt build-dep poppler" to get all the build-dependencies specified in the Debian source package. I checked, and the poppler installation in question was build without libcms2. I'll try to check tonight whether building with libcms2 changes anything. Ralf, does your Okular installation depend on libcms2? yes rpm -q -f /usr/lib64/libpoppler-qt5.so.1 libpoppler-qt5-1-0.43.0-5.1.x86_64 ldd /usr/lib64/libpoppler-qt5.so.1 | grep poppler libpoppler.so.60 => /usr/lib64/libpoppler.so.60 ldd /usr/lib64/libpoppler.so.60 | grep cms liblcms2.so.2 => /usr/lib64/liblcms2.so.2 rpm -q -f /usr/lib64/liblcms2.so.2 liblcms2-2-2.8-5.3.x86_64 When I build with liblcms2 enabled the bug disappears. Yet you claim that you do have liblcms2 *and* the bug. That's odd. Could it be a suse packaging bug? Debian testing has poppler 0.63.0, maybe something was fixed between 0.43.0 and 0.63.0. poppler 0.43.0 is the official version for openSUSE Leap 42.3 (see https://software.opensuse.org/package/poppler). Using the variant from KDE:Qt:5.11 project (which is 0.63.0) fixes the issue. openSUSE Leap 42.3 is maintained until Jan 2019 (see https://en.opensuse.org/Lifetime), so I guess the official poppler package needs an update. Thanks for you support. File a related bug, see https://bugzilla.opensuse.org/show_bug.cgi?id=1100900 |