Bug 466141 – crash in gThumb Image Viewer: Saving a cropped image

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 466141 - crash in gThumb Image Viewer: Saving a cropped image


Summary:	crash in gThumb Image Viewer: Saving a cropped image


Status:	RESOLVED DUPLICATE of bug 391004

Product:	gthumb
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-13 06:02 UTC by Robert F. Chapman
Modified:	2007-08-13 12:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Robert F. Chapman 2007-08-13 06:02:25 UTC

What were you doing when the application crashed?
Saving a cropped image 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 1421312000 vsize: 1421312000 resident: 1357705216 share: 26284032 rss: 1357705216 rss_rlim: 4294967295
CPU usage: start_time: 1186982962 rtime: 2006 utime: 1843 stime: 163 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208453408 (LWP 8548)]
[New Thread -1260344432 (LWP 8561)]
[New Thread -1259816048 (LWP 8560)]
[New Thread -1259287664 (LWP 8559)]
[New Thread -1237779568 (LWP 8556)]
[New Thread -1237251184 (LWP 8555)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 154799

Thread 1 (Thread -1208453408 (LWP 8548))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 exif_set_sshort
from /usr/lib/libexif.so.12
#5 exif_set_short
from /usr/lib/libexif.so.12
#6 ??
from /usr/lib/libexif.so.12
#7 ??
from /usr/lib/libexif.so.12
#8 exif_data_save_data
from /usr/lib/libexif.so.12
#9 jpeg_data_save_data
#10 jpeg_data_save_file
#11 ??
#12 ??
from /usr/lib/gthumb/libgthumb.so
#13 ??
#14 gth_window_activate_action_file_save
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /lib/libgobject-2.0.so.0
#24 ??
from /lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 ??
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit
from /lib/libgobject-2.0.so.0
#33 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#40 g_signal_emit
from /lib/libgobject-2.0.so.0
#41 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /lib/libgobject-2.0.so.0
#45 g_closure_invoke
from /lib/libgobject-2.0.so.0
#46 ??
from /lib/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#48 g_signal_emit
from /lib/libgobject-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#51 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgdk-x11-2.0.so.0
#53 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#54 ??
from /lib/libglib-2.0.so.0
#55 g_main_loop_run
from /lib/libglib-2.0.so.0
#56 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#57 main
#0 __kernel_vsyscall



----------- .xsession-errors (24404 sec old) ---------------------
Selected video codec: [ffdivx] vfm: ffmpeg (FFmpeg DivX ;-) (MS MPEG-4 v3))
==========================================================================
==========================================================================
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 12000 Hz, 1 ch, u8, 96.0 kbit/100.00% (ratio: 12000->12000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
AO: [alsa] 48000Hz 1ch u8 (1 bytes per sample)
Starting playback...
VDec: vo config request - 352 x 240 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 352x240 => 352x240 Planar YV12 
A:   0.0 V:   0.0 A-V:  0.048 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.001 ct:  0.000   2/  2 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.001 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Michael Chudobiak 2007-08-13 12:16:38 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 391004 ***