| Summary: | Digikam is no longer working | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | mippo <mippo9> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.0.0 | |
| Sentry Crash Report: | |||
|
Description
mippo
2019-12-07 16:28:27 UTC
It crash in QDebug section. Probably it's a problem relevant of the system journal settings to archive application log through QDebug. Gilles Caulier After the crash, you would have to use an internal MySQL database. Please post the messages that will be output on the console until crashing. Maik Git commit ceb585f7b1d083c806b12d19557d9ec9956ab02e by Maik Qualmann. Committed on 07/12/2019 at 18:06. Pushed by mqualmann into branch 'master'. prevent crashes in the running database server when we leave the program in main() M +2 -0 core/app/main/main.cpp M +2 -0 core/libs/database/server/databaseserverstarter.cpp https://invent.kde.org/kde/digikam/commit/ceb585f7b1d083c806b12d19557d9ec9956ab02e The crash is clear, we are already leaving the program in main() because of a problem with the database. The database server is still running and printed debug messages and will not be terminated. All we have to do now is know what the problem with the database is. Please post the console log. Maik |