[Digikam-devel] [Bug 267733] Automatical initialisation of Internal MySQL database doesn't work after digikam start

Riccardo Iaconelli riccardo at kde.org
Tue May 10 10:59:54 BST 2011


--- Comment #15 from Riccardo Iaconelli <riccardo kde org>  2011-05-10 11:59:53 ---
ok, so, I managed to "fix" my digikam problem by cp-ing my .kde folder over,
manually starting a mysqld binary, and "migrate" the database to the internal
I still see

An error occurred during the internal server start.
Error while calling the database server starter.
Details: The name org.kde.digikam.DatabaseServer was not provided by any
.service files

at startup, but now things work perfectly. Is this bug really fixed? was it a
problem with my local database, or some old configs left from god knows when?

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Digikam-devel mailing list