After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 300072 - Eye of Gnome quit unexpectedly while opening fiesta.xpm file in Archive Manager
Eye of Gnome quit unexpectedly while opening fiesta.xpm file in Archive Manager
Status: RESOLVED DUPLICATE of bug 313397
Product: eog
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 155553 171515 300560 301382 303725 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-10 11:29 UTC by Frido Roose
Modified: 2005-10-18 02:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
fiesta.xpm file causes crash of eog (302.90 KB, image/x-xpixmap)
2005-04-10 16:50 UTC, Frido Roose 		Details

Description Frido Roose 2005-04-10 11:29:12 UTC 
Distribution: Debian 3.1
Package: EOG
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Eye of Gnome quit unexpectedly while opening fiesta.xpm file in Archive Manager
Bugzilla-Product: EOG
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Eye of Gnome (or the Gimp) quits unexpectedly while opening fiesta.xpm
file in grub-splashboot package.

Steps to reproduce the crash:
1. Install grub-splashboot
2. Open fiesta.xpm (in Archive Manager or after extraction)
3. Eye Of Gnome crashes

Expected Results:
Image should be loaded instead of crashing, or in this case, with a
corrupted image file (doesn't load with the Gimp either), simple should
give an error of a corrupted file instead of crashing.

How often does this happen?
Always when opening the file

Additional Information:
fiesta.xpm is corrupted, Eye of Gnome doesn't handle this well


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 8038)]
[New Thread -1240839248 (LWP 8041)]
[New Thread -1232446544 (LWP 8040)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 57969

Thread 3 (Thread -1232446544 (LWP 8040))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 g_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-10 07:29 -------


Unknown version 2.10.0 in product EOG.  Setting version to "2.10.x".
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 frido@linux.be.
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.
Comment 1 Elijah Newren 2005-04-10 15:49:37 UTC 
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 or
attach the fiesta.xpm file that causes this crash?  (Please see
http://live.gnome.org/GettingTraces for more information on how to get a stack
trace with debugging symbols)
Comment 2 Frido Roose 2005-04-10 16:50:45 UTC 
Created attachment 45105 [details]
fiesta.xpm file causes crash of eog
Comment 3 Frido Roose 2005-04-10 16:54:03 UTC 
I'm not sure if this gdb output contains enough information (I installed
libglib2.0-0-dbg libgtk2.0-0-dbg libgnomevfs2-0-dbg).  You also can find the xpm
file attached.

gdb eog
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/eog
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 11918)]
[New Thread -1224090704 (LWP 11923)]
[New Thread -1232483408 (LWP 11924)]
[New Thread -1232856144 (LWP 11925)]
[New Thread -1241248848 (LWP 11926)]

(eog:11918): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (obj
ect)' failed

Eog-ERROR **: file eog-image.c: line 843 (real_image_load): assertion failed: (i
mage != NULL)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1241248848 (LWP 11926)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

+ Trace 57983

Thread 5 (Thread -1241248848 (LWP 11926))

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #2 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 IA__g_free
    at gmem.c line 187 






Comment 4


Elijah Newren





          2005-04-10 17:35:32 UTC
        



The stack trace isn't very useful, but the assertion may be and the image file
definitely is.  With that, I can reproduce.  Here's the stack trace that I get:

Backtrace was generated from '/opt/gnome2/bin/eog'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150600288 (LWP 32348)]
[New Thread 40127408 (LWP 32351)]
[Thread debugging using libthread_db enabled]
[New Thread -150600288 (LWP 32348)]
[New Thread 40127408 (LWP 32351)]
[Thread debugging using libthread_db enabled]
[New Thread -150600288 (LWP 32348)]
[New Thread 40127408 (LWP 32351)]
[New Thread 53238704 (LWP 32350)]
0x00424402 in ?? ()




+
Trace
    57985






Thread 3
          (Thread 53238704 (LWP 32350))


    

  • 
#0
??

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  741

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
??

    • 

  • 
#5
raise

    
                from
                /lib/tls/libc.so.6

    

    • 

  • 
#6
abort

    
                from
                /lib/tls/libc.so.6

    

    • 

  • 
#7
IA__g_logv

    • 

  • 
#8
IA__g_log

    • 

  • 
#9
IA__g_assert_warning

    
                at gmessages.c
                  line
                  547

    

    • 

  • 
#10
real_image_load

    
                at eog-image.c
                  line
                  843

    

    • 

  • 
#11
g_thread_create_proxy

    
                at gthread.c
                  line
                  561

    

    • 

  • 
#12
start_thread

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#13
clone

    
                from
                /lib/tls/libc.so.6

    

    • 













Comment 5


Elijah Newren





          2005-04-25 05:13:55 UTC
        



*** Bug 171515 has been marked as a duplicate of this bug. ***






Comment 6


Elijah Newren





          2005-05-11 01:42:01 UTC
        



*** Bug 301382 has been marked as a duplicate of this bug. ***






Comment 7


Elijah Newren





          2005-05-11 01:42:13 UTC
        



*** Bug 303725 has been marked as a duplicate of this bug. ***






Comment 8


Kjartan Maraas





          2005-06-22 20:03:45 UTC
        



*** Bug 300560 has been marked as a duplicate of this bug. ***






Comment 9


Christian Kirbach





          2005-07-14 18:56:33 UTC
        



*** Bug 155553 has been marked as a duplicate of this bug. ***






Comment 10


Lucas Rocha





          2005-10-16 02:15:30 UTC
        



I cannot reproduce this bug with EOG 2.12.1. 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.






Comment 11


Lucas Rocha





          2005-10-18 02:32:27 UTC
        




*** This bug has been marked as a duplicate of 313397 ***