[Okular-devel] [Bug 244285] Okular pdf problem

Hugh Urwin h.e.urwin at gmail.com
Wed Oct 20 02:12:21 CEST 2010


https://bugs.kde.org/show_bug.cgi?id=244285





--- Comment #9 from Hugh Urwin <h e urwin gmail com>  2010-10-20 02:12:16 ---
Just for the records here is a a post i made on sabayon forums after getting
feed up of not being able to read my documents on Sabayon


Re: PDF Files won't open [Solved]

by heu » Sun Oct 17, 2010 18:59 
is it really [solved] ?? I am on 5 oh, which went through all upgrades to the
date and I am having the very same problem. It started failing to open some of
my pdfs and now (started a couple of weeks ago) I cannot open any pdf, which is
a serious problem when you need them just like you need water. When I first
encountered the problem I reported (which never happened on opensuse (my main
distro nowadays even when I am considering using Sabayon as the main one on my
new laptop), nor on kubuntu or pcbsd) the bug on kde.org. The okular (the bug
had been already reported by some gentoo user) developer harshly replied (as if
he had the right to...after all okular is one of the weakest items in kde) that
I should tell my distro packager (which was shown as gentoo by the bug info
collector) to compile poppler with exceptions disabled. Ok I'll admit that I
was wicked and reported it regardless of his previous reply to another gentoo
user (he seems to have issues with gentoo users or packagers) just to see if
he'd take a hint and realize that if you develop a package which depends on how
another package you don't have control over how it is COMPILED (not talking
about a command line switch or a parameter in some configuration file but how
another program is COMPILED!!!) instead of working around it in your own
package ranges from bad to horrible software engineering, but from his reply I
can tell that he failed miserably to realize this... My questions now.. 

Were Sabayon packagers informed of this requirement by either okular or kde
developers?

Has it been mentioned anywhere in the documents or release notes and was just
shrugged off by Sabayon packagers or is this a case of poor documentation from
okular developers??

Am I the only Sabayon user that works with pdf documents and that is why nobody
else complained about it?

Why such a serious problem hasn't been addressed through the last 2 weeks if
the solution to it is as simple as compiling poppler with exceptions disabled?


Anyways the problem wasnt on how poppler was compiled but that the package 
app-text/poppler-qt4 wasn't (for some reason uknown to me...maybe it hasn't
been specified as REQUIRED by okular developers...idk) installed or was gone as
a side product of some update.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Okular-devel mailing list