SUMMARY Into Geolocation-Correlator, opening a folder in order to load a gpx file freezes Digikam if this folder contains a json file (any suffixed .json file, even empty). STEPS TO REPRODUCE 1. Add a json file into a folder (any filename, any content) 2. Go to Geoloaction-Correlator 3. Load a GPX file 4. Open the folder containing the json file OBSERVED RESULT at step 4, Digikam freezes EXPECTED RESULT List of the gpx files eventually present in the folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.7-1-MANJARO (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Report made with digiKam-8.3.0-20240312T172522-x86-64.appimage (2024-03-12 17:39)
Why would a *.json file that doesn't load at all cause this? I can't reproduce it either. Please send me the GPX file with which the problem occurs. Maik
I'm currently on Windows, do I understand correctly that when I open the file selector it freezes? Maik
It freezes when opening the file selector and navigate to a folder which contains a json file. The folder is displayed empty (even it contains gpx files) and Digikam freezes.
(In reply to Maik Qualmann from comment #1) > Why would a *.json file that doesn't load at all cause this? I can't > reproduce it either. Please send me the GPX file with which the problem > occurs. Sorry for my bad description. Here, step 3 "Load a GPX file" means Click on the "Load a GPX file" button.
Hmm, I'll test it on Linux later. The AppImage uses the Qt file selector, not a native one from the system. Maik
Just to be sure I tested the same scenario with Digikam 8.2 ("normal" version, not appimage) : no problem.
One more info : it is a loop (Digikam uses 100% cpu).
No problem here with the current AppImage bundle. i get a json files sample from there : https://microsoftedge.github.io/Demos/json-dummy-data/ .. and open the file dialog where the JSon file is stored. No dysfunction under Kubuntu 22.04 / 23.04 / 23.10 Gilles Caulier
> No dysfunction under Kubuntu 22.04 / 23.04 / 23.10. You had the same luck under Ubuntu with "the Freeze (loop ?) when right click on an image" bug.
Created attachment 167098 [details] backtrace from digiKam-8.3.0-20240312T172522-x86-64-debug.appimage bundle
I can't reproduce the problem here with the AppImage under openSUSE. But I had already suspected that it was related to the QFileIconProvider, although a *.gpx filter is set, an icon is probably searched for all files in the directory. As far as I know, the standard implementation only creates a generic icon based on the QMimeDatabase. Gilles, have you reset the last changes to the Mimi Types files? Maik
I built a live USB from the last Manjaro ISO in order to test with a fresh and clean install : I cannot reproduce the problem. So, I suspect there is may be something broken on my system, even if all but Digikam.appimage seems run without problem. Maik, you told about QMimeDatabase ; is there something I can check on my system ? Or may be something to delete to force the OS to rebuild it ?
I see that I have a folder into /home/michel/.local/share/icons which does not exist on the /home/user/.local/share related to my live usb. This folder contains others folders, all of them dozen of files such as appimagekit_0b91f7e6b589f1e5743d8c3bea4a4517_digikam. I suspect each time I have crashed digikam.appimage (for example to test "Freeze (loop ?) when right click on an image" problem), these files were not cleaned. Finally, is there a possibility that previous crashes have left things uncleaned that could be the cause of the present problem ?
Maik, No, The mime file database in the bundle is not yet reset to the previous version. Gilles
Problem fixed doing : update-mime-database ~/.local/share/mime I have no idea why. May be some "corruption" resulting of many killing digikam.appimage after a freeze/loop ?
digiKam do not touch this file in your home directory. Gilles Caulier
To tell the truth, I have also deleted many files in .cache and digikam.appimage related icons (I know, always make only one change at a time to debug...) so I am not absolutely sure that is the update-mime-database ~/.local/share/mime which solve the problem. And above all, remember that I tested the same scenario with Digikam 8.2 ("normal" version) AFTER I discovered the problem with the 8.3 appimage version : there was no problem. But even if it remains a bit of a mystery to me, there's indeed nothing else to do but close this report.