Bug 640268 – crash after crop + save

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 640268 - crash after crop + save


Summary:	crash after crop + save


Status:	RESOLVED NOTGNOME

Product:	gthumb
Classification:	Other
Component:	general
Version:	2.12.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Duplicates:	614265 625699 630554 637434 640663 641058 641311 642622 647951 648418 649022 (view as bug list)
Depends on:
Blocks:

Reported:	2011-01-22 16:30 UTC by Michael Chudobiak
Modified:	2011-04-30 19:19 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Stack trace (10.67 KB, text/plain) 2011-04-30 19:03 UTC, Martin Barry	Details

Description Michael Chudobiak 2011-01-22 16:30:24 UTC

The crop was successful, but the save crashed. Using git master.

A repeat operation worked fine. Which is odd.

- Mike


[New Thread 18707]
[New Thread 18708]
[New Thread 18714]
[New Thread 18891]
Core was generated by `gthumb --import-photos /home/mjc/.gvfs/gphoto2 mount on usb%3A001,009'.
Program terminated with signal 6, Aborted.

+ Trace 225648

Thread 1 (Thread 18707)

#0 raise
from /lib64/libc.so.6
#1 abort
from /lib64/libc.so.6
#2 __assert_fail
from /lib64/libc.so.6
#3 Exiv2::Internal::TiffDirectory::doWrite
at tiffcomposite.cpp line 1299
#4 Exiv2::Internal::TiffIfdMakernote::doWrite
at tiffcomposite.cpp line 1505
#5 Exiv2::Internal::TiffDirectory::doWrite
at tiffcomposite.cpp line 1298
#6 Exiv2::Internal::TiffSubIfd::doWriteData
at tiffcomposite.cpp line 1656
#7 Exiv2::Internal::TiffDirectory::doWriteData
at tiffcomposite.cpp line 1603
#8 Exiv2::Internal::TiffDirectory::doWrite
at tiffcomposite.cpp line 1315
#9 Exiv2::Internal::TiffParserWorker::encode
#10 Exiv2::ExifParser::encode
at exif.cpp line 722
#11 Exiv2::JpegBase::doWriteMetadata
at jpgimage.cpp line 674
#12 Exiv2::JpegBase::writeMetadata
at jpgimage.cpp line 499
#13 exiv2_write_metadata_private
at exiv2-utils.cpp line 1023
#14 exiv2_write_metadata
at exiv2-utils.cpp line 1057
#15 g_hook_list_marshal
at ghook.c line 387
#16 gth_hook_invoke
at gth-hook.c line 269
#17 _gdk_pixbuf_save_async
at pixbuf-io.c line 204
#18 g_closure_invoke
at gclosure.c line 766
#19 signal_emit_unlocked_R
at gsignal.c line 3252
#20 g_signal_emit_valist
at gsignal.c line 2983
#21 g_signal_emit
at gsignal.c line 3040
#22 gtk_real_button_released
at gtkbutton.c line 1725
#23 g_closure_invoke
at gclosure.c line 766
#24 signal_emit_unlocked_R
at gsignal.c line 3182
#25 g_signal_emit_valist
at gsignal.c line 2983
#26 g_signal_emit
at gsignal.c line 3040
#27 gtk_button_button_release
at gtkbutton.c line 1617
#28 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 86
#29 g_closure_invoke
at gclosure.c line 766
#30 signal_emit_unlocked_R
at gsignal.c line 3290
#31 g_signal_emit_valist
at gsignal.c line 2993
#32 g_signal_emit
at gsignal.c line 3040
#33 gtk_widget_event_internal
at gtkwidget.c line 4992
#34 IA__gtk_propagate_event
at gtkmain.c line 2460
#35 IA__gtk_main_do_event
at gtkmain.c line 1665
#36 gdk_event_dispatch
at gdkevents-x11.c line 2377
#37 g_main_dispatch
at gmain.c line 2149
#38 g_main_context_dispatch
at gmain.c line 2702
#39 g_main_context_iterate
at gmain.c line 2780
#40 g_main_loop_run
at gmain.c line 2988
#41 IA__gtk_main
at gtkmain.c line 1237
#42 main
at main.c line 449

Comment 1 Michael Chudobiak 2011-01-26 19:14:54 UTC

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

Comment 2 Michael Chudobiak 2011-01-26 19:15:03 UTC

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

Comment 3 Michael Chudobiak 2011-01-26 19:15:55 UTC

Crashes at:

assert(sv == d);

in eviv2's src/tiffcomposite.cpp:TiffDirectory::doWrite

- Mike

Comment 4 Michael Chudobiak 2011-01-27 13:05:35 UTC

Probably related to this exiv2 bug report:

http://dev.exiv2.org/issues/752

- Mike

Comment 5 Michael Chudobiak 2011-01-27 13:09:43 UTC

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

Comment 6 Michael Chudobiak 2011-01-27 13:16:43 UTC

Some exiv2 discussion:

http://dev.exiv2.org/boards/3/topics/779

Comment 7 Michael Chudobiak 2011-01-27 15:00:07 UTC

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

Comment 8 Michael Chudobiak 2011-01-31 17:57:41 UTC

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

Comment 9 Michael Chudobiak 2011-02-01 16:00:06 UTC

Should be fixed in the next release(s) of exiv2.

http://dev.exiv2.org/issues/752

- Mike

Comment 10 Michael Chudobiak 2011-02-03 13:14:10 UTC

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

Comment 11 Michael Chudobiak 2011-02-13 14:41:26 UTC

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

Comment 12 Michael Chudobiak 2011-02-13 14:43:17 UTC

exiv2 has patches for this issue for 0.20.x and 0.21.x, but distros need to pick up the patch.

On Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=628182

I emailed the Debian exiv2 maintainer about the issue, but didn't hear back.

This affect Shotwell too.

- Mike

Comment 13 Akhil Laddha 2011-02-18 00:58:04 UTC

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

Comment 14 Michael Chudobiak 2011-04-17 12:16:04 UTC

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

Comment 15 Michael Chudobiak 2011-04-21 19:31:50 UTC

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

Comment 16 Michael Chudobiak 2011-04-30 16:04:20 UTC

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

Comment 17 Martin Barry 2011-04-30 19:03:49 UTC

Created attachment 186947 [details]
Stack trace

As requested in 649022 before it was made a duplicate of this bug.

Versions:
- gThumb 2.13.1
- exiv2 0.21.1
- libexiv2 0.21.1

Comment 18 Michael Chudobiak 2011-04-30 19:19:44 UTC

If it crashes with exiv2 0.21.1, then it is exiv2 bug 769 (http://dev.exiv2.org/issues/769).

- Mike