| Summary: | Opening Geolocation Editor crashes DigiKam | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Herb Smith <hesmith1029> |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, hesmith1029, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 9.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 9.1.0 | |
| Sentry Crash Report: | |||
|
Description
Herb Smith
2026-03-08 18:01:26 UTC
digiKam-9.0.0 from Ubuntu as a Snap package or as an AppImage. Maik Ran the appimage from a terminal session. Got the following when attempting to launch geolocation editor. Will keep looking for info
MESA-LOADER: failed to open radeonsi: ././/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths ././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open zink: ././/lib/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths ././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: ././/lib/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths ././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: ././/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths ././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
/tmp/.mount_digiKaOgmmUS/AppRun: line 266: 348948 Segmentation fault (core dumped) digikam $@
Yes, I can reproduce the crash when I switch to the Google map in the AppImage. This is a QWebEngine problem. There are no problems in my native digiKam version. Maik Use Marble as a workaround; switch in the digikamrc to the Marble backend. [Geolocation Edit Settings][Map Widget] Backend=marble Maik Thanks for the quick response. To change to Marble backend normally requires that I be able to get the GeoLocation editor open. So the crash blocks that. I found that starting DigiKam 8.8 and changing the settings there allows DigiKam 9.0 to load with the Marble settings in place. Switching 9.0 to Google instantly crashes. In fact if I switch 8.8 back to Google I can not even launch 9.0, it crashes when loading tools. I am not a big fan of the Marble map, so I may just stick with 8.8 until this gets fixed. You mentioned running Digikam native. Is that an option on Ubuntu? Just tried golocation with the Marble settings. Same result. Immediate crash after enter CTL-Shift-G (In reply to Herb Smith from comment #6) > Just tried golocation with the Marble settings. Same result. Immediate > crash after enter CTL-Shift-G False alarm. Apparently the map settings for right hand display to not carry over to the Geolocation module, nor to map center panel option. I configured all three to use the Marble option and for now it is NOT crashing. Use the pre-release version of digiKam-9.1.0 from here: https://files.kde.org/digikam/ Maik Confirmed fixed on my machine, thanks |