GNOME Bugzilla – Bug 324817
bug report
Last modified: 2005-12-28 20:17:15 UTC
From: Mike <spydertechnologiez@cox.net> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Fitting image in image viewer Date: Wed, 21 Dec 2005 21:52:49 -0600 Message-Id: <1135223569.9650.1.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Distribution: Ubuntu 5.10 (breezy) Package: EOG Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: Fitting image in image viewer Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: app stopped when tried to press fit button Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 -1224017472 (LWP 9567)] [New Thread -1237677136 (LWP 9569)] [New Thread -1225659472 (LWP 9568)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 __kernel_vsyscall ()
+ Trace 64761
Thread 2 (Thread -1237677136 (LWP 9569))
------- Bug created by bug-buddy at 2005-12-22 15:54 ------- Unknown version 2.12.1 in product EOG. Setting version to "2.12.x".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
alfredoj69: It's correct that the stack trace isn't helpful enough to debug the problem, but it turns out that it is enough to determine that it's a duplicate, and the simple-dup-finder can help you find it. :) Reporter: 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. According to the comments in bug 311925, it appears that this problem should be fixed in EOG >= 2.12.2. *** This bug has been marked as a duplicate of 311925 ***