[Digikam-devel] [digikam] [Bug 329091] MySQL : needs to set "max-allowed-packet" server settings from 4.096 to 16.777.216 to prevent Maintenance tool crash

[via KDE Bugzilla]

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

--- Comment #25 from uwe.haider at gmx.net ---
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 at 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 at 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 at 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 at entry=0x7fff4f318c60, filePath=..., writeMode=writeMode at entry=...,
ignoreLazySync=ignoreLazySync at 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.