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 770215 - Crash after activating metadata writing to files
Crash after activating metadata writing to files
Status: RESOLVED DUPLICATE of bug 765963
Product: shotwell
Classification: Other
Component: editing
0.22.x
Other Linux
: Normal critical
: ---
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-08-21 22:31 UTC by Urbain
Modified: 2016-08-22 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Log file before crash. In debug mode, Shotwell hanged and I had to kill it. (5.15 KB, text/x-log)
2016-08-21 22:31 UTC, Urbain
Details

Description Urbain 2016-08-21 22:31:35 UTC
Created attachment 333853 [details]
Log file before crash. In debug mode, Shotwell hanged and I had to kill it.

Shotwell crashes a while after having activated the preference for writing metadata to files.

How can I get the information to identify the problem ?
How can I identify the file (and metadata) generating the crash ?

Here is the shotwell.gdb file :
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from shotwell...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/shotwell 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7a1e700 (LWP 26980)]
[New Thread 0x7fffe721d700 (LWP 26981)]
[New Thread 0x7fffe5ea5700 (LWP 26982)]
[New Thread 0x7fffcff04700 (LWP 26983)]
[New Thread 0x7fffcf703700 (LWP 26984)]
[New Thread 0x7fffcef02700 (LWP 26985)]
[New Thread 0x7fffce701700 (LWP 26986)]
[New Thread 0x7fffcd46d700 (LWP 26990)]
[New Thread 0x7fffccc6c700 (LWP 26991)]
[Thread 0x7fffccc6c700 (LWP 26991) exited]
[New Thread 0x7fffccc6c700 (LWP 26995)]
[Thread 0x7fffccc6c700 (LWP 26995) exited]
[New Thread 0x7fffccc6c700 (LWP 26996)]
[Thread 0x7fffccc6c700 (LWP 26996) exited]
[New Thread 0x7fffccc6c700 (LWP 26997)]
[New Thread 0x7fffc76f0700 (LWP 26998)]
[New Thread 0x7fffc6eef700 (LWP 26999)]
[New Thread 0x7fffc66ee700 (LWP 27000)]
[New Thread 0x7fffc5eed700 (LWP 27001)]
[New Thread 0x7fffc56ec700 (LWP 27002)]
[New Thread 0x7fffc4c91700 (LWP 27003)]
[New Thread 0x7fff9bbd1700 (LWP 27004)]
[Thread 0x7fff9bbd1700 (LWP 27004) exited]
[Thread 0x7fffcd46d700 (LWP 26990) exited]
[Thread 0x7fffc5eed700 (LWP 27001) exited]
[Thread 0x7fffccc6c700 (LWP 26997) exited]
[Thread 0x7fffc66ee700 (LWP 27000) exited]
[Thread 0x7fffc56ec700 (LWP 27002) exited]
[Thread 0x7fffc6eef700 (LWP 26999) exited]
[Thread 0x7fffc76f0700 (LWP 26998) exited]
[New Thread 0x7fffc76f0700 (LWP 27035)]
[New Thread 0x7fffc6eef700 (LWP 27036)]
[Thread 0x7fffc6eef700 (LWP 27036) exited]
[Thread 0x7fffc76f0700 (LWP 27035) exited]
[New Thread 0x7fffc76f0700 (LWP 27215)]
[New Thread 0x7fffc6eef700 (LWP 27216)]
[New Thread 0x7fffc56ec700 (LWP 27217)]
[New Thread 0x7fffc66ee700 (LWP 27218)]
[New Thread 0x7fffcd46d700 (LWP 27219)]
[New Thread 0x7fffccc6c700 (LWP 27224)]
[New Thread 0x7fffc5eed700 (LWP 27227)]
[New Thread 0x7fff9bbd1700 (LWP 27228)]
[New Thread 0x7fff9b3d0700 (LWP 27229)]
[Thread 0x7fffc66ee700 (LWP 27218) exited]
[Thread 0x7fffc4c91700 (LWP 27003) exited]
[Thread 0x7fff9b3d0700 (LWP 27229) exited]
[Thread 0x7fffc76f0700 (LWP 27215) exited]
[Thread 0x7fffc6eef700 (LWP 27216) exited]
[Thread 0x7fffc56ec700 (LWP 27217) exited]
[Thread 0x7fffcd46d700 (LWP 27219) exited]
[Thread 0x7fffccc6c700 (LWP 27224) exited]
[Thread 0x7fff9bbd1700 (LWP 27228) exited]
[New Thread 0x7fff9bbd1700 (LWP 27710)]
L 26973 2016-08-21 23:58:24 [CRT] Directory Sony2 with 20307 entries considered invalid; not read.

shotwell: tiffcomposite.cpp :749 : virtual Exiv2::Internal::TiffComponent* Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, Exiv2::Internal::TiffPath&, Exiv2::Internal::TiffComponent*, Exiv2::Internal::TiffComponent::AutoPtr):  l'assertion « mn_ » a échoué.

Thread 29 "pool" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffc5eed700 (LWP 27227)]
0x00007ffff3939418 in __GI_raise (sig=sig@entry=6)
    at ../sysdeps/unix/sysv/linux/raise.c:54
54	../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type.
(gdb)
Comment 1 Urbain 2016-08-21 22:39:59 UTC
The *.jpg files being written before the crash are associated with *.jpg.xmp files. I don't know if there is any relation to the crash.

Thanks for your advices.
Urbain
Comment 2 Jens Georg 2016-08-22 12:20:44 UTC
Hi, this is a known bug in exiv2 which was missing some implementation there.

It is fixed in the debian package and in the package available in the shotwell ppa.

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