Bug 508579 - Database and Storage access failure - see log
Summary: Database and Storage access failure - see log
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-AppImage (other bugs)
Version First Reported In: 8.7.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-22 00:25 UTC by sendtoworthington
Modified: 2025-09-22 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Log for digikam (129.24 KB, text/plain)
2025-08-22 08:50 UTC, sendtoworthington
Details
Debug log (120.43 KB, text/plain)
2025-08-23 01:21 UTC, sendtoworthington
Details
attachment-469131-0.html (2.16 KB, text/html)
2025-08-23 21:37 UTC, sendtoworthington
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sendtoworthington 2025-08-22 00:25:30 UTC
SUMMARY
After delay of using Digikam, access to files and database information is unavailable. Files show 0B and any rename / move command completes, but nothing is actually performed in the filesystem (quick crash). I am using Digikam in Docker environment and issue started in 8.5 or 8.6 and persisted.


STEPS TO REPRODUCE
1. Run Digikam
2. Leave idle for XX amount of time
3. Attempt to tag images, check file properties (size) or move / rename


OBSERVED RESULT
4. Observe no action performed or 0B files for image.

EXPECTED RESULT
Action to be performed as requested

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Using docker digikam
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty
unknown: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" 
 "Not connected to D-Bus server"
unknown: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" 
 "Not connected to D-Bus server"
