Empty timeline view, empty dates view - but can search for dates?

[Christian Haul]

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


On 12/27/25 9:31 PM, Christian Haul wrote:
> Thanks for all the support. I'm away from my computer for the weekend and will report back on Monday.
> 
> Chris.
> 
> 
> Am 27. Dezember 2025 21:26:34 MEZ schrieb Maik Qualmann <metzpinguin at gmail.com>:
> 
>     The problem seems to only occur with MariaDB; a locale issue is conceivable.
>     However, I can't explain why it only affects the date and timeline view. I did
>     make a change for the upcoming digiKam-9.0.0, but the result should be the
>     same.
> 
>     @Christian, could you please try starting digiKam with a different locale:
> 
>     LANG=C digikam
>     or
>     LANG=de_DE digikam
> 
>     Maik
> 
>     Am Samstag, 27. Dezember 2025, 20:53:07 Mitteleuropäische Normalzeit schrieb
>     Steven Robbins:
> 
>         First: thanks, Christian for posting about this!
> 
>         On Friday, December 26, 2025 9:22:17 a.m. Central Standard Time Maik
>         Qualmann
>         wrote:
> 
>             We received this bug report:
> 
>             https://bugs.kde.org/show_bug.cgi?id=511229 <https://bugs.kde.org/show_bug.cgi?id=511229>
> 
>             The solution for the user was to use the digiKam AppImage.
>             One would have to dig deeper into Debian to see if they've patched
>             anything.
> 
>         I'm the debian maintainer for Digikam. I can confirm that there are no
>         patches made to digikam sources per se. There are presently just two
>         patches, both to the build system: one to disable the configuration probe
>         for jasper and one to ensure stuff that links with libdng also links with
>         libatomic. Both are Debian-specific needs, to the best of my knowledge.
> 
>             Am Freitag, 26. Dezember 2025, 15:58:39 Mitteleuropäische Normalzeit
>             schrieb>
>             Christian Haul:
> 
>                 Hi list,
> 
>                 I have been using digikam for ages now but at some point the timeline
>                 view
>                 (and the dates view) suddenly became empty. I have checked with the DB
>                 (MariaDB) that dates are included, also they are properly shown in the
>                 overview and I can even search for pictures in a timeframe.
> 
>                 I have no clue what might be a reason for this.
> 
> 
>         I am sorry the feature isn't working for you. I don't have any theory as to
>         why. However, I can confirm that both are still working on my Debian
>         system. I'm running a very up-to-date "unstable" debian with KDE and
>         Digikam 8.8.0-2 configured for the SQLite database.
> 
>                 I'm running mostly on gnome on debian unstable but using plasma or Xfce
>                 doesn't change a thing. I'm aware that unstable occasionally breaks
>                 things
>                 but this issue persists now for a longer time so I'm afraid it's
>                 probably
>                 some local configuration issue.
> 
> 
>         Since you are running unstable, there is a possibility it is a package
>         issue. I know from first-hand experience that there have been some hiccups
>         with the recent KDE/Plasma 6 upgrades, as evidenced by the long threads on
>         the topic; e.g. https://lists.debian.org/debian-kde/2025/10/msg00031.html <https://lists.debian.org/debian-
>         kde/2025/10/msg00031.html>
> 
>         And there's a wiki page https://wiki.debian.org/Plasma%206 <https://wiki.debian.org/Plasma%206>
> 
>         I think I got past my upgrade issues by manually installing packages that
>         seemed connected to kde/plasma 6.
> 
>         -Steve