Summary: | Okular pdf problem | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | alessandro <alexrenzi> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andrey.vul, h.e.urwin, reavertm |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
alessandro
2010-07-12 11:18:15 UTC
Your poppler package is build with exceptions, we do not support that. Talk to your packager so that he does not build poppler with exceptions enabled. *** Bug 249012 has been marked as a duplicate of this bug. *** Created attachment 51204 [details]
New crash information added by DrKonqi
okular crashes (quits with signal 6) when opening some pdf files. it can be reproduced anytime.
Please stop adding new information to this bug, i told you were the problem lies and the problem is your distribution compiling poppler with the unsupported exceptions feature enabled, go to your distribution and complain to them for doing that. *** Bug 251868 has been marked as a duplicate of this bug. *** Without exceptions, I get like 20+ lines of "Bogus memory allocation size" in the console output. But at least it stops crashing. Just for the record, while I agree with Albert here (in Gentoo exceptions in poppler are disabled by default btw), on the other hand disabling them only to pretend those issues signalled by those exceptions never happened is bad idea. That being said it's hard to agree with bug resolution - bug is valid, you just probably don't want it to be handled by bugzilla of okular - I would prefer RESOLVED/UPSTREAM in such case. " on the other hand disabling them only to pretend those issues signalled by those exceptions never happened is bad idea. " You are wrong. Read poppler code. 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. Hugh, you are complaing in the wrong place. A) This bug is about Okular crashing inside poppler code, so if you did not have poppler-qt4 installed obviously this is not the bug you were hitting B) If Sabayon doesn't install poppler-qt4 when installing Okular, again that is the distribution fault, complain to them, not to us C) Obviously we did not inform Sabayon of anything, this is not how things work, it's packagers that need to ask us if in doubt, not us that will be chasing uninformed packagers because to tell the truth, i care the less about Sabayon, i didn't even know it existed until you came here doing lots of noise D) Poppler is broken with exception support enabled. It's not a KDE or Okular requirement, Poppler just doesn't work if you enable exceptions, that is why exceptions are disabled by default in poppler build system, but then again *smart* packagers like to enable things without asking if it is a good idea or doing any test, complain to them. And remember that coming to my bugzilla and saying things like "after all okular is one of the weakest items in kde" will not make me more prone to answer you in the future, at the contrary i am just ignoring you in the future. Now calm down and enjoy life. |