unknown: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
unknown: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
unknown: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
unknown: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
Comment 1 sendtoworthington 2025-08-22 00:34:00 UTC
Additional Log -
2025-08-22T00:28:29.632138630Z -- digiKam Linux AppImage Bundle
2025-08-22T00:28:29.632163180Z -- Use 'help' as CLI argument to know all available options for digiKam application.
2025-08-22T00:28:29.632166980Z -- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
2025-08-22T00:28:29.632170046Z --        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
2025-08-22T00:28:29.632173227Z --        to extract the bundle contents locally, use option '--appimage-extract' on the command line.
2025-08-22T00:28:29.648277722Z -- Detected host Linux Debian GNU/Linux-64-12.11
2025-08-22T00:28:29.651554881Z -- AppImage mounted directory: /opt/digikam
2025-08-22T00:28:29.652741325Z Preloading skipped for libudev.so.0
2025-08-22T00:28:29.654277263Z Preloading             /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
2025-08-22T00:28:29.654421780Z Preloading skipped for libcrypto.so.1.1
2025-08-22T00:28:29.654504348Z Preloading skipped for libssl.so.1.1
2025-08-22T00:28:29.657054116Z Preloading             /usr/lib/x86_64-linux-gnu/libnss3.so
2025-08-22T00:28:29.659228707Z Preloading             /usr/lib/x86_64-linux-gnu/libnssutil3.so
2025-08-22T00:28:29.661605206Z Preloading             /usr/lib/x86_64-linux-gnu/libsmime3.so
2025-08-22T00:28:29.664926636Z Preloading             /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
2025-08-22T00:28:29.670577371Z Preloading             /usr/lib/x86_64-linux-gnu/libgnutls.so.30
2025-08-22T00:28:29.675535745Z Preloading             /usr/lib/x86_64-linux-gnu/libnettle.so.8
2025-08-22T00:28:29.675580877Z -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linux-gnu/libgnutls.so.30:/usr/lib/x86_64-linux-gnu/libnettle.so.8
2025-08-22T00:28:29.840222170Z [34mDigikam::DXmlGuiWindow::setupIconTheme[0m: Breeze icons resource file found
2025-08-22T00:28:29.841032002Z [34mDigikam::unloadQtTranslationFiles[0m: Qt standard translations removed: 4
2025-08-22T00:28:29.841060873Z [34mDigikam::loadStdQtTranslationFiles[0m: Qt standard translations path: "/opt/digikam/usr/share/digikam/translations"
2025-08-22T00:28:29.841281456Z [34mDigikam::loadStdQtTranslationFiles[0m: Loaded Qt standard translations "en_US" from catalog "qt"
2025-08-22T00:28:29.841500139Z [34mDigikam::loadStdQtTranslationFiles[0m: Loaded Qt standard translations "en_US" from catalog "qtbase"
2025-08-22T00:28:29.841659937Z [34mDigikam::loadStdQtTranslationFiles[0m: Loaded Qt standard translations "en_US" from catalog "qtdeclarative"
2025-08-22T00:28:29.842079356Z [34mDigikam::loadStdQtTranslationFiles[0m: Loaded Qt standard translations "en_US" from catalog "qtwebengine"
2025-08-22T00:28:29.842280751Z [34mDigikam::loadEcmQtTranslationFiles[0m: Loaded Qt ECM translations "en" from catalog "kcoreaddons6_qt"
2025-08-22T00:28:29.842425547Z [34mDigikam::loadEcmQtTranslationFiles[0m: Loaded Qt ECM translations "en" from catalog "kwidgetsaddons6_qt"
2025-08-22T00:28:29.845681357Z [34mDigikam::ApplicationSettings::setApplicationFont[0m: Switch to application font:  QFont(Sans Serif,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1)
2025-08-22T00:28:29.845884174Z [34mDigikam::AlbumWatch::AlbumWatch[0m: AlbumWatch is disabled
2025-08-22T00:28:29.868049310Z [34mDigikam::AlbumManager::setDatabase[0m: Database Parameters:
2025-08-22T00:28:29.868090815Z    Type:                        "QMYSQL"
2025-08-22T00:28:29.868095775Z    DB Core Name:                "digikam"
2025-08-22T00:28:29.868099341Z    DB Thumbs Name:              "digikam-thumbnails"
2025-08-22T00:28:29.868103668Z    DB Face Name:                "digikam-recognition"
2025-08-22T00:28:29.868107383Z    DB Similarity Name:          "digikam-similar"
2025-08-22T00:28:29.868112332Z    Connect Options:             ""
2025-08-22T00:28:29.868116062Z    Host Name:                   "mariadb"
2025-08-22T00:28:29.868119277Z    Host Port:                   3306
2025-08-22T00:28:29.868122812Z    WAL Mode:                    false
2025-08-22T00:28:29.868125670Z    Internal Server:             false
2025-08-22T00:28:29.868129163Z    Internal Server Path:        ""
2025-08-22T00:28:29.868133118Z    Internal Server Init Cmd:    ""
2025-08-22T00:28:29.868137017Z    Internal Server Admin Cmd:   ""
2025-08-22T00:28:29.868141106Z    Internal Server Program Cmd: ""
2025-08-22T00:28:29.868144504Z    Internal Server Upgrade Cmd: ""
2025-08-22T00:28:29.868148019Z    Username:                    "digikam_user"
2025-08-22T00:28:29.868170411Z    Password:                    "XXXXXXXXXXXX"
2025-08-22T00:28:29.868175515Z 
2025-08-22T00:28:29.902111579Z [34munknown[0m: QSvgHandler: Image filename is empty
2025-08-22T00:28:29.902140102Z [34munknown[0m: QSvgHandler: Image filename is empty
2025-08-22T00:28:29.937027179Z [34mDigikam::DbEngineConfigSettingsLoader::readConfig[0m: Loading SQL code from config file "/opt/digikam/usr/share/digikam/database/dbconfig.xml"
2025-08-22T00:28:29.941302191Z [34mDigikam::DbEngineConfigSettingsLoader::readConfig[0m: Checking XML version ID => expected:  3  found:  3
2025-08-22T00:28:29.950845479Z [34mDigikam::CoreDbSchemaUpdater::update[0m: Core database: running schema update
2025-08-22T00:28:29.996077388Z [34mDigikam::CoreDbSchemaUpdater::startUpdates[0m: Core database: have a structure version  16
2025-08-22T00:28:29.996103860Z [34mDigikam::CoreDbSchemaUpdater::makeUpdates[0m: Core database: makeUpdates  16  to  16
2025-08-22T00:28:30.000516237Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/Originals&fileuuid=05068f77-fc15-415a-ae8e-1e30cf60c810"
2025-08-22T00:28:30.000544287Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/EXPORT&fileuuid=c1c98d69-b0d7-4e59-9a0a-3c5a8547fa36"
2025-08-22T00:28:30.000548982Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/SORTED&fileuuid=29c1a243-7fe1-471b-80c2-27e03d78db49"
2025-08-22T00:28:30.000552316Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/UNSORTED&fileuuid=d797436a-d2ac-4b73-a9cf-1f5aafba571e"
2025-08-22T00:28:30.000556421Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/RAW&fileuuid=f4113c18-f27c-4f90-8e01-42f0748fcab3"
2025-08-22T00:28:30.000559705Z [34mDigikam::AlbumRootLocation::AlbumRootLocation[0m: Creating new Location  "/"  uuid  "volumeid:?path=/config/Pictures/Import&fileuuid=df543e5d-fcab-4c8e-908d-2c71f0c65055"
2025-08-22T00:28:30.000803977Z [34munknown[0m: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" 
2025-08-22T00:28:30.000819523Z  "Not connected to D-Bus server"
2025-08-22T00:28:30.000822711Z [34munknown[0m: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" 
2025-08-22T00:28:30.000825643Z  "Not connected to D-Bus server"
2025-08-22T00:28:30.000904246Z [34munknown[0m: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
2025-08-22T00:28:30.000918022Z [34munknown[0m: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
2025-08-22T00:28:30.001024849Z [34munknown[0m: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
2025-08-22T00:28:30.001053386Z [34munknown[0m: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
2025-08-22T00:28:30.003159303Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/Originals" is available: true => case sensitivity: 1
2025-08-22T00:28:30.004489616Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/EXPORT" is available: true => case sensitivity: 1
2025-08-22T00:28:30.005976282Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/SORTED" is available: true => case sensitivity: 1
2025-08-22T00:28:30.007478064Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/UNSORTED" is available: true => case sensitivity: 1
2025-08-22T00:28:30.008844885Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/RAW" is available: true => case sensitivity: 1
2025-08-22T00:28:30.010524771Z [34mDigikam::CollectionManager::updateLocations[0m: Location for "/config/Pictures/Import" is available: true => case sensitivity: 1
Comment 2 Maik Qualmann 2025-08-22 06:03:24 UTC
The messages in the log that you probably consider errors are currently normal. For example, from the Solid backend, code that was probably changed during the port to Q6 and hasn't been cleaned up yet.

Otherwise, it would be good to see a complete log, including a file operation.

The AppImage log shows no errors; your core DB is found, and your collection is also recognized as available.

Please post a complete log.

Maik
Comment 3 sendtoworthington 2025-08-22 08:46:18 UTC
(In reply to Maik Qualmann from comment #2)
> The messages in the log that you probably consider errors are currently
> normal. For example, from the Solid backend, code that was probably changed
> during the port to Q6 and hasn't been cleaned up yet.
> 
> Otherwise, it would be good to see a complete log, including a file
> operation.
> 
> The AppImage log shows no errors; your core DB is found, and your collection
> is also recognized as available.
> 
> Please post a complete log.
> 
> Maik

Please see below complete log.

Everytime you see "digiKam Linux AppImage Bundle" -THAT is when I manually closed the app in the vnc viewer and restarted it. That has been my only solution to get the app to work again.
Comment 4 sendtoworthington 2025-08-22 08:50:56 UTC
Created attachment 184331 [details]
Log for digikam

Everytime you see "-- digiKam Linux AppImage Bundle" is when I restarted the program in the vnc window to get it working again.
Comment 5 Maik Qualmann 2025-08-22 10:17:16 UTC
This whole VNC connection thing is complicated anyway; Qt6 requires OpenGL. Please enable the use of software OpenGL in the digiKam settings under Miscellaneous -> System.
I also see that your drives are unmounting?
Please also enable debugging in the digiKam settings under Miscellaneous -> System. Currently, we only see warnings in the log, but we also need the debug messages.
Please create a new log in that case.

Maik
Comment 6 sendtoworthington 2025-08-23 01:20:32 UTC
(In reply to Maik Qualmann from comment #5)
> This whole VNC connection thing is complicated anyway; Qt6 requires OpenGL.
> Please enable the use of software OpenGL in the digiKam settings under
> Miscellaneous -> System.
> I also see that your drives are unmounting?
> Please also enable debugging in the digiKam settings under Miscellaneous ->
> System. Currently, we only see warnings in the log, but we also need the
> debug messages.
> Please create a new log in that case.
> 
> Maik

Hi. Please see attached updated log. I did activate the debug logging feature and I pull logs using Dozzle. If this is not sufficient, please let me know what else I can do to obtain the kind of log file that would better help get to the bottom of this matter.
Comment 7 sendtoworthington 2025-08-23 01:21:14 UTC
Created attachment 184366 [details]
Debug log


Hi. Please see attached updated log. I did activate the debug logging feature and I pull logs using Dozzle. If this is not sufficient, please let me know what else I can do to obtain the kind of log file that would better help get to the bottom of this matter.
Comment 8 caulier.gilles 2025-08-23 05:40:56 UTC
What's happen with your Mysql database?

...
2025-08-23T01:03:40.143973464Z [34mDigikam::BdEngineBackendPrivate::debugOutputFailedQuery[0m: Failure executing query:
2025-08-23T01:03:40.143983803Z  "SELECT aspectRatio, audioBitRate, audioChannelType, audioCompressor, duration, frameRate, videoCodec FROM VideoMetadata WHERE imageid=12153;" 
2025-08-23T01:03:40.143994868Z Error messages: "QMYSQL: Unable to execute query" "Lost connection to MySQL server during query" "2013" 2 
2025-08-23T01:03:40.144005670Z Bound values:  QList(QVariant(qlonglong, 12153))
2025-08-23T01:03:40.156217943Z [34mDigikam::BdEngineBackendPrivate::debugOutputFailedQuery[0m: Failure executing query:
2025-08-23T01:03:40.156273050Z  "SELECT property, value, extraValue FROM ImageCopyright WHERE imageid=?;" 
2025-08-23T01:03:40.156291370Z Error messages: "QMYSQL: Unable to prepare statement" "Lost connection to MySQL server during query" "2013" 2 
2025-08-23T01:03:40.156305478Z Bound values:  QList()
2025-08-23T01:03:40.156316608Z [34mDigikam::BdEngineBackendPrivate::debugOutputFailedQuery[0m: Failure executing query:
2025-08-23T01:03:40.156329462Z  "SELECT property, value, extraValue FROM ImageCopyright WHERE imageid=12153;" 
2025-08-23T01:03:40.156343395Z Error messages: "QMYSQL: Unable to execute query" "Lost connection to MySQL server during query" "2013" 2 
2025-08-23T01:03:40.156357220Z Bound values:  QList(QVariant(qlonglong, 12153))
2025-08-23T01:03:40.156369068Z [34mDigikam::BdEngineBackendPrivate::debugOutputFailedQuery[0m: Failure executing query:
2025-08-23T01:03:40.156377477Z  "SELECT value FROM ImageProperties WHERE imageid=? AND property=?;" 
2025-08-23T01:03:40.156386258Z Error messages: "QMYSQL: Unable to prepare statement" "Lost connection to MySQL server during query" "2013" 2 
...
Comment 9 Maik Qualmann 2025-08-23 05:56:07 UTC
Okay, initially everything looks fine, including scanning items and creating thumbnails.
Then there's a debug message that doesn't come from digiKam:

> 2025-08-22 05:33:56,112 [PRIO] Connections: closed: @67.184.250.174_1755854993.673217::websocket (Clean disconnection)
> 2025-08-22 20:03:35,465 [INFO] websocket 3: got client connection from 127.0.0.1
> 2025-08-22 20:03:35,477 [PRIO] Connections: accepted: @73.44.161.199_1755911015.468195::websocket

After that, digiKam immediately loses the connection to the MySQL database:

> Error messages: "QMYSQL: Unable to prepare statement" "Lost connection to MySQL server during query" "2013" 2 

I think you need to contact the team that creates and manages the Docker image.

Maik
Comment 10 sendtoworthington 2025-08-23 21:37:39 UTC
Created attachment 184390 [details]
attachment-469131-0.html

I'll check the timestamps, but I think this particular time might have been a coincidence. Usually the failure is while I'm using the system. It's an interesting thought and I'm going to look into how connected the instances are.

Thank you!

Aug 23, 2025 12:56:10 AM Maik Qualmann <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=508579
> 
> --- Comment #9 from Maik Qualmann <metzpinguin@gmail.com> ---
> Okay, initially everything looks fine, including scanning items and creating
> thumbnails.
> Then there's a debug message that doesn't come from digiKam:
> 
>> 2025-08-22 05:33:56,112 [PRIO] Connections: closed: @67.184.250.174_1755854993.673217::websocket (Clean disconnection)
>> 2025-08-22 20:03:35,465 [INFO] websocket 3: got client connection from 127.0.0.1
>> 2025-08-22 20:03:35,477 [PRIO] Connections: accepted: @73.44.161.199_1755911015.468195::websocket
> 
> After that, digiKam immediately loses the connection to the MySQL database:
> 
>> Error messages: "QMYSQL: Unable to prepare statement" "Lost connection to MySQL server during query" "2013" 2
> 
> I think you need to contact the team that creates and manages the Docker image.
> 
> Maik
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 11 Bug Janitor Service 2025-09-07 03:48:16 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2025-09-22 03:46:58 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.