Summary: | Okular crashes on close if the print preview has not finished | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Kevin Lyles <kevinlyles> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aacid, justin.zobel, kevinlyles, michel.ludwig |
Priority: | NOR | ||
Version: | 0.19.1 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Kevin Lyles
2011-04-10 17:23:13 UTC
That's probably a cause of the nested event loop in Okular::Document::closeDocument. Hmm... the part a child of the print dialog...? Can you please provide a working link to the pdf and the exact steps you do to make okular crash? Unfortunately, there does not seem to be a version of that pdf available any longer. The steps I took were to open the file, open Print Preview, close Print Preview, then close the file. You may have to wait a minute before opening Print Preview (I usually did it after the document had rendered). I will see if I can find another file that does this. I have found another file that has the same issue: http://madisonareampo.org/maps/documents/MadisonAreaMCD.pdf I can attach or e-mail the file if needed; just let me know. Created attachment 59679 [details]
New crash information added by DrKonqi
This is the crash information with the second file.
Seems a bad interaction of the print preview thread still running and us wanting to shut down, need to take a closer look once my main machine is back since debuginning this in a 12" screen is quite painful *** Bug 309734 has been marked as a duplicate of this bug. *** Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |