Bug 641058 – crash in gThumb: rotating blocks of 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 641058 - crash in gThumb: rotating blocks of image...


Summary:	crash in gThumb: rotating blocks of image...


Status:	RESOLVED DUPLICATE of bug 640268

Product:	gthumb
Classification:	Other
Component:	general
Version:	2.11.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-01-31 17:42 UTC by harroun
Modified:	2011-01-31 17:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description harroun 2011-01-31 17:42:39 UTC

Version: 2.11.5

What were you doing when the application crashed?
rotating blocks of images first left, then right, in order to get regenerated thumbnails..  did it to maybe 10 or so groups, then suddenly it didn't like it anymore :(


Distribution: Debian 6.0
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-amd64 #1 SMP Wed Jan 12 05:14:59 UTC 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 238989312 vsize: 238989312 resident: 127209472 share: 17235968 rss: 127209472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1296494227 rtime: 16509 utime: 15115 stime: 1394 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xee7feb70 (LWP 26706)]
[New Thread 0xf16fbb70 (LWP 24467)]
[New Thread 0xf283eb70 (LWP 24464)]
[New Thread 0xf28bfb70 (LWP 24463)]
[New Thread 0xf2940b70 (LWP 24462)]
[New Thread 0xf29c1b70 (LWP 24461)]
[New Thread 0xf2a59b70 (LWP 24460)]
0xf77c4425 in __kernel_vsyscall ()

+ Trace 225785

Thread 1 (Thread 0xf615a730 (LWP 24459))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ??
from /usr/lib/libexiv2.so.9
#11 ??
from /usr/lib/libexiv2.so.9
#12 ??
from /usr/lib/libexiv2.so.9
#13 ??
from /usr/lib/libexiv2.so.9
#14 ??
from /usr/lib/libexiv2.so.9
#15 ??
from /usr/lib/libexiv2.so.9
#16 ??
from /usr/lib/libexiv2.so.9
#17 ??
from /usr/lib/libexiv2.so.9
#18 ??
from /usr/lib/libexiv2.so.9
#19 ??
from /usr/lib/libexiv2.so.9
#20 ??
from /usr/lib/libexiv2.so.9
#21 ??
from /usr/lib/libexiv2.so.9
#22 ??
from /usr/lib/libexiv2.so.9
#23 ??
from /usr/lib/libexiv2.so.9
#24 Exiv2::ExifParser::encode(std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned char const*, unsigned int, Exiv2::ByteOrder, Exiv2::ExifData const&)
from /usr/lib/libexiv2.so.9
#25 ??
from /usr/lib/libexiv2.so.9
#26 Exiv2::JpegBase::writeMetadata()
from /usr/lib/libexiv2.so.9
#27 ??
from /usr/lib/gthumb/extensions/libexiv2_tools.so
#28 exiv2_write_metadata_to_buffer
from /usr/lib/gthumb/extensions/libexiv2_tools.so
#29 ??
from /usr/lib/gthumb/extensions/libexiv2_tools.so
#30 ??
#31 g_hook_list_marshal
from /lib/libglib-2.0.so.0
#32 gth_hook_invoke
#33 jpegtran
from /usr/lib/gthumb/extensions/libjpeg_utils.so
#34 ??
from /usr/lib/gthumb/extensions/libimage_rotation.so
#35 ??
#36 ??
from /usr/lib/libgio-2.0.so.0
#37 g_simple_async_result_complete
from /usr/lib/libgio-2.0.so.0
#38 ??
from /usr/lib/libgio-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#41 ??
from /lib/libglib-2.0.so.0
#42 g_main_loop_run
from /lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 main

A debugging session is active.

	Inferior 1 [process 24459] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (7 sec old) ---------------------
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
Error: Directory Canon with 3584 entries considered invalid; not read.
gthumb: tiffcomposite.cpp:1299: virtual uint32_t Exiv2::Internal::TiffDirectory::doWrite(Exiv2::Internal::IoWrapper&, Exiv2::ByteOrder, int32_t, uint32_t, uint32_t, uint32_t&): Assertion `sv == d' fai
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2011-01-31 17:54:03 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

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


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