https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #56 from Mark Stoughton ---
Everything is fine on this end now. As far as I'm concerned this can be closed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #55 from Mark Stoughton ---
I think I fixed it. Two different solutions, one for PC one for Mac. Both
versions seem to be running fine now.
For the PC
-Uninstall and reinstall Digikam.
For the Mac
- Uninstall and reinstall Digikam
https://bugs.kde.org/show_bug.cgi?id=405235
Mark Stoughton changed:
What|Removed |Added
OS|All |macOS
--- Comment #54 from Mark Stoughton
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #53 from Mark Stoughton ---
I've found one more thing. I swapped databases between the one that uses local
files and the one that uses files on the NAS.
The only difference was the location of the photo files. The databases were
both
https://bugs.kde.org/show_bug.cgi?id=405235
Mark Stoughton changed:
What|Removed |Added
OS|Linux |All
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #52 from Mark Stoughton ---
I ran a few more tests. I think that I've isolated the issue to occur only
when photos are stored on the NAS.
Test 1: Move the database off the System drive to a Thunderbolt Attached SSD -
Photos still
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #51 from Mark Stoughton ---
I ran a few more tests. I think that I've isolated the issue to occur only
when photos are stored on the NAS.
Test 1: Move the database off the System drive to a USB Attached SSD
-Startup time reduced to 21
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #49 from Mark Stoughton ---
(In reply to Maik Qualmann from comment #48)
> If you change an album it's a pure database operation. It doesn't matter
> whether the album is on a NAS. As a test, I would move the digiKam dat
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #47 from Mark Stoughton ---
Hi,
That is correct, it takes about 3 minutes to change folders while using the
program. While in a single folder the program works fine, but takes about a
minute to read the metadata, particularly the EXIF
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #46 from Mark Stoughton ---
I checked the rights and digicam does have RW on the entire drive. The only
thing that I can think of is that there may be some issue because the files are
on a NAS. So this morning I installed it on another
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #45 from Mark Stoughton ---
(In reply to Maik Qualmann from comment #44)
> I understand you correctly that the change from an album takes 3 minutes
> after the start?
> This is a database operation, in principle there is no los
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #43 from Mark Stoughton ---
This is a run with the boxes unchecked. Load time was down to 30 minutes
exactly
Last login: Thu Feb 10 12:53:11 on ttys000
markstoughton@Marks-Mac-mini ~ % export QT_LOGGING_RULES="digikam*
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #42 from Mark Stoughton ---
I unchecked the Settings-Collections I unchecked the box that says "Monitor the
ablbums for external changes(requires restart). Is that the right one? If
not, please direct me to the right one. Thanks.
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #38 from Mark Stoughton ---
After some use, the album switching got down to. fairly repeatable three
minutes, regardless of the number of photos in the album
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #37 from Mark Stoughton ---
I deactivated the monitor external changes and restarted. I saw no difference
in either startup time (40 minutes) or album switching (15 minutes).
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #36 from Mark Stoughton ---
It was activated. I'll try again after deactivating it
(In reply to Maik Qualmann from comment #34)
> I assume you have activated the option to monitor for external changes in
> the digiKam settings
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #35 from Mark Stoughton ---
I ran the debug session. I've annotated it because digicam stopped for several
minutes in different places along the way, and the log does not show the
pauses.
It took 41 minutes from start to finish
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #33 from Mark Stoughton ---
sorry for the slow reply. It's 10 minutes after the smash screen disappears.
The app shows up as non-responsive in Task manager in Windows or in Force Quit
on the Mac.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=405235
--- Comment #32 from Mark Stoughton ---
Hi,
It's from the time the splash screen disappears until the interface shows up.
During that time there is no indicator that Digikam is even running at all. The
photos were already imported. It shows up
https://bugs.kde.org/show_bug.cgi?id=405235
Mark Stoughton changed:
What|Removed |Added
Version|7.4.0 |7.5.0
CC
20 matches
Mail list logo