GNOME Bugzilla – Bug 145893
eog crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: EOG Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: eog crash Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: No idea what happened, sorry. I'm running a fresh install of Fedora Core 2. Debugging Information: Backtrace was generated from '/usr/bin/eog' (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 -150842720 (LWP 22515)] [New Thread 15051696 (LWP 22517)] [Thread debugging using libthread_db enabled] [New Thread -150842720 (LWP 22515)] [New Thread 15051696 (LWP 22517)] [New Thread 26794928 (LWP 22516)] (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -150842720 (LWP 22515)] [New Thread 15051696 (LWP 22517)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00f6d402 in ?? ()
+ Trace 47543
Thread 3 (Thread 26794928 (LWP 22516))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 16:58 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "EOG". Setting to default milestone for this product, '---' 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.
But you can certainly tell us what you did. Did you just start eog and it crashed? Otherwise it's hard to reproduce it and nearly impossible to fix it.
I'm aware of the lack of information, maybe I would have known more 2004-05-19 when I reported this bug via the bug-buddy. It's a pity it did not enter Bugzilla until yesterday... :-( Maybe this is not an eog-specific bug? Take a look at these bugs and the bugs their duplicates: bug 146075 bug 146564 They all have this backtrace in common:
+ Trace 48415
Never mind bug 146564, sorry for the confusion. Maybe just resolve this bug as a duplicate of bug 146075?
David: Good catch, thanks.
*** This bug has been marked as a duplicate of 146075 ***