Empty timeline view, empty dates view - but can search for dates?
Gilles Caulier
caulier.gilles at gmail.com
Mon Dec 29 20:11:01 GMT 2025
Le lun. 29 déc. 2025 à 19:54, Christian Haul <c.haul at web.de> a écrit :
>
> Tried different settings.
>
> LANG=C.UTF-8
> LANG=de_DE.UTF-8
> LANG=C.UTF-8 LC_TYPE=C.UTF-8
> LANG=de_DE.UTF-8 LC_TYPE=de_DE.UTF-8
>
> still both date and timeline views are empty.
>
> I looked at the QTSQL connection properties
> https://doc.qt.io/qt-6/sql-driver.html#qmysql-for-mysql-or-mariadb-5-6-and-higher but nothing appeared to be relevant.
>
> DB reports version "11.8.5-MariaDB-2+b2 from Debian". Happy to lookup and report other DB config vars - but since the
> server reports hundreds, these are the ones related to locales.
>
> character_set_client utf8mb4
> character_set_collations
> utf8mb3=utf8mb3_uca1400_ai_ci,ucs2=ucs2_uca1400_ai_ci,utf8mb4=utf8mb4_uca1400_ai_ci,utf16=utf16_uca1400_ai_ci,utf32=utf32_uca1400_ai_ci
> character_set_connection utf8mb4
> character_set_database utf8mb4
> character_set_filesystem binary
> character_set_results utf8mb4
> character_set_server utf8mb4
> character_set_system utf8mb3
> character_sets_dir /usr/share/mariadb/charsets/
> check_constraint_checks ON
> collation_connection utf8mb4_uca1400_ai_ci
> collation_database utf8mb4_uca1400_ai_ci
> collation_server utf8mb4_uca1400_ai_ci
>
> lc_messages en_US
> lc_messages_dir
> lc_time_names en_US
>
>
> From digikam output (db related)
>
> digikam.general: AlbumWatch use QFileSystemWatcher
> digikam.general: Database Parameters:
> Type: "QMYSQL"
> DB Core Name: "digikam"
> DB Thumbs Name: "digikam"
> DB Face Name: "digikam"
> DB Similarity Name: "digikam"
> Connect Options: ""
> Host Name: "cube.fritz.box"
> Host Port: 3306
> WAL Mode: false
> Internal Server: false
> Internal Server Path: ""
> Internal Server Init Cmd: ""
> Internal Server Admin Cmd: ""
> Internal Server Program Cmd: ""
> Internal Server Upgrade Cmd: ""
> Username: "digikam"
> Password: "XXXXXXXXXXXXXXXXXXXXXXXX"
>
> digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml"
> digikam.dbengine: Checking XML version ID => expected: 3 found: 3
> digikam.coredb: Core database: running schema update
> digikam.coredb: Core database: have a structure version 16
> digikam.coredb: Core database: makeUpdates 16 to 16
> digikam.database: Creating new Location "/" uuid
> "networkshareid:?mountpath=/archive/images&fileuuid=9f574255-317a-48db-909c-111435d8ded6"
> digikam.database: Found Location "/archive/images" with file uuid "9f574255..."
> digikam.database: Location for "/archive/images" is available: true => case sensitivity: 2
> digikam.general: Allowing a cache size of 1024 MB
> digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
> digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
> digikam.thumbsdb: Thumbs database: have a structure version "3"
> digikam.general: Thumbnails database ready for use
> digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
> digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
> digikam.similaritydb: Similarity database: have a structure version "1"
> digikam.similaritydb: Similarity database ready for use
> digikam.dimg: QList("/usr/share/color/icc", "/home/chris/.local/share/icc")
> digikam.dimg: ICM Desktop: looking for the monitor color profile...
> digikam.dimg: ICM Wayland: check the monitor profile for screen 0
> digikam.dimg: ICM Wayland: the device is not a screen: "/org/freedesktop/ColorManager/devices/sysfs_Canon_CanoScan"
> digikam.dnnmodelmanager: Using default backend and CPU target
> digikam.autorotate: AutoRotate model ready
> digikam.facedb: FaceDB SelectFaceSetting val ret = 0
> digikam.facedb: FaceDB SelectFaceSetting val ret = 0
> digikam.facedb: Face database: have a structure version "6"
>
>
>
> Likely unrelated, the internal log produces tons of the following
>
> digikam.dimg: ICM Wayland: check the monitor profile for screen 0
> digikam.dimg: ICM Wayland: the device is not a screen: "/org/freedesktop/ColorManager/devices/sysfs_Canon_CanoScan"
> digikam.dimg: ICM Desktop: looking for the monitor color profile...
> digikam.dimg: ICM Wayland: check the monitor profile for screen 0
>
I suspect a problem with the monitor profile cache mechanism in ICC
profile manager from digiKam.
Gilles Caulier
More information about the Digikam-users
mailing list