| Summary: | Digikam crashes when attempting to modify geolocation data | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | arthur |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
| Attachments: | Crash log - edit geolocation | ||
|
Description
arthur
2021-02-12 13:10:43 UTC
Please, download debug version of PKG available here : https://files.kde.org/digikam/ Try to reproduce the problem and report the log backtrace of crash. Thanks in advance Gilles Caulier How do I do that? I'm sorry, I'm a bit out of my depth here. Just download the PKG with "debug" prefix located here : https://files.kde.org/digikam/ Install it to replace non debug version. Run digiKam and try to reproduce the crash. When it happen, a backtrace dialog will appear with a log text view. Copy and paste the contents here... Gilles Caulier I'm sorry, I should've been more clear. I've already installed the debug version and reproduced the crash, but I can't find the backtrace dialog for the life of me. Should it appear after the crash or at the next startup or something? Because I've run it multiple times and searched for it in the menu items, but I didn't see anything like that at all. Yet again, I'm sorry. I'm probably missing something obvious here. Well the dialog must appear just after the crash... Typically this dialog come from directly macOS. It used to report problem with application to Apple if necessary. Here : https://osxdaily.com/2010/02/15/disable-the-crash-reporter-dialog-in-mac-os-x/ It explained how to turn on/off this dialog. On my macbook pro, it automatically turned on as i installed XCode IDE to develop... Gilles Caulier Created attachment 135718 [details]
Crash log - edit geolocation
It crashes on a Q_ASSERT in Marble::GeoTagHandler::registerHandler(). Because the name of a GeoParser already exists in the QHash. Maik The cause is probably that Marble plugins are duplicated and thus loaded twice. Have you possibly not completely removed an older digiKam version? Maik That's possible, how would I go about checking it? I installed the newest beta using the installer. Hi, I recommend to wait the next PKG build done this evening and avaialble tomorow morning at usual place: https://files.kde.org/digikam/ I accidentally not propagated some change in the computer in charge of PKG build which can introduce dysfunctions to the target macOS binary of digiKam. I fixed the problem so next build must be safe. Note: The problem have been introduced one week ago. Gilles Caulier Arthur,
The new pre-release is published online, and i'm sure that the PKG build is correct now.
If you have a recent PKG version of digiKam installed you can use the "Online Version Checker" feature introduced with 7.2.0.
> Go to Setup/Miscs/Behaviour/Updates
> Switch to check new version as "Weekly Pre-release"
> Press "Check Now..."
the tool must check last online version, download PKG, and propose to install it.
Best
Gilles Caulier
Sadly, the problem still persist, even on the latest version. Do you want me to post the log file again? Hum. Do you have something installed in /opt/digikam on your computer ? Gilles Caulier Gilles, what's the old path to digiKam so that Arthur can see if he still has an older version of digiKam on his Mac. The marble plugins should definitely be present twice in the search path. Maik Hi Maik, The old path is /opt/digikam aka with digiKam version <= 7.2.0-beta1 (perhaps beta2 pre-version, i'm not sure) The new path is /Applications/digiKam.org. /Applications is the stadard place to host macOS applications. Gilles The /opt/digikam folder was gone, so that doesn't seem to be it. I did find a couple of folders related to marble deep inside of MacPorts folders, but those were last changed in 2014 and 2018 respectively, and as far as I can see they never had any bearing on my actual install of digikam itself. Are there perhaps any specific files related to marble I could search to see if there are files left over from a previous installation? yes it is, as the crash backtrace is relevant of Marble APi, this can be a side effect. I don't know why an extra and old Marble version somewhere in your computer can introduce a dysfunction in digiKam macOS bundle... Gilles Caulier Hmm, any idea where those residual files might reside? The only files related to digikam I can find are in the Applications and Application support folders, and in the location of my database file. So I'm really lost as to where any other would be. Yet again, I'm really sorry I'm quite out of my depth here. Thanks for your patience. Athur, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. Thanks in advance Gilles Caulier Hi Arthur and happy new year, Can you reproduce the problem with digiKam 7.5.0 pre-release AppImage bundle for Linux available here where marble component have been updated to last stable : https://files.kde.org/digikam/ Best regards Gilles Caulier (In reply to caulier.gilles from comment #20) > Hi Arthur and happy new year, > > Can you reproduce the problem with digiKam 7.5.0 pre-release AppImage bundle > for Linux available here where marble component have been updated to last > stable : > > https://files.kde.org/digikam/ > > Best regards > > Gilles Caulier Hi Gilles, No, it works perfectly now. Thanks for your hard work! not reproducible with 7.5.0. Closed |