GNOME Bugzilla – Bug 147706
ggv crashes when browsing through pages
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: GGV Severity: major Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: ggv crashes when browsing through pages Bugzilla-Product: GGV Bugzilla-Component: GGV Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: I moved to page 2 with the Space bar and ggv crashed. Steps to reproduce the crash: 1. Open http://dbpubs.stanford.edu/pub/showDoc.Fulltext?lang=en&doc=2003-16&format=pdf&compression= (or "Fulltext source: PDF"@ http://dbpubs.stanford.edu:8090/pub/2003-16) 2. Press Space to browse to page 2. 3. ggv crashes. Expected Results: How often does this happen? Using this document, every time. I haven't seen this bug with other documents yet. 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 -150458240 (LWP 3845)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00124402 in ?? ()
+ Trace 48624
Thread 1 (Thread -150458240 (LWP 3845))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-16 07:08 ------- 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 richard@hirner.at. 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.
See bug 145890
I believe this is really a duplicate of #139408: you are actually trying to activate the recent file drop down menu since that button has the focus. this was fixed in HEAD and in 2.6.1. *** This bug has been marked as a duplicate of 139408 ***