GNOME Bugzilla – Bug 305886
EOG crashes when viewing corrupt png files
Last modified: 2005-10-24 21:51:25 UTC
Distribution: Debian 3.1 Package: EOG Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: EOG crashes when viewing corrup png files Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: EOG crashes when viewing corrup png files Steps to reproduce the crash: 1. Take a corrupt PNG file, probably some png file which has been checked into CVS as a text file instead of binary file 2. Open it in EOG 3. Expected Results: How often does this happen? Always 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) [Thread debugging using libthread_db enabled] [New Thread -1221735776 (LWP 10310)] [New Thread -1241039952 (LWP 10314)] [New Thread -1232319568 (LWP 10312)] [New Thread -1223926864 (LWP 10311)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 60328
Thread 4 (Thread -1223926864 (LWP 10311))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-30 02:27 UTC ------- Unknown version 2.10.0 in product EOG. Setting version to "2.10.x".
can you attach a such file to the bug?
This kind of bug (crash when trying to open a corrupted image file) is fixed in 2.12.x series and HEAD. Marking as a duplicate of bug #313397. Feel free to reopen this bug if you experience this problem in the latest versions of EOG. *** This bug has been marked as a duplicate of 313397 ***