[digikam] [Bug 467505] When launching the latest version of digiKam, the old internal MySql database cannot be started.

[Felipe]

https://bugs.kde.org/show_bug.cgi?id=467505

--- Comment #14 from Felipe <fmontagut at gmail.com> ---
The error persists in version 8.7.0.

I found the issue. During the initialization phase the mariadb command has an
argument with a "//" that is incorrect. The correct argument should be:
"--basedir=/Applications/digiKam.org/digikam.app/Contents/lib/mariadb/" and the
current code generates two // between Contents and lib.

I am not developer but searched through the code, and the issue might be on
databaseserver.cpp, look how the argument is generated on lines 522 and 568: 
mysqldServCmdArgs <<
QDir::toNativeSeparators(QString::fromLatin1("--basedir=%1/lib/mariadb/").
Looking other codelines, the output of macOSBundlePrefix always finish with
"/", and combining both you get the wrong "..Contents//lib/... path.

I added an attachment to see the error string, and a screenshot of the search I
used to find the potential typo in the code

-- 
You are receiving this mail because:
You are watching all bug changes.