Summary: | digiKam migration crash on cancel | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Johann-Nikolaus Andreae <johann-nikolaus> |
Component: | Database-Migration | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, maeseee |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.5.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.5.0 |
Description
Johann-Nikolaus Andreae
2017-08-06 14:21:48 UTC
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/ Maik, Marcel, I think this one is fixed with next 7.0.0. Can you confirm ? At least, i cannot reproduce here with my computer... Gilles Gilles, wait with closing this bug. I recently also had a similar problem on the migration of the db type with my huge photo collection. Probably it is connected to this one. It took me several tries until migration worked. I'm trying to reproduce the error with debug information enabled. Hi Marcel, Yes i would no close file too much quickly. This is why i start to post a remember comment to all entries with "crash", "major", "grave", and "critical" properties. This is what we call a "bugs-triage" (:-)) Gilles Git commit e60e89cda0c483be18ac2a294c7a03511b710902 by Maik Qualmann. Committed on 09/07/2020 at 19:19. Pushed by mqualmann into branch 'master'. fix logic for stop processing in the for loop M +14 -11 core/libs/database/coredb/coredbcopymanager.cpp https://invent.kde.org/graphics/digikam/commit/e60e89cda0c483be18ac2a294c7a03511b710902 Git commit c2a0c8a42c852b7b3037cc7b81b39a94e490407b by Maik Qualmann. Committed on 09/07/2020 at 19:46. Pushed by mqualmann into branch 'master'. it is better not to skip the loop M +3 -3 core/libs/database/coredb/coredbcopymanager.cpp M +1 -1 core/libs/database/coredb/coredbcopymanager.h https://invent.kde.org/graphics/digikam/commit/c2a0c8a42c852b7b3037cc7b81b39a94e490407b Git commit 91d7f791faf95873632e195da1241fb04d1cdfa2 by Maik Qualmann. Committed on 09/07/2020 at 20:24. Pushed by mqualmann into branch 'master'. use volatile for the stop flag M +1 -1 core/libs/database/coredb/coredbcopymanager.h https://invent.kde.org/graphics/digikam/commit/91d7f791faf95873632e195da1241fb04d1cdfa2 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 Johann, 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 |