https://bugs.kde.org/show_bug.cgi?id=329091
Maik Qualmann changed:
What|Removed |Added
Status|REOPENED|RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #39 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle
available here :
https://files.kde.org/digikam/
Gilles Caulier
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #38 from caulier.gil...@gmail.com ---
Following this commit:
https://commits.kde.org/digikam/6a9fd9891a3ff341dc42fe36158cbf0101d513b6
... the approach to fix this problem is under way and new digiKam 5.8.0
pre-release bundles will be
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #37 from Maik Qualmann ---
Git commit 6a9fd9891a3ff341dc42fe36158cbf0101d513b6 by Maik Qualmann.
Committed on 17/12/2017 at 19:20.
Pushed by mqualmann into branch 'master'.
delete threads from memory when they are
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #36 from caulier.gil...@gmail.com ---
new 5.6.0 pre-release as bundle is available here :
https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
Please check if this problem still reproducible with these versions.
Thanks in
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #35 from uwe.hai...@gmx.net ---
Done.
Here it can be found: http://dev.exiv2.org/issues/1207
uhai
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #34 from caulier.gil...@gmail.com ---
[Switching to Thread 0x7ffee7ff7700 (LWP 6946)]
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffeec27dd40,
tinfo=0x771a8340 >,
dest=0x76818ce0
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #33 from uwe.hai...@gmx.net ---
Tested now with gdb and digikam-5.1.0 (with german trasnlation!):
New crash with face-search - sorry no backtrace:
digikam.general: Check for finish: 51 packages, 0 infos to filter,
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #32 from caulier.gil...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #31 from caulier.gil...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #30 from caulier.gil...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #29 from caulier.gil...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #28 from uwe.hai...@gmx.net ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #27 from uwe.hai...@gmx.net ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #26 from uwe.hai...@gmx.net ---
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
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #25 from uwe.hai...@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:
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #24 from uwe.hai...@gmx.net ---
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]
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #23 from caulier.gil...@gmail.com ---
> 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://bugs.kde.org/show_bug.cgi?id=329091
caulier.gil...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=329091
--- Comment #21 from caulier.gil...@gmail.com ---
- 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
https://bugs.kde.org/show_bug.cgi?id=329091
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|MySQL : Maintenance leads |MySQL : needs to set
21 matches
Mail list logo