https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #16 from vadeinpa...@gmail.com ---
Thanks much.
I would appreciate your observation on YOLO based facial recognition. I am
running it for close to a day and it scanned about 10% of the images. It does
not seem to use my GPU even though the
https://bugs.kde.org/show_bug.cgi?id=430451
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
|
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #14 from vadeinpa...@gmail.com ---
Thanks Much; --Haim
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #13 from Maik Qualmann ---
The crash with 16 bit PSD files has just fixed in the current version. Please
install and report Beta2 (2020-12-16)from here:
https://files.kde.org/digikam/
Maik
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #12 from vadeinpa...@gmail.com ---
Hello,
I am now able to easily recreate the problem. I identified the file. Its a
"psd" file 596MB.
I removed all collections for digikam, created a new collection with this file
and digikam stops abruptly
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #11 from vadeinpa...@gmail.com ---
Thanks for your comments.
The file indicated seems OK and exiftool has no warnings regarding it.
Also, its probably not an issue with a single file.
I run the facial recognition on 2 unique catalog subsets
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #10 from Maik Qualmann ---
This extreme debug output from libjpeg is strange. It can be this file:
D:/Photography/Pictures/טיולים בחול/09-2018 Laugavegur איסלנד/05-09-2018
Reykjav?k/Iceland_2018-09-05_0129.jpg
You have also activated the t
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #9 from vadeinpa...@gmail.com ---
Hello,
I decided to skip fingerprinting and do facial recognition through the
maintenance menu.
Results are the same. digikam stops at what seems to be the same position.
It may reaffirm the notion that fail
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #8 from vadeinpa...@gmail.com ---
Hello,
The scientific comment related to the progress bar. I share your suspicion
that there may be a problem with parsing a specific image.
1 - I did not add new images recently, and things worked OK with
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #7 from caulier.gil...@gmail.com ---
If finger print process stop at the same place, it's more scientific that you
expect. This want probably mean that an image cannot be parsed and generated an
exception.
Another possibility is a file size
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #6 from vadeinpa...@gmail.com ---
Thanks for your comment.
I removed the similarity.db, started digikam and run the fingerprint process.
digikam broke at what seems to be the same point as before (the DB size is
similar as well as the process
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #5 from caulier.gil...@gmail.com ---
So, it's not a crash, but a break point somewhere, as a database lock for
example...
Where is stored your sqlite database file ? Locally i hope, as sqlite do not
support network shared file system...
Gil
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #4 from vadeinpa...@gmail.com ---
Hello,
Installed digiKam-7.2.0-beta2-20201214T120943-Win64-debug.
I do not see any digikam_crash.log
Please note that there is still a digikam process running on my machine. It
does not consume any CPU.
Than
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #3 from vadeinpa...@gmail.com ---
Thanks for your prompt response.
I do not have a log file. I installed from the Win64 binary that did not have
debug symbols.
Please note that I used to work with local MySQL (MariaDB) and there was no
prob
https://bugs.kde.org/show_bug.cgi?id=430451
Maik Qualmann changed:
What|Removed |Added
Severity|normal |crash
CC|
https://bugs.kde.org/show_bug.cgi?id=430451
--- Comment #2 from caulier.gil...@gmail.com ---
Under Windows, the binary installers comes with debug symbols and a DrMinGw
crash course handler, which will generate a file backtrace in you home
directory as below:
C:\Users\_user_name_\AppData\Loca
https://bugs.kde.org/show_bug.cgi?id=430451
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
17 matches
Mail list logo