Summary: | Picture downloading from camera, crashed | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Michael Powell <alvin.michael> |
Component: | Import-Albums | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, Julien |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 8.1.0 | |
Sentry Crash Report: |
Description
Michael Powell
2010-01-23 03:48:47 UTC
Thanks for the report, but this bug as already been fixed for a long time. It has also been reported multiple times (more than 94 !). Look here: https://bugs.kde.org/show_bug.cgi?id=210462 In fact, it is the 8th most reported bug in the history of KDE (https://bugs.kde.org/duplicates.cgi). It means that it has impacted many people. Digikam developpers are sorry as this gives a bad opinion of Digikam although the bug was in a beta version and has been fixed quickly in the next beta. It is not your fault, your distribution (Ubuntu) has decided to package a beta version of Digikam in its stable release AND this beta version contains of bug with breaks one of the main features of Digikam AND Ubuntu is refusing to update the package to the final version 1.0.0 which fixes many bugs (>200). They want to follow their rules about when a package should be updated (https://wiki.ubuntu.com/StableReleaseUpdates). These rules have been designed to provide a stable distribution. But in this case, it does not make sense in my opinion because: - they packaged a beta version of Digikam - this beta contains a bug which breaks one of the main features of Digikam - the stable version is out - no tools depends on Digikam Please ask them to put the final 1.0.0 release in updates. For the time being you can install 1.0.0 final using the backports repository, look here for details: https://help.ubuntu.com/community/UbuntuBackports Julien *** This bug has been marked as a duplicate of bug 210462 *** Fixed with #210462 |