[digikam] [Bug 451221] New: Cannot start digicam
Jan Steinman
bugzilla_noreply at kde.org
Mon Mar 7 04:55:30 GMT 2022
https://bugs.kde.org/show_bug.cgi?id=451221
Bug ID: 451221
Summary: Cannot start digicam
Product: digikam
Version: unspecified
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
Severity: critical
Priority: NOR
Component: Database-Schema
Assignee: digikam-bugs-null at kde.org
Reporter: jan.steinman at gmail.com
Target Milestone: ---
Created attachment 147338
--> https://bugs.kde.org/attachment.cgi?id=147338&action=edit
Two dialogs left on the screen upon startup of digikam.
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Double-click digicam.app in the Finder.
OBSERVED RESULT
Database (mariadb on localhost) fails to update, according to message, and
hangs forever.
EXPECTED RESULT
digikam runs
SOFTWARE/OS VERSIONS
Windows:
macOS: 10.15.7 (Catalina latest)
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
I have not used DigiKam for some time. I upgraded MariaDB from 10.4 to 10.6
(latest). When I attempt to run it, I get the following message: "Failed to
update the database schema from version 12 to version 13.
Please read the error messages printed on the console and report this error as
a bug at bugs.kde.org."
No error messages appear in the system console. Besides the error dialog,
digikam The last thing in MariaDB's error log is: "2022-03-06 19:35:39 135
[Warning] Aborted connection 135 to db: 'DigiKam-Core' user: 'DigiKam' host:
'localhost' (Got an error reading communication packets)"
My max_allowed_packet is set to 499,999,744, because I recently restored an
email database that was losing connection until I boosted max_allowed_packet.
Should I reduce that number? I have 56GB of RAM on an older MacPro 4,1.
Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
More information about the kde-mac
mailing list