[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467711 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-24 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #10 from Daimonicon --- Thanks in any case for your time and effort. It's not because the images have been shrinked in size ? To be on the safe side, I had removed the ~200 shrinked images and replaced them with completely new ones. Since

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #9 from Maik Qualmann --- I see in your log: Using 24 CPU core to run thread We have seen strange behavior with machines that have such a high number of CPU cores. I'll take a look at the relevant code again in the next few days. Maik --

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #8 from Maik Qualmann --- Your database is constantly locked for the maximum wait time of 10 seconds and then discards the job. Normally, this wait time is used to wait for the other thread that is currently performing a write (SQLite can

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #7 from Daimonicon --- I may have found the problem, but I'm not 100% sure. The DB contains a total of about 3500 entries, for the last 100-150 I had the idea that it would not be bad to shrink the size of the pictures without quality lost

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #6 from Daimonicon --- I created another log this time it took several minutes but the app didn't hang - estimate 20-30 minutes I can't figure out from the log time. 139 images with colour markers. I added a user marker to the beginning

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #5 from Daimonicon --- Attachments doesn't work cause of file size Link: https://gist.github.com/Daimonicon/1d70ab6c4692a43c19fee366ef14b680 -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #4 from Daimonicon --- (In reply to Maik Qualmann from comment #3) > If it took longer to apply the tags, the progress bar would activate. A wait > cursor could only occur if there are several thousand images in the current > album, since

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #3 from Maik Qualmann --- If it took longer to apply the tags, the progress bar would activate. A wait cursor could only occur if there are several thousand images in the current album, since the tag status then has to be read again from

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467711 --- Comment #2 from Daimonicon --- (In reply to Maik Qualmann from comment #1) > How many images did you apply the tag change to? And how many images are in > the current view? > > Maik When I noticed it, it was 5-15 pictures, but sometimes I have

[digikam] [Bug 467711] Display the real actual status of digiKam.

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467711 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik