GNOME Bugzilla – Bug 154193
ggv crashes when space key is typed.
Last modified: 2005-03-30 15:57:20 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: GGV Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: ggv crashes when space key is typed. Bugzilla-Product: GGV Bugzilla-Component: GGV Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: ggv crashes when there is a opened document and space key is typed Steps to reproduce the crash: 1. Open a ps file with ggv. 2. Type space key. 3. Expected Results: You mean expected error result or expected normal result? Well, the error expected is a crash, and the function I expected was to move to next page, as gv does. How often does this happen? Every time I open open a file and type space key, i. e., always. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/ggv' (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)...[Thread debugging using libthread_db enabled] [New Thread -151175040 (LWP 2798)] (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)...(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)...0x003b37a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50642
Thread 1 (Thread -151175040 (LWP 2798))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-30 15:12 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "GGV". 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 candida@ic.unicamp.br. 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
*** Bug 156165 has been marked as a duplicate of this bug. ***
*** Bug 157666 has been marked as a duplicate of this bug. ***
Matches the stack trace in bug 146401 exactly. *** This bug has been marked as a duplicate of 146401 ***
*** Bug 159962 has been marked as a duplicate of this bug. ***
*** Bug 160054 has been marked as a duplicate of this bug. ***
*** Bug 160347 has been marked as a duplicate of this bug. ***
*** Bug 163739 has been marked as a duplicate of this bug. ***
*** Bug 170386 has been marked as a duplicate of this bug. ***
*** Bug 172112 has been marked as a duplicate of this bug. ***