Re: Collections are suddenly gone in DK

I have just tried installing the 8.8.0 with debug.

It made no difference. Entire 2025 and part of 2024 is still gone.


Would it make sense to produce a log file from this DK?


Would I need to recreate all my database? :(


BR

Thomas


On 14/09/2025 19.14, Maik Qualmann wrote:
> The problem is, even if digiKam couldn't read the collection for some reason,
> the root album names should still be displayed. But you don't have them,
> right?
>
> Your log doesn't show any anomalies or error messages from the database. But I
> can only imagine some kind of database problem.
>
> If you haven’t already, please try the digiKam-8.8.0 pre-release version from
> here: https://files.kde.org/digikam/
>
> Maik
>
> Am Sonntag, 14. September 2025, 19:05:00 Mitteleuropäische Sommerzeit schrieb
> Thomas:
>> Hi,
>>
>>
>> This is Apple Silicon M3.
>>
>> MacOS version 15.6.1.
>>
>> The volumes are mounted. I can ls the contents from a terminal and I can
>> open the images int he Finder file browser.
>>
>> I will check Apple Console app although, I am not sure what to look for?
>>
>>
>> BR
>>
>> Thomas
>>
>> On 14/09/2025 04.06, Gilles Caulier wrote:
>>> Hi,
>>>
>>> Right it's MacOS. Which version ? Arm or Intel.
>>>
>>> Perhaps the disk is unmounted by the system ? Did you see something
>>> abnormal in the system log (Apple Console Application)?
>>>
>>> Best regards
>>>
>>> Gilles Caulier
>>>
>>> Le sam. 13 sept. 2025 à 14:57, Thomas <[email protected]> a écrit :
>>>> On 12/09/2025 17.52, Gilles Caulier wrote:
>>>>
>>>> I'm 99% sure that something in your Windows installation locks the
>>>> database or the application or the file system. This introduces giant
>>>> time latency in the program. This can be the Windows update running in
>>>> background, an antivirus, or a malfunction with your hardware.
>>>>
>>>> Another issue can be the file path scheme name in your collection
>>>> which cause dysfunction, eg. no latin1 char encoding for ex, even if
>>>> digiKam supports UTF8 and the application manifest for Windows sets
>>>> these properties at run time.
>>>>
>>>> In my office we switch from WIN10 to WIN11 progressively on all
>>>> desktop computers, and we sometimes see troubles with file paths when
>>>> we use company applications (where WIN10 has no problem for a very
>>>> long time). This is difficult to investigate and to reproduce. This is
>>>> especially true with the network file systems but not with all users.
>>>> The reason is not clear...
>>>>
>>>>
>>>> This is macOS - not Windows.
>>>>
>>>> I don't think something is locking my files and I have tried over
>>>> multiple restarts.
>>>>
>>>> I will try to see if I can figure out how to see which files are locked
>>>> on macOS.
>>>>
>>>> There is no antivirus.
>>>>
>>>>
>>>> Also, all files on this file system should be plain ascii compatible as I
>>>> ensure files only have names in the set "A-Za-z0-9._, -()+"
>>>>
>>>>
>>>> Any ideas how to troubleshoot this further?
>
>
>