Created attachment 150063 [details] Screenshot of the message SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. At the start of digikam (since digiKam-7.7.0-20220620T060942-Win64.exe) a window appears with the notice: "Your locale has changed since this album was last opened. ..." The full message is given with the pic I've attached. One has to decide whether to click "yes" or "no". 2. 3. I don't understand the reason / background of this message and the respective results. Therefore I decided to switch back to the version of 2022/06/18. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
This is not a bug, click Ok. We now read the locales of the database, no longer the locales of the textencoding. Maik
The mentioned change of reading the current database encoding is actually not included in digiKam-7.7.0. However, a long-standing Qt bug that always returned "System" as the current text encoding under Windows has been fixed by Qt. Now the actually used code page is returned. Hence the message. This means that the message will appear again in digiKam-8.0.0. However, this message is purely informative and has no further influence in digiKam and can simply be confirmed with ok. Maik
(In reply to Maik Qualmann from comment #2) > The mentioned change of reading the current database encoding is actually > not included in digiKam-7.7.0. > However, a long-standing Qt bug that always returned "System" as the current > text encoding under Windows has been fixed by Qt. Now the actually used code > page is returned. Hence the message. > This means that the message will appear again in digiKam-8.0.0. > However, this message is purely informative and has no further influence in > digiKam and can simply be confirmed with ok. > > Maik Thank you for your explanation. Greetings Stephan
(In reply to Maik Qualmann from comment #2) > The mentioned change of reading the current database encoding is actually > not included in digiKam-7.7.0. > However, a long-standing Qt bug that always returned "System" as the current > text encoding under Windows has been fixed by Qt. Now the actually used code > page is returned. Hence the message. > This means that the message will appear again in digiKam-8.0.0. > However, this message is purely informative and has no further influence in > digiKam and can simply be confirmed with ok. > > Maik Unfortunately, I have to disagree. This effect acts as a blockade when using GPX data to subsequently add geodata to the images.
No, this change does not affect adding GPX data either. Can you describe your problem when adding GPX data? There is a change due to bug reports that the decimal separator (dot or comma) for GPS coordinates should match the locale. Maik
(In reply to Maik Qualmann from comment #5) > No, this change does not affect adding GPX data either. Can you describe > your problem when adding GPX data? > There is a change due to bug reports that the decimal separator (dot or > comma) for GPS coordinates should match the locale. > > Maik Thanks Maik. Here comes the overall picture. My configuration: Windows: 10 Pro / 21H2 / Build 19044.1806 / Region Germany / Format German / Date Time: ISO 8601: YYYY-MM-DD hh:mm:ss Digikam: 7.7.0 since 2022-07-08 (until version 7.6 the insertion of GPX data worked) GPX data: Garmin Oregon 600, alternatively 'GPS Logging App'@Android12 When installing digikam 7.7.0 I got a hint about changed code page: 'Old locale: System, new locale: windows-1252' (attachment, page 1). I did not understand what is meant by this and what to do. My Windows is installed as usual. When trying to add coordinates to photos using GPX data, the message came up "Correlation failed - No image could be correlated - please make sure time zone and time difference settings are correct." My understanding is that everything is set correctly in Windows. However, if digikam is meant, I don't know where to look.
I did not find the bug, but my digikam 7.7.0 works again regarding geodata entry in photos from GMX files. No further action is required. Sorry for my false report.
The error message actually says that the time information in the GPX file cannot be compared with that of the images because they are too different. Possible causes are in the error message (time zones) or in the wrong GPX file for the images. Maik