[digikam] [Bug 383204] digiKam migration crash on cancel

2022-01-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.5.0 Resolution|---

[digikam] [Bug 383204] digiKam migration crash on cancel

2021-12-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #11 from caulier.gil...@gmail.com --- Johann, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance -- You are receiving this mail because: You are watching all

[digikam] [Bug 383204] digiKam migration crash on cancel

2021-03-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #10 from caulier.gil...@gmail.com --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #9 from Maik Qualmann --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #8 from Maik Qualmann --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #7 from Maik Qualmann --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #6 from caulier.gil...@gmail.com --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-09 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=383204 --- Comment #5 from Marcel --- 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

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 caulier.gil...@gmail.com changed: What|Removed |Added CC||maes...@gmail.com --- Comment #4

[digikam] [Bug 383204] digiKam migration crash on cancel

2020-07-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383204 caulier.gil...@gmail.com changed: What|Removed |Added Summary|digikam migration chrash on |digiKam migration crash on