https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #24 from caulier.gil...@gmail.com ---
Hi,
The digiKam 8.7.0 pre-release for Windows have been rebuild from scratch today
with many improvements and updates. Please test with this version to see if the
problem is reproducible.
Link to downlo
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #23 from caulier.gil...@gmail.com ---
Hi,
digiKam 8.6.0 is just released:
https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/
Problem still exists with this version?
Thanks in advance
Gilles Caulier
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #22 from caulier.gil...@gmail.com ---
@stefan,
digiKam 8.3.0 stable version is released and available at usual place :
https://www.digikam.org/download/
Can you reproduce the dysfunction on your computer ?
Thanks in advance
Gilles Caulie
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #21 from caulier.gil...@gmail.com ---
@stefan.mueller...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #19 from caulier.gil...@gmail.com ---
Git commit 3d71acc72593534c2a1398d2945992fbbf45935a by Gilles Caulier.
Committed on 16/05/2023 at 03:00.
Pushed by cgilles into branch 'master'.
Switch bundles from Exiv2 0.27 maintenance branch to new 0
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #20 from caulier.gil...@gmail.com ---
Git commit 3d71acc72593534c2a1398d2945992fbbf45935a by Gilles Caulier.
Committed on 16/05/2023 at 03:00.
Pushed by cgilles into branch 'master'.
Switch bundles from Exiv2 0.27 maintenance branch to new 0
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #18 from stefan.mueller...@gmail.com ---
Cannot tell at the moment, I don't use it currently (travelling)
sent from a fair mobile
On Thu, 20 Apr 2023, 07:40 , wrote:
> https://bugs.kde.org/show_bug.cgi?id=386291
>
> --- Comment #17 from c
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #17 from caulier.gil...@gmail.com ---
@stefan
digiKam 8.0.0 is out. Problem still reproducible ?
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #16 from hgx9j8a34...@opayq.com ---
Hi Maik,
What could be done to make the mapping face process faster for the user and
less error prone (avoiding refresh on the screen)?
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #15 from Maik Qualmann ---
Again, the whole thing here has nothing to do with lazy synchronization at all.
The lazy synchronization writes the metadata into the images at the end of the
program or manually. We cannot delay writing to the dat
https://bugs.kde.org/show_bug.cgi?id=386291
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|5.8.0 |7.3.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=386291
hgx9j8a34...@opayq.com changed:
What|Removed |Added
CC||hgx9j8a34...@opayq.com
--- Comment #14
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #13 from caulier.gil...@gmail.com ---
digiKam 7.2.0 official release is published with more than 360 files closed
from bugzilla:
https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/
Can you reproduce the dysfunction with this
https://bugs.kde.org/show_bug.cgi?id=386291
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #11 from caulier.gil...@gmail.com ---
Hi,
Can you check if this problem still exist with last weekly bundle build of
digiKam 7.0.0 available here:
https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=386291
IWBR changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #10 from stefan.mueller...@gmail.com ---
Hallo Maik,
if the described behaviour cannot be prevented I would like to have a
stop/start screen refresh or un-/freeze database operations button. It may need
to be activated first in the options me
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #9 from stefan.mueller...@gmail.com ---
first of all the obligatory, happy new year :)
so how can I prevent
>When I do face recognition and change and/or confirm a recognized face it
>disappear immediately from the *Unconfirmed* collectio
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #8 from Maik Qualmann ---
Lazy synchronization is about the delayed writing of metadata FROM the database
into the images / sidecar.
The database is always up to date, otherwise digiKam would not work.
Maik
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #7 from stefan.mueller...@gmail.com ---
For clarification, lazy synchronization (Settings - Metadata - Behavior tab) is
supposed that digikam won't sync database, sidecars or images (depending where
metadata shall be stored) until you click o
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #6 from Maik Qualmann ---
There is no change in the function here because the operation is misunderstood
for Lazy synchronization. Of course, the database is always updated, where else
should all changes be saved, which should later be writt
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #5 from stefan.mueller...@gmail.com ---
Will to next week as I currently away
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #4 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just
released ?
https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #3 from stefan.mueller...@gmail.com ---
any chance to add option that it will be possible to prevent auto-refresh and
have it be done by the user themself?
It's getting really nasty to find wrongly tagged faces again and again
--
You are re
https://bugs.kde.org/show_bug.cgi?id=386291
--- Comment #2 from stefan.mueller...@gmail.com ---
I've been explained that the database won't be updated until sync button is
pressed.
I don't want the search results (e.g. face recognition) to be updated when I
change/add a property (e.g. person tag)
https://bugs.kde.org/show_bug.cgi?id=386291
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
26 matches
Mail list logo
