Bug 1111771

Summary: Crash when opening print preview
Product: [Fedora] Fedora Reporter: info <info>
Component: okularAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:14:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Example file that consistently crashes okular's print preview none

Description info@kobaltwit.be 2014-06-21 08:23:15 UTC
Created attachment 910985 [details]
Example file that consistently crashes okular's print preview

Description of problem:
I have attached a pdf file that was generated by Scribus. This pdf file opens fine in okular. When I select print preview the application closes without any messages or abrt report.

Version-Release number of selected component (if applicable):
okular-4.12.5-1.fc20

I have tested on both 23-bit and 64-bit installations

How reproducible:
Always with this particular document

Steps to Reproduce:
1. Open attached document in okular
2. Select Print Preview

Actual results:
On the 32-bit system the preview window appears but before the preview itself is rendered the application closes.
On the 64-bit system (a faster machine with more RAM) okular manages to show the preview window and render the preview itself and exits right after that.

Expected results:
Print preview should be displayed and application should not crash.

Additional info:
When run from the command line there is a little more info:
okular A-6_Volledige_klad.pdf 
okular: Fatal IO error: client killed
KCrash: Application 'okular' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/janssege/.kde/socket-legolas.kobaltwit.lan/kdeinit4__0

I have also tried the same in Evince. Evince can display the print preview correctly.

Comment 1 Fedora End Of Life 2015-05-29 12:10:49 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 info@kobaltwit.be 2015-05-29 12:24:17 UTC
The end of life reminder triggered me to retest this.

okular-14.12.3-1.fc21.x86_64 (on Fedora 21) no longer crashes, so bug got fixed upstream apparently.

Comment 3 Fedora End Of Life 2015-06-29 21:14:57 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.