GNOME Bugzilla – Bug 170386
crashes when I hitting space bar immediately after opening document
Last modified: 2005-03-14 21:01:41 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: GGV Severity: normal Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: crashes when I hitting space bar immediately after opening document Bugzilla-Product: GGV Bugzilla-Component: GGV Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: The application crashes if I hit the space bar immediately after opening a document from a bash shell. Steps to reproduce the crash: 1. type ggv <filename>.ps in a command terminal 2. hit space bar 3. Expected Results: I expected it to scroll down the page. How often does this happen? Only occurs immediately after opening document. If move the page with the mouse and then hit the space bar, the behaviour is normal. 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 -150196096 (LWP 5790)] [New Thread 26209200 (LWP 5791)] [Thread debugging using libthread_db enabled] [New Thread -150196096 (LWP 5790)] [New Thread 26209200 (LWP 5791)] [Thread debugging using libthread_db enabled] [New Thread -150196096 (LWP 5790)] [New Thread 26209200 (LWP 5791)] (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)...0x0028c402 in ?? ()
+ Trace 56876
Thread 1 (Thread -150196096 (LWP 5790))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-14 15:56 ------- 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 paul.milliken@gmail.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.
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. Matches the stack trace in bug 159962, which has been marked as a duplicate of 154193. *** This bug has been marked as a duplicate of 154193 ***