After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 146385 - crash opening document
crash opening document
Status: RESOLVED DUPLICATE of bug 139211
Product: gpdf
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Martin Kretzschmar
Martin Kretzschmar
Depends on:
Blocks:
 
 
Reported: 2004-06-06 17:14 UTC by Sean Middleditch
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Sean Middleditch 2004-07-09 04:05:27 UTC 
Distribution: Fedora Core release 2 (Tettnang)
Package: gpdf
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: crash opening document
Bugzilla-Product: gpdf
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
opening this document caused gpdf to crash:

http://www.angelfire.com/realm2/kanarinc/KGEsignoutsheet2003.pdf




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 00:05 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gpdf".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Elijah Newren 2004-07-09 21:20:27 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused the crash.  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting
a useful stack trace.
Comment 2 Martin Kretzschmar 2004-07-29 19:11:25 UTC 
Confirming thumbnail crasher in gpdf <= 0.131
Comment 3 Martin Kretzschmar 2004-07-29 19:11:58 UTC 
This is fixed in gpdf 0.132 or 2.7.x and later

*** This bug has been marked as a duplicate of 139211 ***