| Summary: | Option to select ignored folders on first setup crashes DigiKam | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Douglas Silva <doug.hs> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 6.2.0 | |
| Sentry Crash Report: | |||
|
Description
Douglas Silva
2017-11-19 02:35:06 UTC
The backtrace is really strange : there is nothing about digiKam code relevant. I recommend to try the 5.8.0 pre-release Linux AppImage bundle instead the Suse package. The bundle can be downloaded from here : https://files.kde.org/digikam/ ... and too see if the problem still reproducible. Gilles Caulier Can you post the output from the console? The QMessageLogger should possibly still have issued a message. Maik I have on my service laptop in the company the same software as you (openSUSE Leap 42.3, digiKam-5.5.0). Even with a new DB and new config file I can not reproduce this crash there. Maik What's about this file using 5.8.0 pre-release buncle : 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/ This problem is not reproducible. If necessary, reopen the bug report. Maik |