Bug 417947 – crash in Image Viewer: saving a gif image with ...

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 417947 - crash in Image Viewer: saving a gif image with ...


Summary:	crash in Image Viewer: saving a gif image with ...


Status:	RESOLVED DUPLICATE of bug 367788

Product:	eog
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Duplicates:	427894 428448 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-13 18:27 UTC by iradigales
Modified:	2007-04-11 16:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description iradigales 2007-03-13 18:27:38 UTC

Version: 2.16.1

What were you doing when the application crashed?
saving a gif image with the extension png


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 116776960 vsize: 0 resident: 116776960 share: 0 rss: 17809408 rss_rlim: 0
CPU usage: start_time: 1173810394 rtime: 0 utime: 144 stime: 0 cutime:136 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1226364736 (LWP 7934)]
[New Thread -1286526048 (LWP 7936)]
[New Thread -1228633184 (LWP 7935)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 118344

Thread 1 (Thread -1226364736 (LWP 7934))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_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 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gdk_region_get_rectangles
from /usr/lib/libgdk-x11-2.0.so.0
#11 gdk_region_get_rectangles
from /usr/lib/libgdk-x11-2.0.so.0
#12 gdk_region_union
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_window_invalidate_maybe_recurse
from /usr/lib/libgdk-x11-2.0.so.0
#14 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_frame_new
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_hbox_new
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#26 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_vbox_new
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#34 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#39 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_vbox_new
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#42 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#44 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#47 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#48 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#49 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#50 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#51 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#54 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#55 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_container_resize_children
from /usr/lib/libgtk-x11-2.0.so.0
#57 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#58 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#59 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#60 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#61 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#62 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#63 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#64 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#65 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#66 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#67 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#68 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#69 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#70 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#71 main
#0 __kernel_vsyscall

Comment 1 Felix Riemann 2007-03-13 19:39:16 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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

Comment 2 palfrey 2007-04-09 21:24:20 UTC

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

Comment 3 palfrey 2007-04-11 16:15:27 UTC

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