Bug 177531 - gpdf crashes on a PDF file
Summary: gpdf crashes on a PDF file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gpdf
Version: 4.0
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-11 16:59 UTC by Radek Bíba
Modified: 2013-04-02 04:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 16:17:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Radek Bíba 2006-01-11 16:59:28 UTC
Description of problem:
gpdf crashes for me when I try to display a testing PDF file. This file is
absolutely normal, not corrupted, viewable in other PDF viewers. It's a
documentation file from package prelink, which is stored as
/usr/share/doc/prelink-0.3.3/prelink.pdf on those RHEL 4 arches where it's
available (unfortunately not on ia64).

Version-Release number of selected component (if applicable):
gpdf-2.8.2-7.3.ia64

How reproducible:
Always

Steps to Reproduce:
1. "grab" /usr/share/doc/prelink-0.3.3/prelink.pdf
2. open it in gpdf
  
Actual results:
Crash, error dialog with 'The Application "gnome-pdf-viewer" has quit
unexpectedly.' is displayed and this is written to the command line:
(gpdf:13791): Bonobo-CRITICAL **: file bonobo-control-frame.c: line 539
(bonobo_control_frame_control_deactivate): assertion `frame->priv->control !=
CORBA_OBJECT_NIL' failed


Expected results:
The PDF file is displayed.

Additional info:

Comment 2 Jiri Pallich 2012-06-20 16:17:10 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.