https://bugs.kde.org/show_bug.cgi?id=430949
Bug ID: 430949
Summary: digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing
local MySQL/MariaDB instances on upgrade
Product: digikam
Version: 7.2.0
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
Severity: major
Priority: NOR
Component: Setup-Misc
Assignee: digikam-bugs-n...@kde.org
Reporter: hackintos...@posteo.eu
Target Milestone: ---
SUMMARY
On my MacBook Pro (17" MacBookPro5,2, macOS 10.14.6 with Security Upddate
2020-007) the upgrade from digiKam 7.2.0-beta2-20201219T112949 to digiKam 7.2.0
(official beta2 released today) has broken the MySQL / MariaDB backend.
After analyzing the issue I suspect this is caused by the installer moving the
MariaDB binaries from /opt/digikam/lib/mariadb/bin/ to some place inside the
digikam.app in digiKam-7.2.0-beta2 while obviously NOT upgrading the MySQL /
MariaDB path variables in /Users/$user/Library/preferences/digikamrc.
STEPS TO REPRODUCE
1. Create a digiKam 7.1 installation using the local MySQL / MariaDB database
variant. Launch digiKam and make sure it works.
2. Upgrade to the just release digiKam 7.2.0-beta2.
3. After the digiKam 7.2.0-beta2 is finished, launch digiKam.
OBSERVED RESULT
digiKam can't launch the local MySQL daemon and the whole launch fails as a
consequence.
EXPECTED RESULT
digiKam should launch normally.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
