https://bugs.kde.org/show_bug.cgi?id=524946
--- Comment #5 from kidakeh <[email protected]> --- Thank you Maik and Gilles for your replies. Following Maik's suggestion, I checked the time zone configuration. Here are the complete test results: 1. Windows system time zone (client) C:\> time /t 16:25 C:\> tzutil /g China Standard Time 2. MariaDB server time zone MariaDB [(none)]> SHOW VARIABLES LIKE '%time_zone%'; +------------------+---------------+ | Variable_name | Value | +------------------+---------------+ | system_time_zone | Asia/Shanghai | | time_zone | SYSTEM | +------------------+---------------+ MariaDB [(none)]> SELECT @@GLOBAL.time_zone, @@SESSION.time_zone; +--------------------+---------------------+ | @@GLOBAL.time_zone | @@SESSION.time_zone | +--------------------+---------------------+ | SYSTEM | SYSTEM | +--------------------+---------------------+ MariaDB [(none)]> SELECT NOW(); +---------------------+ | NOW() | +---------------------+ | 2026-08-31 16:25:39 | +---------------------+ Can you confirm that the server and client are using the same time zone, and that this issue is not caused by time zone misconfiguration? 3. Database backend information Database internal server: Yes Database backend version: 10.11.19-MariaDB-log Database backend: QMYSQL Question for Gilles: Based on your earlier reply, may I confirm that the only way to fix this issue is to wait for digiKam to be rebuilt with libmariadb? Thank you! -- You are receiving this mail because: You are watching all bug changes.
