Bug 503892 - Database connection timeout or error after update to 8.6.0
Summary: Database connection timeout or error after update to 8.6.0
Status: RESOLVED DUPLICATE of bug 502858
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (other bugs)
Version First Reported In: 8.6.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-07 18:33 UTC by sendtoworthington
Modified: 2025-05-07 20:08 UTC (History)
1 user (show)

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


Attachments
attachment-2544985-0.html (2.08 KB, text/html)
2025-05-07 20:08 UTC, sendtoworthington
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sendtoworthington 2025-05-07 18:33:31 UTC
SUMMARY
When leaving system idle for period of time, the database connection appears corrupted or gets interrupted somehow, but the software does not give any error. Any tagging or metadata adjustments are not recorded to the database. Solution is to close the program and reload digikam from the kasmvnc viewer. The loss in connection to the database can be easily noted when viewing database statistics in the help menu - this become 0 for all entries when there is a database connection defect.

STEPS TO REPRODUCE
1. Open digikam
2. Leave idle for some period of time
3. View database statistics to see if values are shown as 0 (indicating no database connection and any metadata changes will not be recorded)

OBSERVED RESULT
Any changes to metadata will not synch to database / file after making metadata changes and the summary stats of the database will show 0

EXPECTED RESULT
normal operations

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Ubuntu with Docker
Comment 1 Maik Qualmann 2025-05-07 19:03:32 UTC
We haven't changed anything in digiKam that could have altered the behavior. Timeouts can be changed in the MySQL server.

Maik
Comment 2 Maik Qualmann 2025-05-07 19:04:10 UTC

*** This bug has been marked as a duplicate of bug 502858 ***
Comment 3 sendtoworthington 2025-05-07 20:08:55 UTC
Created attachment 181041 [details]
attachment-2544985-0.html

I see how this might be similar, however this behavior didn't exist with prior version. Also, I'm not having issues seeing images as per the other 'duplicate' bug report, just making any metadata changes are not stored. Also there's no error report or indication from digikam that the database is not accessible.

Thank you

May 7, 2025 2:04:13 PM Maik Qualmann <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=503892
> 
> Maik Qualmann <metzpinguin@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |RESOLVED
>          Resolution|---                         |DUPLICATE
> 
> --- Comment #2 from Maik Qualmann <metzpinguin@gmail.com> ---
> 
> 
> *** This bug has been marked as a duplicate of bug 502858 ***
> 
> -- 
> You are receiving this mail because:
> You reported the bug.