Summary: | digikam crash on startup | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Johannes Schwall <johannes.schwall> |
Component: | Geolocation-Marble | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | CLOSED WORKSFORME | ||
Severity: | crash | CC: | andrew.i.coles, caulier.gilles, janox, kaysimon |
Priority: | NOR | ||
Version: | 1.8.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.9.0 | |
Sentry Crash Report: |
Description
Johannes Schwall
2011-01-29 17:47:04 UTC
Short version: remove the package libmarblewidget10 and try again. Long version: Digikam 1.8 from the Kubuntu Backports PPA was compiled to use libmarblewidget.so.11, but looking at your backtrace it's loading libmarblewidget.so.10. *** Bug 264875 has been marked as a duplicate of this bug. *** The problem is caused by upgrading to KDE 4.6, but using a version of digikam compiled to work with marble from KDE 4.5. The new marble data is incompatible with the older version of marble. The kubuntu backports PPA contains a copy of digikam compiled to use marble from KDE 4.6 - use this package, rather than the one from ppa:philip5/extra. If you only added the philip5 PPA to get digikam, the easiest way to do this is to run: sudo apt-add-repository -r ppa:philip5/extra sudo apt-get update sudo apt-get remove digikam digikam-data sudo apt-get install digikam digikam-data (In reply to comment #3) > The kubuntu backports PPA contains a copy of digikam compiled to use marble > from KDE 4.6 - use this package, rather than the one from ppa:philip5/extra. > If you only added the philip5 PPA to get digikam, the easiest way to do this is > to run: > > sudo apt-add-repository -r ppa:philip5/extra > sudo apt-get update > sudo apt-get remove digikam digikam-data > sudo apt-get install digikam digikam-data I can confirm that this solution works for me, on Kubuntu 10.10. Thanks very much! Thanks a lot! This indeed did the trick. I guess this bug could be closed now, as it's not really a bug. I'll just do that. (Hope it's the right thing to do!?) *** Bug 267412 has been marked as a duplicate of this bug. *** |