[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 caulier.gil...@gmail.com changed: What|Removed |Added Platform|MacPorts Packages |Mac OS X Disk Images Version Fixed

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #64 from caulier.gil...@gmail.com --- Testa, Good news... After all, the last problem in this entry is solved. The crash relevant of QProcess calls disapear after to recompile the whole digiKam bundle from scratch. Probably a mix of

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #63 from caulier.gil...@gmail.com --- Ok, I'm back to this issue with some progress. Typically, as explained well in this page : http://www.qtcentre.org/threads/38730-Calling-external-programs-via-QProcess-on-Mac-OS The MACOS world is

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #62 from caulier.gil...@gmail.com --- In time, these crashes appear just before to see the First Run assistant. This one populate the Database page with runtime dependecies detected at startup up. It's fun to see these thread crashed

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #61 from caulier.gil...@gmail.com --- This is the resume of the 4 crashes which appear when i start digiKam from Launchpad : Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_malloc.dylib 0x7fff783dc910

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #60 from caulier.gil...@gmail.com --- Created attachment 112840 --> https://bugs.kde.org/attachment.cgi?id=112840=edit MacOS log files viewer with digiKam reports while starting from lauchpad -- You are receiving this mail because: You

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #59 from caulier.gil...@gmail.com --- Testa, Maik, Sorry for my late response. I'm not at home, and i'm busy until next Sunday. I can confirm that i can reproduce the problem when i start digiKam directly from OSX desktop icon. Running

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #58 from testa --- > Q : what do you mean by "How can I trace in normal application mode ?" > Do you mean to trace debug statement on the console without to run digiKam in > the terminal ? Yes that's it. Using a

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #57 from caulier.gil...@gmail.com --- Q : what do you mean by "How can I trace in normal application mode ?" Do you mean to trace debug statement on the console without to run digiKam in the terminal ? Do you mean that starting digiKam

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #56 from caulier.gil...@gmail.com --- Testa, Under MacOS, start the "Terminal" application. run digiKam directly from the console with this command ; /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam All the trace will be

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #55 from testa --- I had tested with a very small collection. I can trace in terminal mode but it is this mode that works. How can I trace in normal application mode, except to modify the appropriate script. Guy >

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #54 from caulier.gil...@gmail.com --- So, if the problem appear with a large collection, we will need a full debug trace from the console with all collection scan stages, until the failure event. You need to reset the database before, of

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #53 from testa --- I confirm that in normal mode the direct launch fails. As for the long time I wanted to talk about the time taken for the app to request information. By cons I launched digikam in terminal mode:

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

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

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #51 from testa --- Hi I followed your indications to know how to do the cleaning of: - - ~ / Library / Application Support / digikam - ~ / Library / Preferences / digikamrc - ~ / Pictures / .mysql.digikam as well as

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #50 from caulier.gil...@gmail.com --- The error message is relevant of mysql_install_db which still use the DB conf file copied on user space instead to use one from /opt/digikam/... internal space. This is abnormal, as the code have been

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #49 from testa --- Created attachment 112805 --> https://bugs.kde.org/attachment.cgi?id=112805=edit error message -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #48 from testa --- Sorry, but the last package still causes the error as an attachment. The launch is very very long. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #47 from caulier.gil...@gmail.com --- Testa, The new PKG installer is now online with last code from git/master repository. I'm waiting for your feedback, but for me this file can be closed soon. Best Gilles Caulier -- You are

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #46 from caulier.gil...@gmail.com --- Testa, To be able to start DK with last PKG installer, please remove the following files : - _your_home_directory_/Library/Application Support/digikam -

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #45 from caulier.gil...@gmail.com --- Created attachment 112803 --> https://bugs.kde.org/attachment.cgi?id=112803=edit DK 6.0.0 trace from scratch with Mysql internal server Maik, I tried my last PKG with all Mariadb binaries fixes, and

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #44 from caulier.gil...@gmail.com --- testa, 6.0.0 PKG installer is updated at usual place with ore mariadb binaries compatibilities Please try again Gilles Caulier -- You are receiving this mail because: You are watching all bug

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #43 from caulier.gil...@gmail.com --- bash-3.2$ /opt/digikam/lib/mariadb/bin/mysql -u root --socket="/Users/gilles/Library/Application Support/digikam/digikam/db_misc/mysql.socket" Welcome to the MariaDB monitor. Commands end with ; or \g.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #42 from Maik Qualmann --- Access from the console (digiKam must be started, internal server started): mysql -u root --socket=Path_to_socket_file CREATE DATABASE digikamtest; USE digikamtest; CREATE TABLE Test

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #41 from caulier.gil...@gmail.com --- Created attachment 112795 --> https://bugs.kde.org/attachment.cgi?id=112795=edit mysql internal servel log file after local collection add and scan completed. -- You are receiving this mail because:

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #40 from caulier.gil...@gmail.com --- Look like the collection after first scan completed is available and ready to use. Look like the local collection has moved as a removable one. Why ? Gilles -- You are receiving this mail because: You

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #39 from caulier.gil...@gmail.com --- Created attachment 112794 --> https://bugs.kde.org/attachment.cgi?id=112794=edit DK screenshot after first scan with mysql internal server and a local collection set -- You are receiving this mail

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #38 from caulier.gil...@gmail.com --- No wrong alert. socket file is well created.This is not the problem. I restart digiKam and setup a local collection. Scan is started. At end DK said that it cannot add the collection to DB. Gilles --

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #37 from caulier.gil...@gmail.com --- Maik, For the socket connection, /Users/gilles/Library/Application Support/digikam/digikam/db_misc/mysql.socket at least /Users/gilles/Library/Application Support/digikam/digikam/db_misc/ directory do

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #36 from caulier.gil...@gmail.com --- Maik, Mysql give a log from internal server : bash-3.2$ cat mysql.err 180521 20:43:30 InnoDB: The InnoDB memory heap is disabled 180521 20:43:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #35 from caulier.gil...@gmail.com --- Maik, Remember me, which SQL query is used to create the digikam databases in internal server ? how i can reproduce this task on CLI ? Gilles -- You are receiving this mail because: You are watching

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #34 from caulier.gil...@gmail.com --- I cleaned again all DK data files (config, DB), and startup again : macbook-pro-de-gilles:~ gilles$ /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam digikam.widgets: Breeze icons

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #33 from caulier.gil...@gmail.com --- No idea. I take a look. Gilles -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #32 from Maik Qualmann --- Gilles, I think the MySQL server can not access the data directory. Is it possible that a mysql user needs to be created in MacOS? Maik -- You are receiving this mail because: You are

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #31 from testa --- Hi In terminal mode it actually happened. To follow, I will test thoroughly, but in any case thank you for considering the problem. It is a good application that allows to quickly view his photos,

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #30 from Maik Qualmann --- Gilles, QProcess with the arguments use internally quotes. The mysqld is already started, the database can not be created, strange. Maik -- You are receiving this mail because: You are

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #29 from caulier.gil...@gmail.com --- Look my comment #27 (:=)))... This is the reason. It's always a path with space problem. Gilles -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #28 from Maik Qualmann --- ... > digikam.databaseserver: Failed to use database "digikam" > digikam.databaseserver: Query error: "Unknown database 'digikam' QMYSQL: > Unable to execute query" > digikam.databaseserver:

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #27 from caulier.gil...@gmail.com --- Maik, Using doube quote over path passed as argument for mysqld is the solution : macbook-pro-de-gilles:~ gilles$ /opt/digikam/lib/mariadb/bin/mysqld --defaults-file="/Users/gilles/Library/Application

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #26 from caulier.gil...@gmail.com --- The problem is the next stage to start internal server : macbook-pro-de-gilles:~ gilles$ /opt/digikam/lib/mariadb/bin/mysqld --defaults-file=/Users/gilles/Library/Application

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #25 from caulier.gil...@gmail.com --- Maik, Now in fact the problem with mysql_install_db is fixed. Look like DB files are now created properly on user space : # pwd /Users/gilles/Pictures/.mysql.digikam # ls -alR total 0 drwxr-xr-x 3

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #24 from caulier.gil...@gmail.com --- No, the mysql_install_script exec right is fine. Look the PKG contents. Now the error is probably relevant of path used with the communication socket between the server and the Qt Mysql plugin. Look the

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #23 from caulier.gil...@gmail.com --- Created attachment 112785 --> https://bugs.kde.org/attachment.cgi?id=112785=edit PKG file contents before packaging See attached ls -alR over root directory before to package in target PKG for MacOS

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #22 from Maik Qualmann --- My guess, the script is not found or the execution rights are not set. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #21 from caulier.gil...@gmail.com --- Comment on attachment 112779 --> https://bugs.kde.org/attachment.cgi?id=112779 new error message ok. Open a terminal, and run : /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam The

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #20 from testa --- Created attachment 112779 --> https://bugs.kde.org/attachment.cgi?id=112779=edit new error message -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #19 from testa --- Hi I just tried the last package digikam digiKam-6.0.0-git-20180520T114315-MacOS-x86-64, I made a complete reinstallation, but at the opening of digikam I immediately got the following message: --

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #18 from Maik Qualmann --- We close the bug if it was tested on MacOS. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #17 from Maik Qualmann --- Git commit 1f22ae00a59372bf0df9f203d36305abaeba019b by Maik Qualmann. Committed on 20/05/2018 at 06:18. Pushed by mqualmann into branch 'master'. use the digiKam global MySQL config file

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 --- Comment #16 from caulier.gil...@gmail.com --- You are right. By this way the conf file is always store in a simpler path under Linux and MacOS. It's definitively the best and simpler way. Gilles -- You are receiving this mail because: You are

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

https://bugs.kde.org/show_bug.cgi?id=394434 Maik Qualmann changed: What|Removed |Added Summary|installation problem mysql |installation problem