https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #17 from Kristian Karl ---
Thank you very much Maik
/Kristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #14 from Kristian Karl ---
A workaround that seems to work for me is adding: "-xmp-gcontainer:all= " to my
exiftool command in my script.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #13 from Kristian Karl ---
I think I have a repro for creating the occurrence of the "tmp0" container.
1 - Remove the sidecar file
2 - From Digikam select the image and from the menu do "Item -> Write Metadata
to File
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #12 from Kristian Karl ---
No. No other software than Digikam for this image/sidecare. It was created by
Digikam/Exfitool.
Version of exiftool on my machine is 13.25
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #8 from Kristian Karl ---
I added the new test data (my 2nd commit) to my fork of digikam-test-data, but
I guess you mean that the test job of the automatic pipeline used data from
https://invent.kde.org/graphics/digikam-test-data, and not
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #5 from Kristian Karl ---
Looks like the CI caught my failing test:
https://invent.kde.org/kristiankarl/digikam/-/pipelines/946628
I did not know that CI ran on forked project in KDE/Gitlab - very nice!
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #4 from Kristian Karl ---
I maybe have created a better repro for you.
I forked digikam and digikam-test-data from https://invent.kde.org and created
2 commits that together reproduces the problem of getting the exiv2 errors:
Exiv2 ( 3
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #3 from Kristian Karl ---
Ah, good to know.
However the problem is very real for me.
Let me see if I can come up with a better repro.
Kristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503885
Kristian Karl changed:
What|Removed |Added
Version|unspecified |8.7.0
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=503885
--- Comment #1 from Kristian Karl ---
Added attachments here:
https://github.com/KristianKarl/digikam_bugs/tree/main/bug_503885
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503885
Bug ID: 503885
Summary: Fails to write to sidecar file, leaving it corrupt
Classification: Applications
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=502629
Bug ID: 502629
Summary: Some Keyboard Accelerators are not working, and some
input boxes aren't tabbed through
Classification: Applications
Product: krename
Version: 5.0.1
Pla
https://bugs.kde.org/show_bug.cgi?id=502629
--- Comment #1 from Kristian Buchman ---
I've made a mistake in this bug report.
When Extension is set to Use original extension the accelerator doesn't
respond, but once you change it to Custom Extension it does!
However, the behav
https://bugs.kde.org/show_bug.cgi?id=497824
--- Comment #1 from Kristian Karl ---
Video file:
https://github.com/KristianKarl/digikam_bugs/raw/refs/heads/main/bug_497824/location_test.mp4
Video sidecar file:
https://raw.githubusercontent.com/KristianKarl/digikam_bugs/refs/heads/main/bug_497824
https://bugs.kde.org/show_bug.cgi?id=497824
--- Comment #4 from Kristian Karl ---
Thank you very much. All good now :+1:
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497824
Bug ID: 497824
Summary: Wrong location displayed for mp4
Classification: Applications
Product: digikam
Version: 8.6.0
Platform: Appimage
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=493726
Bug ID: 493726
Summary: Plasma crashes after resuming from suspended mode
Classification: Plasma
Product: plasmashell
Version: 5.27.5
Platform: Debian stable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #14 from Kristian ---
Created attachment 169579
--> https://bugs.kde.org/attachment.cgi?id=169579&action=edit
Screenshots
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #13 from Kristian ---
I finally found some time to have another look and I can easily reproduce the
bug with a backup. As per the discussion, it is because of the changed UUID and
should be fixed in the next version, but did you also
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #13 from Kristian ---
It's reproducible: It's not even necessary to do anything with the picture,
after "writing metadata to file", the dates previously mentioned are changed by
one hour.
This can be fixed by applying
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #12 from Kristian ---
i don't know if this is connected, but I've also trouble with the times of JPEG
files after activating the settings to write face and GPS data to the file and
performing a "write meta data to file"
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #11 from Kristian ---
Created attachment 167726
--> https://bugs.kde.org/attachment.cgi?id=167726&action=edit
Screenshot metadata settings Exiftool
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #10 from Kristian ---
Created attachment 167725
--> https://bugs.kde.org/attachment.cgi?id=167725&action=edit
Screenshot metadata settings side car files
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #9 from Kristian ---
Created attachment 167724
--> https://bugs.kde.org/attachment.cgi?id=167724&action=edit
Screenshot metadata settings behaviour
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #11 from Kristian ---
OK, I did this, but digikam is still continuing to perform a full scan for new
entries.
I assume it's save to continue to use the backup database or is there anything
I need to check?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #15 from Kristian ---
I can confirm that this bug only appears on my old Thinkpad T420 with a Nvidia
graphics card and the respective Nvidia drivers. I've a new one which does not
show this behaviour.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #3 from Kristian ---
I can reproduce it, but it only occurs when the following setting is UNCHECKED:
Metadata -> Behaviour -> Write Metadata -> GPS coordinates
In this case the NEF files show GPS coordinates i.e. the little g
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #8 from Kristian ---
Please see attached log:
digikam.database: Creating new Location "/$USER/Bilder/Fotos" uuid
"volumeid:?uuid=27ea6369-b602-469f-b7e7-XXX&fileuuid=40d34373-bac4-4760-bfca-XXX"
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #7 from Kristian ---
Created attachment 167711
--> https://bugs.kde.org/attachment.cgi?id=167711&action=edit
digikam startup log (after bug happened)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #6 from Kristian ---
It is still the same and I did not touch it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #4 from Kristian ---
That's what I did, digkam started the scanning automatically.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
--- Comment #2 from Kristian ---
The file "digikam4.db" was gone, but a file called
"digikam4.db-backup-2024-03-24T18:04:56" was there instead.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484398
--- Comment #2 from Kristian ---
I have "write into file and XMP side car files" activated.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484400
Bug ID: 484400
Summary: digikam doesn't find DB anymore after change of
settings
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=484398
Kristian changed:
What|Removed |Added
Summary|GPS Coordinates for JPEG|GPS Coordinates for JPEG
|files
https://bugs.kde.org/show_bug.cgi?id=484398
Bug ID: 484398
Summary: GPS Coordinates for JPEG files are not saved (need to
iterations)
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=483633
Bug ID: 483633
Summary: KDE crashes
Classification: Plasma
Product: kwin
Version: 5.27.5
Platform: Debian stable
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=474265
--- Comment #15 from Kristian Karl ---
I downloaded and tested: digiKam-8.3.0-20231223T122431-x86-64.appimage (which
is a later date than 20231222T162413)
I'm afraid that it still crashes the same way:
=
https://bugs.kde.org/show_bug.cgi?id=474265
--- Comment #12 from Kristian Karl ---
Maybe related: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/2046844
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474265
Kristian Karl changed:
What|Removed |Added
CC||kristian.hermann.karl@gmail
https://bugs.kde.org/show_bug.cgi?id=477379
Kristian changed:
What|Removed |Added
Version|8.1.0 |8.2.0
--- Comment #12 from Kristian ---
Same story
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #11 from Kristian ---
...and the same crash with a different user who newer used digikam.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #10 from Kristian ---
No change, still crashes. Renaming the complete folder .local/share/digikam
doesn't help, too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433732
Kristian changed:
What|Removed |Added
CC||kde-b...@kristiankoch.com
--- Comment #52 from
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #8 from Kristian ---
Created attachment 163409
--> https://bugs.kde.org/attachment.cgi?id=163409&action=edit
GDB output with QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing"
Still crashes with export
QTWEBENGI
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #6 from Kristian ---
I closed everything and now GDB ran through, see attached logs with different
variables exported.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #5 from Kristian ---
Created attachment 163376
--> https://bugs.kde.org/attachment.cgi?id=163376&action=edit
GDB output with QT_LOGGING_RULES="digikam*=true" and
QTWEBENGINE_DISABLE_GPU_THREAD=1
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #4 from Kristian ---
Created attachment 163375
--> https://bugs.kde.org/attachment.cgi?id=163375&action=edit
GDB output with QT_LOGGING_RULES="digikam*=true"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477379
--- Comment #3 from Kristian ---
Unfortunately, the terminal crashes each time I try to use GDB. Logging to a
file creates a strange file with hundres of white lines and very few info like
"[New Thread 0x7fffb53fa6c0 (LWP 30253)]".
Here&#x
https://bugs.kde.org/show_bug.cgi?id=477379
Bug ID: 477379
Summary: digikam crashes on start with "failed to create
drawable" / "glXCreatePbuffer failed."
Classification: Applications
Product: digikam
Version: 8.1.0
Pla
https://bugs.kde.org/show_bug.cgi?id=468573
--- Comment #11 from Kristian Rink ---
(In reply to vujo from comment #10)
> (In reply to Kristian Rink from comment #9)
> > Yes I do.
>
> Can you write your OS and version of kate?
Hmm. kate 22.12.3, Kubuntu 23.04 - I think I alread
https://bugs.kde.org/show_bug.cgi?id=468573
--- Comment #9 from Kristian Rink ---
Yes I do.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468573
--- Comment #7 from Kristian Rink ---
Seems not related to FreeBSD. Same here (kate 22.12.3, Kubuntu 23.04).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468573
Kristian Rink changed:
What|Removed |Added
CC||m...@zimmer428.net
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=468586
--- Comment #9 from Kristian Karl ---
I tested the fix this morning, and it works as expected now.
Thank you very much, I really appreciate your work <3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468586
--- Comment #5 from Kristian Karl ---
Ah, nice, thank you!
I did not mention it, but I'm running my digikam on a Maria/mysql instance. But
I guess it does not matter in this case?
Also, I made a video https://youtu.be/BUHJIVCn-XY using a
https://bugs.kde.org/show_bug.cgi?id=468586
--- Comment #3 from Kristian Karl ---
Ah, interesting! Maybe my repro steps was flawed or incorrect. I'll make a
video of the problem tomorrow.
One way to expose the problem is to ask Digikam to re-read from the sidecar
files, but it is not nece
https://bugs.kde.org/show_bug.cgi?id=468586
--- Comment #1 from Kristian Karl ---
Also, I tested an verified the same unexpected result on
digiKam-8.0.0-x86-64.appimage
Build date: 2023-04-12 15:32 (target: RelWithDebInfo)
Revision: 66b84e1ba8f8003994fa398a669e1ccc4224a901
Branch: HEAD
https://bugs.kde.org/show_bug.cgi?id=468586
Bug ID: 468586
Summary: Deleting 2 tags only updates 1 tag to file
Classification: Applications
Product: digikam
Version: unspecified
Platform: Ubuntu
OS: Linux
Status
https://bugs.kde.org/show_bug.cgi?id=462845
Kristian Polso changed:
What|Removed |Added
CC||krist...@polso.info
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=457847
Kristian Polso changed:
What|Removed |Added
CC||krist...@polso.info
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=459695
--- Comment #2 from Kristian Karl ---
I uploaded to dropbox an example of a raw Gopro image, GOPR0006.GPR, made by a
Gopro Hero 11 camera.
https://www.dropbox.com/s/1fas6ackb5g7uyt/GOPR0006.GPR?dl=0
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=459695
Bug ID: 459695
Summary: Digikam does not include Gopro raw images *.GPR
Classification: Applications
Product: digikam
Version: 7.9.0
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=458200
--- Comment #4 from Kristian Karl ---
I verified the fix, and it looks great.
Thank you :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458200
Bug ID: 458200
Summary: Size or position change made to face rectangle is only
written to database and not to image file/sidecar
Product: digikam
Version: 8.0.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=454656
--- Comment #7 from Kristian Karl ---
I verified the fix, and it works fine now.
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=454656
--- Comment #3 from Kristian Karl ---
exiftool version => 12.40
Regarding the question of missing locale settings:
Yes, that is a good question indeed. It's a complete fresh install of Ubuntu
22.04, using English as the main language, and Sw
https://bugs.kde.org/show_bug.cgi?id=454656
Bug ID: 454656
Summary: When locales not set, crash occurs when opening
"Settings -> Configure digikam"
Product: digikam
Version: 8.0.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #12 from Kristian Karl ---
Most awesome!
Thanks for the speedy fix :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #7 from Kristian Karl ---
Ah, thanks! Good to know for the next time :+1:
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #5 from Kristian Karl ---
Created attachment 148456
--> https://bugs.kde.org/attachment.cgi?id=148456&action=edit
Screenshot of "Adjust Time & Date"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #4 from Kristian Karl ---
Video available here:
https://www.dropbox.com/s/l8lxx65ovjkdya9/2022-04-27_181056.mp4?dl=0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #3 from Kristian Karl ---
This output was not possible to add here, so I created a public gist unstead:
https://gist.github.com/KristianKarl/cbf1e62c3fdfbd7bfa7bb97bbd57ccd4
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #2 from Kristian Karl ---
Select the attached video in thumbnal view, and then open the dialog "Adjust
Time & Date"
Digikam: digiKam compiled from sources
==
>digikam.general: Act
https://bugs.kde.org/show_bug.cgi?id=453180
--- Comment #1 from Kristian Karl ---
For some reason, I get "Your comment has been automatically blocked as it is
believed to contain spam. Please contact Sysadmin if you believe this to be
incorrect." when I try to add the log output fr
https://bugs.kde.org/show_bug.cgi?id=453180
Bug ID: 453180
Summary: "not valid" dates for video in "Adjust Time & Date"
Product: digikam
Version: 8.0.0
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=251424
Kristian Karl changed:
What|Removed |Added
CC||kristian.hermann.karl@gmail
https://bugs.kde.org/show_bug.cgi?id=451802
--- Comment #9 from Kristian Karl ---
I verified the fix this morning. Looks all good now.
Thanks Maik :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451802
--- Comment #5 from Kristian Karl ---
Inserting this code after
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/geolocation/geoiface/tracks/trackreader.cpp#L332
seems to be one solution to the problem.
if (xml.name
https://bugs.kde.org/show_bug.cgi?id=451802
Bug ID: 451802
Summary: GPX files fails to load
Product: digikam
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=450518
Bug ID: 450518
Summary: Crash when opening Advanced Search
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=381319
Kristian Karl changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=381319
--- Comment #8 from Kristian Karl ---
Hi Gilles and happy new year!
I think we can close this report. I believe the modification for a tablet to
work with DK is maybe unnecessary.
I stopped using the tablet this way. Keyboard and mouse is much faster
https://bugs.kde.org/show_bug.cgi?id=444692
--- Comment #6 from Kristian ---
(In reply to Maik Qualmann from comment #5)
> Fixed with this merge request from Philip Gouverneur:
>
> https://invent.kde.org/graphics/digikam/-/commit/
> 6836a0f4399de081f1bd42f01da94a5220ca9086
>
&g
https://bugs.kde.org/show_bug.cgi?id=427278
--- Comment #12 from Kristian Rink ---
(In reply to Alain Knaff from comment #11)
> (In reply to Kristian Rink from comment #10)
> > Wondering, though, whether there's a more reliable workaround for that.
> > Restarting plasm
https://bugs.kde.org/show_bug.cgi?id=427278
--- Comment #10 from Kristian Rink ---
Wondering, though, whether there's a more reliable workaround for that.
Restarting plasma seems to work just sometimes, but sometimes the panel just
won't re-appear or apparently there's no way of
https://bugs.kde.org/show_bug.cgi?id=427278
Kristian Rink changed:
What|Removed |Added
CC||m...@zimmer428.net
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=427209
Bug ID: 427209
Summary: Music pauses on Android phone when Linux laptop is
closed
Product: kdeconnect
Version: unspecified
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=421023
--- Comment #12 from Kristian Karl ---
For me, it works as expected again.
Thanks for the fix :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421023
Kristian Karl changed:
What|Removed |Added
CC||kristian.hermann.karl@gmail
https://bugs.kde.org/show_bug.cgi?id=418337
Bug ID: 418337
Summary: Crash after resume
Product: digikam
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=416231
Kristian Karl changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=416231
--- Comment #7 from Kristian Karl ---
Okay, got it!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416231
--- Comment #5 from Kristian Karl ---
Sorry, not left sidebar. I meant the right metadata sidebar in the comment
above.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416231
--- Comment #4 from Kristian Karl ---
Should not the update to the database (by the Time Adjust Tool) be reflected in
the [left] Metadata sidebar?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416231
--- Comment #2 from Kristian Karl ---
Ah, true. I missed that. Thanks for clarifying.
But how come is actually changes when I do a "Item -> Write Metadata to File"?
Maybe
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416231
Bug ID: 416231
Summary: exif date not written to sidecar file when modified,
nor is it updated in the metadata sidebar
Product: digikam
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=415679
Kristian Karl changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=415679
--- Comment #3 from Kristian Karl ---
I experimented a bit, and I think I know what's going on.
When I let Digikam detect faces, I set 'Face Accuracy' to 100%, which gives
very good results.
Then I carry on with Face Recognition, wit
https://bugs.kde.org/show_bug.cgi?id=415679
--- Comment #2 from Kristian Karl ---
My subset of images were placed in a new folder, and I started a new Digikam
database in that folder. So everything was completely new for Digikam. No old
databases.
I started digikam like this:
digikam --database
1 - 100 of 237 matches
Mail list logo
