| Summary: | Crash with MariaDB-Database | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Gerard <gandalfs-welt> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, gandalfs-welt |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
|
Description
Gerard
2017-02-12 14:26:03 UTC
I use Mageia also to develop digiKam. MariaDB is used here. No crash. I recompile myself digiKam of coure. I do not use Mageia RPM of course. The crash appears in Qt5 sql driver. Perhaps something is wrong here, or in your DB server settings. Did you follow all instruction from handbook here : https://docs.kde.org/trunk5/en/extragear-graphics/digikam/using-setup.html#using-setup-database At least i recommend to test the Mysql internal database in digiKam. This will use Mariadb as sqlite, not has a deamon server. Gilles Caulier Hi and thanks for the very quick reply. I'll tried to change to internal database (i'ved had some strange problems with this previous - driver not loaded, socket file not found etc...) now I'm migrating the external database to internal... I will be back soon :-) My configuration was the same way, like the link you posted. Migration won't work... First: all seems to be ok, but the database was empty... New indexing of all Photos (ca. 25,000) still running.... new 5.6.0 pre-release as bundle is available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Please check if this problem still reproducible with these versions. Thanks in advance Gilles Caulier digiKam 5.6.0 is now released and available as bundle for Linux, MacOS and Windows. https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ Can you check if problem still exists with this version ? Thanks in advance Gilles Caulier Hi, thank you. I will take a try these weekend. New digiKam 5.7.0 are built with current implementation as pre-release bundles: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Problem still reproducible ? With next 5.8.0 release Mysql support have been well improved and a lots of bugs fixed. Please test with pre release 5.8.0 bundles that we provide and give us a feedback https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle available here : https://files.kde.org/digikam/ Gilles Caulier Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ Hi, Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla: https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/ Can you reproduce the dysfunction with this version ? Thanks in advance for your feedback Gilles Caulier Gerard, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance No feedback. not reproducible with 7.5.0. Closed |