Stephen, I am sorry that you feel this way. As I said, solution is to install digikam from karmic-backports repository. You can install just digikam (and kipi-plugins), if you are concerned about "unsupported" status of backports (to prevent other backported packages to install).
For digikam itself, I can only assure you that the karmic backport version (1.0.0) will have same (or even better) attention than "supported" version.
For "supported" version in karmic, we could only get single fix for the crash (a bit hard to hunt actual patches as there were several changes for this crash issue), but this will not make our users happier, as they would probably then get other beta5 issue, that need attention. It is not useful use of our limited resources to do that (and yes, this is mostly done by community resources).
Stephen, I am sorry that you feel this way. As I said, solution is to install digikam from karmic-backports repository. You can install just digikam (and kipi-plugins), if you are concerned about "unsupported" status of backports (to prevent other backported packages to install).
For digikam itself, I can only assure you that the karmic backport version (1.0.0) will have same (or even better) attention than "supported" version.
For "supported" version in karmic, we could only get single fix for the crash (a bit hard to hunt actual patches as there were several changes for this crash issue), but this will not make our users happier, as they would probably then get other beta5 issue, that need attention. It is not useful use of our limited resources to do that (and yes, this is mostly done by community resources).