GNOME Bugzilla – Bug 322454
Crash after folder full of images was opened
Last modified: 2005-11-25 21:46:13 UTC
Distribution: Ubuntu 5.10 (breezy) Package: EOG Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: Crash after folder full of images was opened Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Opened a folder containing about 70 jpeg pictures (2Mb average size) and as soon as the first image displayed, the program crashed. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? This is the first time I used eog on a fresh install of Ubuntu 5.10. 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 -1224111680 (LWP 11138)] [New Thread -1250616400 (LWP 11155)] [New Thread -1227457616 (LWP 11154)] [New Thread -1227191376 (LWP 11149)] [New Thread -1226597456 (LWP 11148)] [New Thread -1226331216 (LWP 11147)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 64265
Thread 2 (Thread -1250616400 (LWP 11155))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-25 18:08 UTC ------- Unknown version 2.12.1 in product EOG. Setting version to "2.12.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was gburca-bugbuddy@ebixio.com.
Thanks for reporting. This should be fixed in Gnome 2.12.2 (and newer releases). If not, please reopen Bug #311925 *** This bug has been marked as a duplicate of 311925 ***