GNOME Bugzilla – Bug 156274
crash on resizing viewer window of damaged tiff file
Last modified: 2005-10-18 02:33:55 UTC
Distribution: Debian testing/unstable Package: EOG Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: the problem is with the tif file Bugzilla-Product: EOG Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: gimp gives out a slew of error messages when trying to open it. 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 1088015872 (LWP 4252)] [New Thread 1116654512 (LWP 4257)] [Thread debugging using libthread_db enabled] [New Thread 1088015872 (LWP 4252)] [New Thread 1116654512 (LWP 4257)] [Thread debugging using libthread_db enabled] [New Thread 1088015872 (LWP 4252)] [New Thread 1116654512 (LWP 4257)] (no debugging symbols found)...[New Thread 1107803056 (LWP 4255)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 51274
Thread 3 (Thread 1107803056 (LWP 4255))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-24 02:35 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "EOG". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was lists@mailry.net. 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.
Can you attach the tif file that causes the problem? (Note to self: probably a duplicate of bug 146474 via a few others, most notably bug 156273)
Created attachment 33559 [details] tif file the bug's subject/title should be: crash on resizing viewer window of damaged tiff file
Reopening, though for what it's worth I can't duplicate...
*** Bug 158641 has been marked as a duplicate of this bug. ***
*** Bug 159478 has been marked as a duplicate of this bug. ***
From bug 159478: I launched eog to rpeview a TIFF image that was beeing written too by another program. EOg crashed with the following message : (eog:30969): GLib-GObject-CRITICAL **: file gobject.c: line 1561 (g_object_ref): assertion `G_IS_OBJECT (object)' failed Eog-ERROR **: file eog-image.c: line 843 (real_image_load): assertion failed: (image != NULL) aborting... Failed to read a valid object file image from memory.
version of eog i am using is 2.9.1. I am also able to reproduce the crash if i rename a text file as .tif file. the error message i got at the terminal is: (eog:746): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Eog-ERROR **: file eog-image.c: line 843 (real_image_load): assertion failed: (image != NULL) Shall this be marked as duplicate of bug #155553.
*** Bug 300950 has been marked as a duplicate of this bug. ***
Duplicated in EOG 2.10.2, with a text file renamed to a .tif. Same error message as in comment 7. Stack trace is: Backtrace was generated from '/usr/bin/eog' Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1209763072 (LWP 2724)] [New Thread -1227461712 (LWP 2727)] [New Thread -1219069008 (LWP 2726)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 61909
Thread 3 (Thread -1219069008 (LWP 2726))
I cannot reproduce this bug with EOG 2.12.1. I can resize the window normaly when viewing the attached tiff image. There were several internal error handling improvements from 2.10.x to 2.12.x. So, this bug seems to be solved in EOG 2.12.x series.
*** This bug has been marked as a duplicate of 313397 ***