GNOME Bugzilla – Bug 315804
pdfview crash
Last modified: 2005-09-13 05:25:00 UTC
From: <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.8.0 Subject: pdfview crash Distribution: Debian testing/unstable Package: gpdf Severity: normal Version: GNOME2.10.2 2.8.2 Gnome-Distributor: Debian Synopsis: pdfview crash Bugzilla-Product: gpdf Bugzilla-Component: general Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: Steps to reproduce the crash: 1.open file pdf 2. crash and close Xpdf 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gpdf' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3620)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x4070b248 in waitpid () from /lib/libpthread.so.0
+ Trace 62884
Thread 1 (Thread 16384 (LWP 3620))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-09 16:28 UTC ------- Unknown version 2.8.2 in product gpdf. Setting version to "2.8.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was hercules.veloso@gmail.com.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 305680 ***
Sorry, looks like the other bug is still open... Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?
A good place to start would be to compile with debugging symbols or install debugging symbol packages. Please see http://live.gnome.org/GettingTraces for more information on how to do so. If you can't do this, then if you run the application from the terminal and then paste any abort errors that you get in a comment on bug 305680, that would be somewhat helpful as well.