Summary: | Digikam crash when goelocating image in the marble tab | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Philippe <pmiossec> |
Component: | Geolocation-Marble | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | marcel.wiesweg |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: |
Description
Philippe
2009-04-12 14:42:51 UTC
Without a backtrace we cannot do anything... Gilles Caulier yes, it's what I was thinking and I have even installed gdb but it tell me that the backtrace was not usefull. I have downloaded the sourcecode to try with compiling my own version to help you better. But I actually don't know how to compile it ( ./configure script not present :( surely have to use cmake?! Is that ok?) But you could surely reproduce the bug because it seems not to be a fedora packaging bug because it is present in the windows version of digikam too. This is most certainly a problem coming from Marble. (I am having Marble crashes myself here occasionally. There have been lots of bug reports) So - if you get a backtrace don't be disappointed if we redispatch to the Marble guys! Getting the latest KDE 4.2.x packages may help as well, when new ones are available. cosmocat, What's news about this entry. It still valid ? Gilles Caulier Thanks for the interest ported to this issue. Since the update of fedora, it seems to be corrected. There is no more systematic crash. Nevertheless, I can't be categoric because I still experience crashes and I can't actually figure out where they come from. I prefer you close this bug report and I will post another bug report if I could find some logic behind the crashes. Ok. Thanks fro the report. I close this file now. Gilles Caulier |