GNOME Bugzilla – Bug 156846
gpdf does not start up
Last modified: 2005-01-28 12:13:17 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gpdf Severity: blocker Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gpdf does not start up Bugzilla-Product: gpdf Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: After upgrading gpdf with up2date, gpdf does not start up any more Steps to reproduce the crash: 1. start up 2. 3. Expected Results: How often does this happen? allways Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gpdf' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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 -151131808 (LWP 3861)] (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)...0x009ff7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 51459
Thread 1 (Thread -151131808 (LWP 3861))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-29 14:28 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gpdf". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was karlcottenie@hotmail.com. 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.
Unique stack trace AFAICS
*** Bug 161614 has been marked as a duplicate of this bug. ***
Duplicate was under 2.8.x, and was with gedit; reassinging to libegg due to the stack trace.
*** This bug has been marked as a duplicate of 157723 ***