[digikam] [Bug 329091] New: Maintenance MYSQL leads to crash digikam

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #14 from [hidden email] ---
That's it: max-allowed-packet was 4096. I set it to 16.777.216 ->
facerecognition works first time ever :-))

But some error messages are still on:

digikam.general: Allowing a cache size of 200 MB
digikam.dbengine: Prepare failed!
digikam.dbengine: Failure executing query:
 "SELECT value FROM ThumbSettings WHERE keyword=?;"
Error messages: "QMYSQL3: Unable to prepare statement" "Table
'digikam.ThumbSettings' doesn't exist" 1146 2
Bound values:  ()
digikam.dbengine: Failure executing query:
 "SELECT value FROM ThumbSettings WHERE keyword='DBThumbnailsVersion';"
Error messages: "QMYSQL: Unable to execute query" "Table
'digikam.ThumbSettings' doesn't exist" 1146 2
Bound values:  (QVariant(QString, "DBThumbnailsVersion"))
digikam.dbengine: Error while executing DBAction [ "SelectThumbnailSetting" ]
Statement [ "SELECT value FROM ThumbSettings WHERE keyword=:keyword;" ]
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  1
digikam.dbengine: Prepare failed!
digikam.dbengine: Failure executing query:
 "SELECT value FROM ThumbSettings WHERE keyword=?;"
Error messages: "QMYSQL3: Unable to prepare statement" "Table
'digikam.ThumbSettings' doesn't exist" 1146 2
Bound values:  ()
digikam.dbengine: Failure executing query:
 "SELECT value FROM ThumbSettings WHERE keyword='DBThumbnailsVersionRequired';"
Error messages: "QMYSQL: Unable to execute query" "Table
'digikam.ThumbSettings' doesn't exist" 1146 2
Bound values:  (QVariant(QString, "DBThumbnailsVersionRequired"))
digikam.dbengine: Error while executing DBAction [ "SelectThumbnailSetting" ]
Statement [ "SELECT value FROM ThumbSettings WHERE keyword=:keyword;" ]

How can I fix this? Can I set up the tables via phpmyadmin? Is there a doku for
the db-structure? And how can I fill this hand made tables?

I will test the other functions of maintenance separatly an give feedback....

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #15 from [hidden email] ---
I couldn't solve all of the above mentioned problems:

1 - done
2 - no language pack l18n for digikam in Gentoo??
3 - Breeze icons are installed now, but some icons miss in digikam
4 - same

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #16 from [hidden email] ---
>That's it: max-allowed-packet was 4096. I set it to 16.777.216 -> facerecognition works first >time ever :-))

Where do you tune this settings exactly ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #17 from [hidden email] ---
>How can I fix this? Can I set up the tables via phpmyadmin? Is there a doku for the db->structure? And how can I fill this hand made tables?

The errors come from Thumbnail database which can be broken due to previous
crash. This database only contain wavelets compressed thumbs. You can drop it
and recreate the database in mysql as at init. The database contents will be
recreated automatically.

Gilles  Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #18 from [hidden email] ---
> no language pack l18n for digikam in Gentoo??

No idea. No Gentoo here.

