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

[Riccardo Iaconelli]

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





--- Comment #13 from Riccardo Iaconelli <riccardo kde org>  2011-05-10 11:44:25 ---
1) Start digikam from the command line. Error Box:

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

2) Press "Ok", watch the konsole:

[ruphy at hilbert:digikam/build]$ digikam                                         
                                                                   (05-10
11:40)
digikam(23910)/digikam (core): Error while opening the database. Error details
[ QSqlError(2002, "QMYSQL: Unable to connect", "Can't connect to local MySQL
server through socket
'/home/ruphy/.kde/share/apps/digikam/db_misc/mysql.socket' (2)") ] 
QSqlError(2002, "QMYSQL: Unable to connect", "Can't connect to local MySQL
server through socket
'/home/ruphy/.kde/share/apps/digikam/db_misc/mysql.socket' (2)") ] 
...

3) Try to open the config dialog, tick "internal server", and try to test a
connection:

Database connection test was not successful. 
Error was: Can't connect to local MySQL server through socket
'/home/ruphy/.kde/share/apps/digikam/db_misc/mysql.socket' (2) QMYSQL: Unable
to connect

As a matter of facts, looking in there you find that there is no mysql.socket
file.

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