[digikam] [Bug 377432] Crash on browsing images

2020-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Severity|normal  |crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #27 from caulier.gil...@gmail.com ---
[gilles@localhost digikam5]$ gdb --version
GNU gdb (GDB) 7.8.1-7.mga5 (Mageia release 5)
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
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-mageia-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #26 from wildcowboy  ---
(In reply to caulier.gilles from comment #25)
> I think it's a packaging problem. Here GDB is installed under Mageia6/5 and
> no crash... as expected.
> 
> Gilles Caulier

What version of GDB do you have?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #25 from caulier.gil...@gmail.com ---
I think it's a packaging problem. Here GDB is installed under Mageia6/5 and no
crash... as expected.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #24 from caulier.gil...@gmail.com ---
Interesting. As to your Linux team what's GDB install change in the system to
disable C++ exception handling at run time. Perhaps a bash variable is set ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #23 from wildcowboy  ---
I installed all the rest packages back and digiKam is not crashing still.
Looks like debugger it is. Weird...

To bad I actually moved to another Linux distribution because of this...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #22 from wildcowboy  ---
I deleted all packages one by one and digiKam stoped crashing only after I
deleted the debugger...

gdb (7.12.1-1)
gdb-common (7.12.1-1

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #21 from wildcowboy  ---
I think the problem is somewhere else. I was able to open the file after clean
OS install but I after I installed few packages it crashes again.
Here is the list of what I installed:


[2017-03-14 09:32] [ALPM] transaction completed
[2017-03-14 09:32] [ALPM] installed gdb (7.12.1-1)
[2017-03-14 09:32] [ALPM] installed gdb-common (7.12.1-1)
[2017-03-14 09:32] [ALPM] installed darktable (2:2.2.3-2)
[2017-03-14 09:32] [ALPM] installed osm-gps-map (1.1.0-3)
[2017-03-14 09:32] [ALPM] installed graphicsmagick (1.3.25-4)
[2017-03-14 09:32] [ALPM] installed colord-gtk (0.1.26+5+ga9d9c91-1)
[2017-03-14 09:32] [ALPM] installed flickcurl (1.26-2)
[2017-03-14 09:32] [ALPM] installed pugixml (1.8-1)
[2017-03-14 09:32] [ALPM] installed lensfun (0.3.2-3)
[2017-03-14 09:32] [ALPM] installed exiv2 (0.25-3)
[2017-03-14 09:32] [ALPM] installed rawtherapee (1:5.0.r1-1)
[2017-03-14 09:32] [ALPM] installed libiptcdata (1.0.4-3)
[2017-03-14 09:32] [ALPM] transaction started
[2017-03-14 09:06] [ALPM] running 'systemd-update.hook'...
[2017-03-14 09:06] [ALPM] transaction completed
[2017-03-14 09:06] [ALPM] installed perl-image-exiftool (10.40-1)
[2017-03-14 09:06] [ALPM] transaction started
[2017-03-14 09:06] [PACMAN] Running 'pacman -S perl-image-exiftool'
[2017-03-14 09:06] [PACMAN] Running 'pacman -S exiftool'
[2017-03-14 08:49] [PAMAC] synchronizing package lists
[2017-03-14 08:33] [ALPM] running 'systemd-update.hook'...
[2017-03-14 08:33] [ALPM] transaction completed
[2017-03-14 08:33] [ALPM] installed lib32-openal (1.17.2-1)
[2017-03-14 08:33] [ALPM] installed openal (1.17.2-2)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-14 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #20 from wildcowboy  ---
Looks like it keeps crashing on Manjaro too...

digikam.metaengine: Exiv2 ( 3 ) :  Directory PentaxDng with 26368 entries
considered invalid; not read.

[Switching to Thread 0x7fff04fe9700 (LWP 5271)]

Thread 62 "Thread (pooled)" hit Catchpoint 1 (exception thrown),
__cxxabiv1::__cxa_throw (obj=0x7fffbc0223a0, tinfo=0x761a0880 , 
dest=0x0)
at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:62
62  /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc: No such
file or directory.
(gdb) bt
#0  __cxxabiv1::__cxa_throw (obj=0x7fffbc0223a0, 
tinfo=0x761a0880 , dest=0x0)
at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:62
#1  0x75e85d3d in VerifyXPathRoot (expandedXPath=0x7fff04fe7970, 
propName=0x7fffbc022058 "prefix0:LocationCreated", 
schemaURI=0x7fffbc02d9b8 "http://iptc.org/std/Iptc4xmpExt/2008-02-29/;)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:203
#2  ExpandXPath (
schemaNS=0x7fffbc02d9b8 "http://iptc.org/std/Iptc4xmpExt/2008-02-29/;, 
propPath=, expandedXPath=expandedXPath@entry=0x7fff04fe7970)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:688
#3  0x75e8965c in GetNextXMPNode (info=...)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPIterator.cpp:335
#4  0x75e898dc in XMPIterator::Next (this=this@entry=0x7fffbc0340f0, 
schemaNS=schemaNS@entry=0x7fff04fe7ab0, 
nsSize=nsSize@entry=0x7fff04fe7ab8, 
propPath=propPath@entry=0x7fff04fe7ac0, 
pathSize=pathSize@entry=0x7fff04fe7ac8, 
propValue=propValue@entry=0x7fff04fe7ad0, valueSize=0x7fff04fe7ad8, 
propOptions=0x7fff04fe7c88)
---Type  to continue, or q  to quit---
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPIterator.cpp:630
#5  0x75e795ee in WXMPIterator_Next_1 (iterRef=0x7fffbc0340f0, 
schemaNS=, nsSize=0x7fff04fe7ab8, propPath=0x7fff04fe7ac0, 
pathSize=0x7fff04fe7ac8, propValue=0x7fff04fe7ad0, 
valueSize=, propOptions=0x7fff04fe7c88, 
wResult=0x7fff04fe7ae0)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/WXMPIterator.cpp:148
#6  0x75e6a647 in TXMPIterator::Next (
this=this@entry=0x7fff04fe7cd0, schemaNS=schemaNS@entry=0x7fff04fe7bf0, 
propPath=propPath@entry=0x7fff04fe7c00, 
propValue=propValue@entry=0x7fff04fe7c50, 
options=options@entry=0x7fff04fe7c88)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/include/client-glue/TXMPIterator.incl_cpp:208
#7  0x75e64777 in Exiv2::XmpParser::decode (xmpData=..., 
xmpPacket="\r\nhttp://www.w3.org/1999/02/22-rdf-syntax-ns#\;> to continue, or q  to quit---
#9  0x767f5126 in Digikam::MetaEngine::load (
this=this@entry=0x7fff04fe8870, filePath=...)
at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine.cpp:280
#10 0x7683da36 in Digikam::DMetadata::load (
this=this@entry=0x7fff04fe8870, filePath=...)
at /b/dktemp/digikam-master/core/libs/dmetadata/dmetadata.cpp:96
#11 0x7683dab2 in Digikam::DMetadata::DMetadata (this=0x7fff04fe8870, 
filePath=...)
at /b/dktemp/digikam-master/core/libs/dmetadata/dmetadata.cpp:63
#12 0x76882bd8 in Digikam::PreviewLoadingTask::loadImagePreview (
this=this@entry=0x3dd8910, sizeLimit=1366)
at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:589
#13 0x76883e09 in Digikam::PreviewLoadingTask::execute (this=0x3dd8910)
at /b/dktemp/digikam-master/core/libs/threadimageio/previewtask.cpp:309
#14 0x7686e482 in Digikam::LoadSaveThread::run (this=0xc54dd0)
at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133
#15 0x768ac50e in Digikam::DynamicThread::DynamicThreadPriv::run (
this=0xc54ec0)
at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183
#16 0x0031e02abf8d in ?? () from /tmp/.mount_PMks6X/usr/lib/libQt5Core.so.5
#17 0x0031e02aef49 in ?? () from /tmp/.mount_PMks6X/usr/lib/libQt5Core.so.5
#18 0x75a37454 in start_thread () from /usr/lib/libpthread.so.0
#19 0x7fffed8677df in clone () from /usr/lib/libc.so.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #19 from wildcowboy  ---
(In reply to caulier.gilles from comment #18)
> Yes you report to Mint team just to know the origin of the problem

Posted. https://bugs.launchpad.net/linuxmint/+bug/1672451

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #18 from caulier.gil...@gmail.com ---
Yes you report to Mint team just to know the origin of the problem

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #17 from wildcowboy  ---
(In reply to caulier.gilles from comment #16)
> The XMP packet in the image start with :
> 
> 
>  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;> rdf:about="uuid:faf5bdd5-ba3d-11da-ad31-d33d75182f1b"
> xmlns:xmp="http://ns.adobe.com/xap/1.0/;>Microsoft Photo
> Gallery 16.4.3528.331 rdf:about="uuid:faf5bdd5-ba3d-11da-ad31-d33d75182f1b"
> xmlns:prefix0="http://iptc.org/std/Iptc4xmpExt/2008-02-29/;> LocationCreated> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;> Description
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;> xmlns:prefix0="http://iptc.org/std/Iptc4xmpExt/2008-02-29/;>Canada CountryName> xmlns:prefix1="http://iptc.org/std/Iptc4xmpExt/2008-02-29/;>AB ProvinceState> xmlns:prefix2="http://iptc.org/std/Iptc4xmpExt/2008-02-29/;>Alberta City>
> 
> Exiv2 CLI tool said that a XMP namespace do not match.
> 
> Probably the XMP definition is not fully implemented in Exiv2. You can
> report this to Exiv2 team with the image attached for investiguation.
> 
> So now this file can be closed...
> 
> Gilles Caulier

Ubuntu dogs again? :) Should I report this as a Mint / Ubuntu bug anywhere or
that will be a waste of time anyways?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||5.6.0
 Resolution|UPSTREAM|FIXED

--- Comment #16 from caulier.gil...@gmail.com ---
The XMP packet in the image start with :


http://www.w3.org/1999/02/22-rdf-syntax-ns#;>http://ns.adobe.com/xap/1.0/;>Microsoft Photo
Gallery 16.4.3528.331http://iptc.org/std/Iptc4xmpExt/2008-02-29/;>http://www.w3.org/1999/02/22-rdf-syntax-ns#;>http://www.w3.org/1999/02/22-rdf-syntax-ns#;>http://iptc.org/std/Iptc4xmpExt/2008-02-29/;>Canadahttp://iptc.org/std/Iptc4xmpExt/2008-02-29/;>ABhttp://iptc.org/std/Iptc4xmpExt/2008-02-29/;>Alberta

Exiv2 CLI tool said that a XMP namespace do not match.

Probably the XMP definition is not fully implemented in Exiv2. You can report
this to Exiv2 team with the image attached for investiguation.

So now this file can be closed...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #15 from wildcowboy  ---
Also I am wondering what's wrong with the XMP data. This is just a picture from
my cell phone. I got thousands of these

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #14 from wildcowboy  ---
(In reply to caulier.gilles from comment #13)
> Just to be sure, i tested also with last 5.5.0 AppImage, and no crash :
> 
> digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Schema namespace
> URI and prefix mismatch
> 
> digikam.metaengine: Exiv2 ( 2 ) :  Failed to decode XMP metadata.
> 
> digikam.dimg: "/mnt/data/photos/20160911_132121.jpg"  : JPEG file identified
> 
> 
> The exception is here...
> 
> I suspect a big problem in your system, from low level libraries, as
> libc/libc++ which do not generate exceptions...
> 
> Can you test on another system to see if it's reproducible ?
> 
> Gilles Caulier

Just tested on Manjaro 17 Cinnamon and got the same result as yours. No crash.
Also I liked the Manjaro, so looks like you just caused me to jump to another
distro :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #13 from caulier.gil...@gmail.com ---
Just to be sure, i tested also with last 5.5.0 AppImage, and no crash :

digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Schema namespace URI
and prefix mismatch

digikam.metaengine: Exiv2 ( 2 ) :  Failed to decode XMP metadata.

digikam.dimg: "/mnt/data/photos/20160911_132121.jpg"  : JPEG file identified


The exception is here...

I suspect a big problem in your system, from low level libraries, as
libc/libc++ which do not generate exceptions...

Can you test on another system to see if it's reproducible ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #12 from caulier.gil...@gmail.com ---
Note  : i tried with digiKam to see if your image crash the application : no
dysfunction... The exception is generated on the console as expected.

So, i'm very curious to understand why it crash on your computer.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #11 from caulier.gil...@gmail.com ---
Ok,

I created a basic test CLI tool to read metadata from your image which crash
digiKam :

[gilles@localhost dmetadata]$ ./readfromimage 20160911_132121.jpg 
...
digikam.metaengine: Exiv2 ( 3 ) :  XMP Toolkit error 101: Schema namespace URI
and prefix mismatch

digikam.metaengine: Exiv2 ( 2 ) :  Failed to decode XMP metadata.

--- Comments   ---
digikam.general: Does not contain  "Comment"  Namespace
digikam.metaengine: Loading default values 
QMap()
--- Titles ---
QMap()
--- IPTC info  ---
IptcCoreContactInfo::city: "", IptcCoreContactInfo::country: "",
IptcCoreContactInfo::address: "", IptcCoreContactInfo::postalCode: "",
IptcCoreContactInfo::provinceState: "", IptcCoreContactInfo::email: "",
IptcCoreContactInfo::phone: "", IptcCoreContactInfo::webUrl: ""
IptcCoreLocationInfo::country: "", IptcCoreLocationInfo::countryCode: "",
IptcCoreLocationInfo::provinceState: "", IptcCoreLocationInfo::city: "",
IptcCoreLocationInfo::location: ""
()
--- Media info ---
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2016-09-11 13:21:21.000 CEST Qt::TimeSpec(LocalTime))
PhotoInfoContainer::make: "samsung", PhotoInfoContainer::model: "SM-G925W8",
PhotoInfoContainer::lens: "", PhotoInfoContainer::exposureTime: "1/386 s",
PhotoInfoContainer::exposureMode: "Auto", PhotoInfoContainer::exposureProgram:
"Auto", PhotoInfoContainer::aperture: "F1.9", PhotoInfoContainer::focalLength:
"4.3 mm", PhotoInfoContainer::focalLength35mm: "28.0 mm",
PhotoInfoContainer::sensitivity: "40"PhotoInfoContainer::flash: "No
flash"PhotoInfoContainer::whiteBalance: "Auto"PhotoInfoContainer::dateTime:
QDateTime(2016-09-11 13:21:21.000 CEST PhotoInfoContainer::aspectRatio: "",
PhotoInfoContainer::duration: "", PhotoInfoContainer::frameRate: "",
PhotoInfoContainer::videoCodec: "", PhotoInfoContainer::audioBitRate: "",
PhotoInfoContainer::audioChannelType: "", PhotoInfoContainer::audioCompressor:
"", 
--- XMP info   ---
()
()
()

It do not crash here but Exiv2 report an exception about XMP namespace.

Now, if i try to read XMP metadata with Exiv2 CLI tool i can see :

[gilles@localhost bin]$ ./exiv2 --version
exiv2 0.26 001900 (64 bit build)
Copyright (C) 2004-2017 Andreas Huggel.

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public
License along with this program; if not, write to the Free
Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
Boston, MA 02110-1301 USA

[gilles@localhost bin]$ exiv2 -px 20160911_132121.jpg 
Error: XMP Toolkit error 101: Schema namespace URI and prefix mismatch
Warning: Failed to decode XMP metadata.

So the same exception if generated. It do not crash.

Note : i tried with the official release Exiv2 0.25 and i see the same message.

Can you try on your computer with Exiv2 tool to see if the same error is
reproducible or if it crash ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #10 from wildcowboy  ---
(In reply to caulier.gilles from comment #9)
> Try to isolate the JPEG image file which introduce the dysfunction. It's a
> JPEG image as i can see on the backtrace.
> 
> After that, share the image on the cloud. I will try to reproduce the
> problem here.
> 
> Gilles Caulier

This one definitely causing the crash. I copied it to a different folder and
now digiKam crashes when trying to scan this folder.
https://drive.google.com/open?id=0B5_iknSPeSNBcGFZcUduTzJsZzQ

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #9 from caulier.gil...@gmail.com ---
Try to isolate the JPEG image file which introduce the dysfunction. It's a JPEG
image as i can see on the backtrace.

After that, share the image on the cloud. I will try to reproduce the problem
here.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #8 from wildcowboy  ---
3 folders... All 3 folders contain pictures from the same trip. There
pictures from two Samsung phones and Pentax K-S1 camera in there

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #7 from wildcowboy  ---
(In reply to caulier.gilles from comment #6)
> Yes, exactly, into XMP SDK from Adobe when a thumbnail of image must be
> created.
> 
> The crash appear always on the same image ?
> 
> Gilles Caulier

Right now it crashes when I open two particular folders.
It just happened again.
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
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 
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:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Catchpoint 1 (throw)
Starting program: /tmp/.mount_I0blN4/usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe78e2700 (LWP 4706)]
digikam.widgets: Breeze icons ressource file found
digikam.general: AlbumWatch use QFileSystemWatcher
[New Thread 0x7fffe5ffd700 (LWP 4707)]
[New Thread 0x7fffe57fc700 (LWP 4708)]
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/media/data/FamilyPictures/digikam4.db"
   DB Thumbs Name:   "/media/data/FamilyPictures/thumbnails-digikam.db"
   DB Face Name: "/media/data/FamilyPictures/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

[New Thread 0x7fffe4ffb700 (LWP 4709)]
[Thread 0x7fffe4ffb700 (LWP 4709) exited]
digikam.dbengine: Loading SQL code from config file
"/tmp/.mount_I0blN4/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/FamilyPictures"  uuid 
"volumeid:?uuid=e0deb5d0deb59eea"
digikam.database: location for  "/media/data/FamilyPictures"  is available 
true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8244797440
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  "Fusion"
digikam.dimg: ("/usr/share/color/icc", "/home/andrey/.local/share/icc")
[New Thread 0x7fffe4ffb700 (LWP 4715)]
digikam.general: Camera XML data: 
"/home/andrey/.local/share/digikam/cameras.xml"
[New Thread 0x7fffd5f9d700 (LWP 4716)]
[New Thread 0x7fffd579c700 (LWP 4717)]
[New Thread 0x7fffd4f9b700 (LWP 4718)]
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
[New Thread 0x7fffc3fff700 (LWP 4719)]
[New Thread 0x7fffc37fe700 (LWP 4720)]
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
[New Thread 0x7fffc2ffd700 (LWP 4721)]
[New Thread 0x7fffc27fc700 (LWP 4722)]
[New Thread 0x7fffc1ffb700 (LWP 4723)]
[New Thread 0x7fffc17fa700 (LWP 4724)]
[New Thread 0x7fffc0ff9700 (LWP 4725)]
digikam.facesengine: Face database ready for use
[New Thread 0x7fffa3fff700 (LWP 4726)]
[New Thread 0x7fffa37fe700 (LWP 4727)]
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
[New Thread 0x7fffa2ffd700 (LWP 4728)]
[New Thread 0x7fffa27fc700 (LWP 4729)]
[New Thread 0x7fffa1ffb700 (LWP 4730)]
[New Thread 0x7fffa17fa700 (LWP 4731)]
digikam.geoiface: "setting backend marble"
QtAV 1.11.0(Mar  9 2017, 11:27:18)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin, Shanghai, ChinaCopyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #6 from caulier.gil...@gmail.com ---
Yes, exactly, into XMP SDK from Adobe when a thumbnail of image must be
created.

The crash appear always on the same image ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-12 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #5 from wildcowboy  ---
One more crash. Looks like exiv2 again...

Thread 595 "Thread (pooled)" hit Catchpoint 1 (exception thrown),
0x7fffee0cc8bd in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x7fffee0cc8bd in __cxa_throw ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x75e7fd3d in VerifyXPathRoot (expandedXPath=0x7fff0dff96d0, 
propName=0x7fff14078818 "prefix0:LocationCreated", 
schemaURI=0x7fff1409bf18 "http://iptc.org/std/Iptc4xmpExt/2008-02-29/;)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:203
#2  ExpandXPath (
schemaNS=0x7fff1409bf18 "http://iptc.org/std/Iptc4xmpExt/2008-02-29/;, 
propPath=, expandedXPath=expandedXPath@entry=0x7fff0dff96d0)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:688
#3  0x75e8365c in GetNextXMPNode (info=...)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPIterator.cpp:335
#4  0x75e838dc in XMPIterator::Next (this=this@entry=0x7fff140690b0, 
schemaNS=schemaNS@entry=0x7fff0dff9810, 
nsSize=nsSize@entry=0x7fff0dff9818, 
propPath=propPath@entry=0x7fff0dff9820, 
pathSize=pathSize@entry=0x7fff0dff9828, 
propValue=propValue@entry=0x7fff0dff9830, valueSize=0x7fff0dff9838, 
propOptions=0x7fff0dff99e8)
---Type  to continue, or q  to quit---
0
#5  0x75e735ee in WXMPIterator_Next_1 (iterRef=0x7fff140690b0,
schemaNS=, nsSize=0x7fff0dff9818, propPath=0x7fff0dff9820, 
pathSize=0x7fff0dff9828, propValue=0x7fff0dff9830, valueSize=, propOptions=0x7fff0dff99e8, wResult=0x7fff0dff9840)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/WXMPIterator.cpp:148
#6  0x75e64647 in TXMPIterator::Next
(this=this@entry=0x7fff0dff9a30, schemaNS=schemaNS@entry=0x7fff0dff9950, 
propPath=propPath@entry=0x7fff0dff9960,
propValue=propValue@entry=0x7fff0dff99b0, options=options@entry=0x7fff0dff99e8)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/include/client-glue/TXMPIterator.incl_cpp:208
#7  0x75e5e777 in Exiv2::XmpParser::decode (xmpData=..., 
xmpPacket="\r\nhttp://www.w3.org/1999/02/22-rdf-syntax-ns#\;>, identifier=...)
at
/b/dktemp/digikam-master/core/libs/threadimageio/thumbnailcreator.cpp:197
#15 0x768929d0 in Digikam::ThumbnailLoadingTask::execute
(this=0xc613d0) at
/b/dktemp/digikam-master/core/libs/threadimageio/thumbnailtask.cpp:76
#16 0x7686b482 in Digikam::LoadSaveThread::run (this=0xb9ba50) at
/b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133
#17 0x768a950e in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0xb3db40) at
/b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183
#18 0x0031e02abf8d in ?? () from /tmp/.mount_z2eVTb/usr/lib/libQt5Core.so.5
#19 0x0031e02aef49 in ?? () from /tmp/.mount_z2eVTb/usr/lib/libQt5Core.so.5
#20 0x75a316ba in start_thread (arg=0x7fff0dffb700) at
pthread_create.c:333
#21 0x7fffed85d82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-09 Thread Simon
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #4 from Simon  ---
Thank you for all your reporting here and upstream on the exiv2 project!

On 10/03/17 07:14, wildcowboy wrote:
> https://bugs.kde.org/show_bug.cgi?id=377432
>
> --- Comment #3 from wildcowboy  ---
> (In reply to caulier.gilles from comment #1)
> Anyways, you might be correct. I have already had some issues with a metadata
> created by my Pentax K-S1 and exiv2 called via API by darktable.
> Posted. http://dev.exiv2.org/issues/1283
> Thanks for your help!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #3 from wildcowboy  ---
(In reply to caulier.gilles from comment #1)
> Again a crash in Exiv2.
> 
> Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax
> makernote tags parser is used. You can report this crash directly in Exiv2
> bugzilla. It's not a crash in digiKam as well.
> 
> Sound like your PEntax image are not well liked by Exiv2.
> 
> Try to identify the image file and report this problem to Exiv2 bugzilla as
> UPSTREAM.
> 
> Gilles Caulier

Anyways, you might be correct. I have already had some issues with a metadata
created by my Pentax K-S1 and exiv2 called via API by darktable.
Posted. http://dev.exiv2.org/issues/1283
Thanks for your help!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377432

--- Comment #2 from wildcowboy  ---
(In reply to caulier.gilles from comment #1)
> Again a crash in Exiv2.
> 
> Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax
> makernote tags parser is used. You can report this crash directly in Exiv2
> bugzilla. It's not a crash in digiKam as well.
> 
> Sound like your PEntax image are not well liked by Exiv2.
> 
> Try to identify the image file and report this problem to Exiv2 bugzilla as
> UPSTREAM.
> 
> Gilles Caulier

I see this:
---
#1  0x0032d2b81dda in Exiv2::Internal::PentaxMakerNote::printShutterCount (
os=..., value=..., metadata=)
at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/pentaxmn.cpp:1157
---
But how do I determine whether it caused the crash or not? If you did not tell
me I would never find out that "Exiv2 crash when Pentax makernote tags parser
is used."
What I am saying is it's not that clear when you don't have the knowledge. I am
learning though...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 377432] Crash on browsing images

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377432

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|AlbumsView  |Metadata-Engine
 Resolution|--- |UPSTREAM
 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---
Again a crash in Exiv2.

Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax
makernote tags parser is used. You can report this crash directly in Exiv2
bugzilla. It's not a crash in digiKam as well.

Sound like your PEntax image are not well liked by Exiv2.

Try to identify the image file and report this problem to Exiv2 bugzilla as
UPSTREAM.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.