GNOME Bugzilla – Bug 160054
GGV crashes when space bar is hit.
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: GGV Severity: major Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: GGV crashes when space bar is hit. Bugzilla-Product: GGV Bugzilla-Component: GGV Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: GGV crashes when space bar is hit. Steps to reproduce the crash: 1. Open a pdf. 2. Hit space bar to advance to the next frame. 3. Expect chaos to ensue. Expected Results: GGV crashes. How often does this happen? Every time. Additional Information: I guess this is not high priority, but for users who don't use a mouse, it's much easier to hit space bar (like xpdf). 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 -1223139200 (LWP 3959)] [New Thread -1225794640 (LWP 3960)] [Thread debugging using libthread_db enabled] [New Thread -1223139200 (LWP 3959)] [New Thread -1225794640 (LWP 3960)] (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1223139200 (LWP 3959)] [New Thread -1225794640 (LWP 3960)] (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)...0xffffe410 in ?? ()
+ Trace 52988
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-01 00:10 ------- 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 damian@cs.utexas.edu. 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. 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 154193 ***