https://bugs.kde.org/show_bug.cgi?id=394434
--- Comment #52 from caulier.gil...@gmail.com ---
The first scan can be long, this depend of collection size and number of items
to populate in database.
In my case, i setup a small collection to test (less than images). I recommend
to do the same in first.
For the error reported previously, i insist : it's abnormal to see
mysql_install_db using conf file from user space instead DK bundle one (from
/opt/digikam/...).
At init you must to see someting like this on the console :
digikam.databaseserver: Database initializer:
"/opt/digikam/lib/mariadb/bin/mysql_install_db"
("--datadir=/Users/gilles/Pictures/.mysql.digikam/db_data",
"--defaults-file=/opt/digikam/Applications/KF5/digikam.app/Contents/Resources//digikam/database/mysql-global.conf")
This line come from my debug trace. Look the path to mysql-global.conf. It come
from /opt/digikam/..., not my user space (/Users/gilles/...).
This is mandatory as the shell script from mysql/mariadb is bugous and do not
accept space in path).
After that, creating mysql server instance in memory, using the binary file
mysqld which is not a sheel script, can use a path with space. From my debug
trace :
digikam.databaseserver: Database server: "/opt/digikam/lib/mariadb/bin/mysqld"
("--defaults-file=/Users/gilles/Library/Application
Support/digikam/digikam/mysql.conf",
"--datadir=/Users/gilles/Pictures/.mysql.digikam/db_data",
"--socket=/Users/gilles/Library/Application
Support/digikam/digikam/db_misc/mysql.socket")
This one use conf file from user space, as the temporary socket file used to
communicate with the internal server from DK, through localhost.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
