GNOME Bugzilla – Bug 318867
Crash after load screen.png
Last modified: 2005-11-25 21:46:54 UTC
Distribution: Ubuntu 5.10 (breezy) Package: EOG Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: Crash after load screen.png Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Steps to reproduce the crash: load screen.png 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 -1224382784 (LWP 9234)] [New Thread -1239929936 (LWP 9236)] [New Thread -1226695760 (LWP 9235)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 63538
Thread 2 (Thread -1239929936 (LWP 9236))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-14 14:22 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 p21@gmx.net.
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. Also, could you attach here the problematic image (screen.png)?
Created attachment 53483 [details] crash pic
I cannot reproduce this bug with EOG 2.12.1. Are still having this problem? Can you get us a stack trace with debugging symbols?
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 ***