GNOME Bugzilla – Bug 146414
Crash on launch
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gpdf Severity: normal Version: GNOME2.6.1 unspecified Gnome-Distributor: Debian Synopsis: Crash on launch Bugzilla-Product: gpdf Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: When launched by Mozilla on this specific PDF-file, gpdf crashes. Steps to reproduce the crash: 1. Go to http://www.wired.com/wired/archive/12.06/free.html in Mozilla 2. Click on "Open Source Everywhere"-link 3. Tell Mozilla to open it with gpdf (default on my box) 4. Inform the developers via Bugbuddy Expected Results: gpdf opened the .pdf (or explained why it couldn't). How often does this happen? Every time. Additional Information: I'm using Debian/unstable: ii gpdf 0.131-1 Portable Document Format (PDF) viewer ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 00:34 ------- 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.
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.
Created attachment 29507 [details] Stacktraces I'm not well versed in this, but I tried following the instructions under "Obtaining a stack trace using both Bug Buddy and GDB" and got the attached results. Let me know if I can supply more information. Best regards, Adam.
Thanks for following up. You got a stack trace for two different programs (gpdf and gnome-pdf-viewer). Did bug-buddy report that they both crashed, or just that one of the two did. If just one, which one? Unfortunately, the second stack trace doesn't look useful (probably a stripped binary, and/or excessive optimization flags used when compiling). The first one may be but is still lacking debugging symbols. But I'll reopen so that a maintainer can take a look.
Bug Buddy reports that the second one crashed: "The Application "gnome-pdf-viewer" has quit unexpectedly. You can inform the developers of what happened to help them fix it. Or you can restart the application right now. [Close] [Inform Developers]" This was the window that I originally clicked "Inform Developers" in, and it was when this window was open that I tried to get the stack-traces today. As I am using the packages provided by Debian, they are probably stripped and/or with optimization. I am using the gpdf 0.131-1 package from Debian/unstable (newest at the time of writing).
Here is the stack trace: (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-Y6Jf57" using fallback (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-ElBeF7" using fallback (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-fCSof7" using fallback (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-0wuQP6" using fallback (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-d5lxq6" using fallback (gnome-pdf-viewer:23412): GnomePrint-WARNING **: PS name is NULL, for "/tmp/gnome-print-CtLn25" using fallback Program received signal SIGSEGV, Segmentation fault.
+ Trace 48599
Thread NaN (LWP 23412)
This bug is fixed post 0.131 *** This bug has been marked as a duplicate of 139211 ***