Summary: | Okular crashes when sending two documents to a network printer right after another | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | cmertes |
Component: | PDF backend | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | aacid, cfeck |
Priority: | NOR | ||
Version: | 0.9.2 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
cmertes
2010-06-08 11:03:56 UTC
Which version of the poppler library do you have installed? The question is which version *did* I have – it's been a while. I think I used Ubuntu Karmic at the time which would make it poppler 0.12.0 according to <http://packages.ubuntu.com/karmic/poppler-utils>. I don't this is a poppler problem, basically i think we miss pdfdoc mutex acquiring on printing and thus printing two documents from the same poppler instance at once just makes things go mad, of course this could and ideally should be fixed by making poppler able to print two different documents at the same time without going crazy. This is just a guess but GlobalParams being on the stack trace and GlobalParams being "global" per app instead of per document makes me think of it as the probable cause for this crash. This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) No answer in more than 6 months |