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

--- Comment #3 from Karsten de Freese <karsten.defre...@posteo.de> ---
Thanks for the ultra-quick reply, which helped me move on, but with no good
result yet..

- I tried the manual update first. Directory
/home/karsten/.local/share/digikam/db_misc/ was empty, and probably because of
this the upgrade fails (as described by Jens in one of his earlier posts).
- Then I downloaded the 7.4.0 AppImage. It did actually produce the same GUI
error messages as the 7.3.0 installation.
- Erroneously, I started the manual update again while the GUI error messages
from the 7.4.0 AppImage were still open, and the manual update succeeded then.
- After closing the 7.4.0 error messages I started the installed 7.3.0 version,
which produced:
"An error occurred during the internal server start.
Details:
Database process exited unexpectedly during initial connection.<p>Executable:
/usr/sbin/mysqld</p><p>Arguments:
--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket</p><p>Process
error: Process crashed</p>"
but after closing the error message and confirming the database configuration,
digikam continued to start up correctly ONCE.

A second start of digikam however resulted in the same error messsage. Closing
the message window brings up the database configuration window, and confirming
the current configuration brings back the error message etc. etc.
The path to db files is set to /var/lib/digikam_db/MySQL.

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

Reply via email to