At least, digiKam is released with whole translations pack. After, each
packager make packages following distro rules...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #19 from [hidden email] ---
(In reply to caulier.gilles from comment #16)
> >That's it: max-allowed-packet was 4096. I set it to 16.777.216 -> facerecognition works first >time ever :-))
>
> Where do you tune this settings exactly ?
>
> Gilles Caulier

in mariadb via phpmyadmin. (settings - max-allowed-packets) works fine.

maintenance thumbnails & fingerprints work - now testing duplicates....

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #20 from [hidden email] ---
I have finished  testing the maintenance modules:

- searching duplicates ok
- rebuild fingerprints ok
- searching new items ok
- thumbnails ok
- quality sort ok (but very slow - 2 days?)
- synchronizing metadata (both directions) leads to segementation vault & crash

Sorry, I can't see any error message for the segementation vault in the shell
(zsh). How can I get the informations you need?

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|MySQL : Maintenance leads   |MySQL : needs to set
                   |to crash digiKam            |"max-allowed-packet" server
                   |                            |settings from 4.096 to
                   |                            |16.777.216 to prevent
                   |                            |Maintenance tool crash
            Version|4.14.0                      |5.0.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #21 from [hidden email] ---
- quality sort ok (but very slow - 2 days?) ==> yes this part have never been
optimized from algorithm side.

- synchronizing metadata (both directions) leads to segmentation vault & crash
: probably some non re-entrancy with Exiv2 shared library. Did you use at least
0.25 release and disable multi-core support. Just to be sure. There are a lots
of reports about this problem in bugzilla...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
     Ever confirmed|0                           |1
                 CC|                            |[hidden email]
         Resolution|WAITINGFORINFO              |---

--- Comment #22 from [hidden email] ---
Swati,

1/ We need to fix internal Mysql configuration file include with digiKam to set
right value of "max-allowed-packet".

2/ In Remote Mysql Setup page Requirements, we need to add some words about
this settings to be sure that end user will configure fine the server.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #23 from [hidden email] ---
> I can't see any error message for the segmentation vault in the shell (zsh). How can I get the informations you need?

Very simple. from a console, just run digiKam in gdb as explained here :

https://www.digikam.org/contrib

When it crash, the backtrace will be reported by GDB "bt" command.

Note : digiKam must be compiled with debug symbols.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #24 from [hidden email] ---
Thanks for your patience. I will build digikam with USE=debug today and test
again.

This is my exiv2:
---------
media-gfx/exiv2
     Verfügbare Versionen:   0.24-r1(0/13) ~0.25-r1(0/14) 0.25-r2(0/14)[1]
{contrib doc examples nls png static-libs webready xmp zlib ABI_MIPS="n32 n64
o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" LINGUAS="bs de es fi
fr gl ms pl pt ru sk sv ug uk vi"}                                              
     Installierte Versionen: 0.25-r2(0/14)(16:57:49 14.02.2016)(nls png xmp
-doc -examples -webready ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64"
ABI_S390="-32 -64" ABI_X86="32 64 -x32" LINGUAS="de -bs -es -fi -fr -gl -ms -pl
-pt -ru -sk -sv -ug -uk -vi")                                                  
     Startseite:             http://www.exiv2.org/
     Beschreibung:           EXIF, IPTC and XMP metadata C++ library and
command line utility
-----

I don't know if it is build with multi-core support. I wil research...

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #25 from [hidden email] ---
ok, here we go:

-----
digikam.metaengine: ""  ==> Title:  QMap()
digikam.metaengine: ""  ==> Comment:  QMap(("x-default",
CaptionValues::caption: "Copyright 2011 by Uwe Haider        ",
CaptionValues::author: "", CaptionValues::date: QDateTime(
Qt::TimeSpec(LocalTime)) ) )
digikam.metaengine: ""  ==> Pick Label:  0
digikam.metaengine: ""  ==> Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: ""  ==> Read Iptc Keywords:  ()
digikam.metaengine: ""  ==> New Iptc Keywords:  ()
digikam.metaengine: xmlACDSee "<Categories></Categories>"
digikam.metaengine: Failed to apply changes: file path is empty!
digikam.general: One job is done
digikam.general: One job is done
digikam.general: No write to baloo +++++++++++++++++++++++++++++++++++++
digikam.general: One job is done
digikam.general: One job is done
[Switching to Thread 0x7fff4f319700 (LWP 1393)]
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffe96ba72a0,
tinfo=0x7ffff71aa480 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7ffff682a8e0 <Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63    
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:
Datei oder Verzeichnis nicht gefunden.
---------

And here is the backtrace:

(gdb) bt
#0  __cxxabiv1::__cxa_throw (obj=0x7ffe96ba72a0, tinfo=0x7ffff71aa480 <typeinfo
for Exiv2::BasicError<char>>, dest=0x7ffff682a8e0
<Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
#1  0x00007ffff01eb865 in Exiv2::ImageFactory::open
(path="/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf",
useCurl=useCurl@entry=true)
    at
/var/tmp/portage/media-gfx/exiv2-0.25-r2/work/exiv2-0.25/src/image.cpp:478
#2  0x00007ffff680a880 in Digikam::MetaEngine::load
(this=this@entry=0x7fff4f318be0, filePath=...) at
/var/tmp/portage/media-gfx/digikam-5.0.0/work/digikam-5.0.0/core/libs/dmetadata/metaengine.cpp:278
#3  0x00007ffff68561d6 in Digikam::DMetadata::load
(this=this@entry=0x7fff4f318be0, filePath=...) at
/var/tmp/portage/media-gfx/digikam-5.0.0/work/digikam-5.0.0/core/libs/dmetadata/dmetadata.cpp:100
#4  0x00007ffff6856272 in Digikam::DMetadata::DMetadata (this=0x7fff4f318be0,
filePath=...) at
/var/tmp/portage/media-gfx/digikam-5.0.0/work/digikam-5.0.0/core/libs/dmetadata/dmetadata.cpp:67
#5  0x00007ffff76e7a9e in Digikam::MetadataHub::write
(this=this@entry=0x7fff4f318c60, filePath=..., writeMode=writeMode@entry=...,
ignoreLazySync=ignoreLazySync@entry=true, settings=...)
    at
/var/tmp/portage/media-gfx/digikam-5.0.0/work/digikam-5.0.0/core/libs/fileactionmanager/metadatahub.cpp:373
#6  0x00007ffff7626869 in Digikam::MetadataTask::run (this=0x1c3ac8480) at
/var/tmp/portage/media-gfx/digikam-5.0.0/work/digikam-5.0.0/core/utilities/maintenance/metadatatask.cpp:103
#7  0x00007ffff426aa8d in QThreadPoolThread::run (this=0x7fff14097820) at
thread/qthreadpool.cpp:93
#8  0x00007ffff426e52a in QThreadPrivate::start (arg=0x7fff14097820) at
thread/qthread_unix.cpp:341
#9  0x00007ffff5fd45e6 in start_thread (arg=0x7fff4f319700) at
pthread_create.c:334
#10 0x00007ffff399c9ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

-------------

Is this helpful for you? gdb is still running for further information....

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #26 from [hidden email] ---
ok, I have news for the exiv2 usage:

the gentoo package media-gfx/exiv2 isn't able for multi-core support. a
friendly soul has checked the code :-) (thank s to firefly)

So the only way to multi.core support is the switch in digikams maintenance
dialog - right? I don't use the switch because I have to work while digikam
makes the maintenance....

Is this informaiton what you need?

Uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #27 from [hidden email] ---
Oops! got some more:

-----
(gdb) cont
Continuing.
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
"Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im
Pfad /org/freedesktop/NetworkManager/ActiveConnection/2"
"Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im
Pfad /org/freedesktop/NetworkManager/ActiveConnection/2"
digikam.general: One job is done
digikam.metaengine: Cannot load metadata from file   (Error # 11 :
/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf: The file contains data of an
unknown image type
digikam.general: One job is done
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Comment:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Pick Label:  0
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
Read Iptc Keywords:  ()
digikam.metaengine: "/home/uhai/Bilder_alt/08-11-23 Hd Hausansicht.xcf"  ==>
New Iptc Keywords:  ()
digikam.metaengine: xmlACDSee "<Categories></Categories>"
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file "/home/uhai/Bilder_alt/08-11-23
Hd Hausansicht.xcf"
digikam.general: One job is done
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffe96ba72a0,
tinfo=0x7ffff71aa480 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7ffff682a8e0 <Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63      in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
(gdb)cont
[....]
digikam.metaengine: "/home/uhai/Bilder_alt/avatar.png"  ==> Read Iptc Keywords:
 ()
digikam.metaengine: "/home/uhai/Bilder_alt/avatar.png"  ==> New Iptc Keywords:
()
digikam.metaengine: xmlACDSee "<Categories></Categories>"
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file
"/home/uhai/Bilder_alt/avatar.png"
digikam.metaengine: wroteComment:  true
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "avatar.png" written to file.
digikam.metaengine: Will write XMP sidecar for file "avatar.png"
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file ' "avatar.png" ' written to XMP sidecar.
digikam.general: No write to baloo +++++++++++++++++++++++++++++++++++++
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffee26b3220,
tinfo=0x7ffff71aa480 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7ffff682a8e0 <Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63      in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
(gdb) cont
Continuing.
digikam.metaengine: Cannot load metadata from file   (Error # 11 :
/home/uhai/Bilder_alt/bag5.jpg: The file contains data of an unknown image type
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Comment:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Pick Label:  0
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> Read Iptc Keywords:
()
digikam.metaengine: "/home/uhai/Bilder_alt/bag5.jpg"  ==> New Iptc Keywords:
()
digikam.metaengine: xmlACDSee "<Categories></Categories>"
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file
"/home/uhai/Bilder_alt/bag5.jpg"
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffef20c0530,
tinfo=0x7ffff71aa480 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7ffff682a8e0 <Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63      in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
[....
-------

still running. Now I know "cont" :-)

uhai

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #28 from [hidden email] ---
That's it:

-------------
igikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Title:  QMap()
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Comment:  QMap()
digikam.general: One job is done
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Pick Label:  3
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Color Label:  0
digikam.metaengine: Rating value to write is out of range!
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> Read Iptc Keywords:  ()
digikam.metaengine: "/home/uhai/Bilder_alt/Urlaub Pfingsten
2011/2011-06-21T17-24-14.png"  ==> New Iptc Keywords:  ()
digikam.metaengine: xmlACDSee "<Categories></Categories>"
digikam.metaengine: MetaEngine::metadataWritingMode 2
digikam.metaengine: Will write Metadata to file "/home/uhai/Bilder_alt/Urlaub
Pfingsten 2011/2011-06-21T17-24-14.png"
digikam.metaengine: Exiv2 ( 3 ) :  Directory Casio2: Next pointer is out of
bounds; ignored.

digikam.metaengine: wroteComment:  true
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true

Program received signal SIGSEGV, Segmentation fault.
Exiv2::Internal::TiffComponent::addPath (this=0x0, tag=tag@entry=2,
tiffPath=std::stack wrapping: std::deque with 2 elements = {...},
pRoot=0x7ffeb3ac35a0, object=...)
    at
/var/tmp/portage/media-gfx/exiv2-0.25-r2/work/exiv2-0.25/src/tiffcomposite.cpp:634
634    
/var/tmp/portage/media-gfx/exiv2-0.25-r2/work/exiv2-0.25/src/tiffcomposite.cpp:
Datei oder Verzeichnis nicht gefunden.
(gdb) cont
Continuing.
[Thread 0x7fff4eb18700 (LWP 6703) exited]
[Thread 0x7fff0effd700 (LWP 1038) exited]
[Thread 0x7fffd2105700 (LWP 8136) exited]
[Thread 0x7fffdadff8c0 (LWP 7847) exited]
[Thread 0x7fff4f319700 (LWP 1393) exited]
[Thread 0x7fffc8e3c700 (LWP 9969) exited]
[Thread 0x7ffefd5eb700 (LWP 8218) exited]
[Thread 0x7ffefddec700 (LWP 8217) exited]
[Thread 0x7ffefe5ed700 (LWP 8216) exited]
[Thread 0x7ffefedee700 (LWP 8215) exited]
[Thread 0x7fffca837700 (LWP 8175) exited]
[Thread 0x7fffcb7fe700 (LWP 8173) exited]
[Thread 0x7fffcbfff700 (LWP 8138) exited]
[Thread 0x7fffd0fdd700 (LWP 8137) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
----------
But no Backtrace:
-----
(gdb) bt
No stack.
------

uhai

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #29 from [hidden email] ---
Thanks Uwe,

All backtraces indicate a problem with Exiv2 multicore/Multi-threads
processing. This use case problem must be reported to Exiv2 bugzilla. There is
no reason for these kind of dysfunctions while Exiv2 read or write from/to
image files metadata.

>the gentoo package media-gfx/exiv2 isn't able for multi-core support. a friendly soul has checked the code :-) (thank s to firefly)

How this information have been verified exactly ?

So the only way to multi.core support is the switch in digikams maintenance
dialog - right? I don't use the switch because I have to work while digikam
makes the maintenance....

Yes. Disabling multicore support will run maintenance tools in a single CPU. It
will be interesting to see if the Exiv2 dysfunctions are reproducible in this
case.

Of course, One single core to run maintenance tools will be slower, as
expected.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #30 from [hidden email] ---
Git commit abe510108e827ad3f2f1946a5651cda85cb071f0 by Swati Lodha.
Committed on 06/08/2016 at 09:39.
Pushed by swatil into branch 'master'.

Change MySQL configuration file

M  +1    -1    data/database/mysql-global.conf
M  +3    -1    libs/database/utils/dbsettingswidget.cpp

http://commits.kde.org/digikam/abe510108e827ad3f2f1946a5651cda85cb071f0

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #31 from [hidden email] ---
Git commit c8e7c3260cacc6ebf422efe15d703a7188cd132c by Gilles Caulier.
Committed on 06/08/2016 at 13:44.
Pushed by cgilles into branch 'master'.

Due to some limitation in Exiv2 with multithreads/multi-core CPU (even with
last Exiv2 0.25), limit metatdate synchronizer maintenenace tool to one CPU for
the moment.

M  +1    -1    utilities/maintenance/maintenancedlg.cpp
M  +3    -2    utilities/maintenance/maintenancemngr.cpp

http://commits.kde.org/digikam/c8e7c3260cacc6ebf422efe15d703a7188cd132c

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=329091

--- Comment #32 from [hidden email] ---
Uwe,

Metadata synchronizer maintenance tool will always use one cpu core now.

Please confirm that fix crash on you computer.

Also, we must have a real feedback from Exiv2 team about muticore cpu support
in this library. Please report this problem into Exiv2 bugzilla as well.

Thanks in advance

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.