[Digikam-users] digikam 4.1 bugs

Wilkins, Vern W vwilkins at indiana.edu
Mon Jul 28 13:39:00 BST 2014

I haven't followed the thread completely but my question is whether the preview bug has been satisfactorily fixed in 4.1.  I gave up on using 4.x because of this problem.  No offense intended but this is a 'major' bug to have in a stable release and still in an update to the stable release.  For me it made the application more or less unusable.

I had the problem with 4.0 on Gentoo Linux, compiling against the latest unstable kde and opencv libraries, which included opencv 2.4.9.  I still had the problem after I built my own package for 4.1 and built against the same libraries.

On Fedora I had the same problem with Digikam 4.0.  I used another repository to install 4.1 and the problem still persists.  Fedora developers are trying to get opencv 2.9 into the repository and indicating this will fix the problem.  I'm not sure I've really seen that explained here.  Is this really a fix for the preview problem?

From: digikam-users-bounces at kde.org [digikam-users-bounces at kde.org] on behalf of Anders Lund [anders at alweb.dk]
Sent: Monday, July 28, 2014 5:56 AM
To: digiKam - Home Manage your photographs as a professional with the power of open source
Subject: Re: [Digikam-users] digikam 4.1 bugs

On Mandag den 28. juli 2014 11:51:55, Remco Viƫtor wrote:
> On Monday 28 July 2014 11:03:49 Anders Lund wrote:
> > On Mandag den 21. juli 2014 18:19:52, Gilles Caulier wrote:
> > > Here, i'm in full debug mode, which introduce some small time
> > > latencies. which is enough to mask this kind of problem.
> >
> > I don't think it is smart to require digikam being compiled in full debug
> mode
> > to work correctly!
> Gilles is not saying that you are required to build digikam in full debug
> mode, just that that is what he does, and that the build mode could change
> timings enough so that certain race conditions don't become visible (or
> much less often). That does not mean the races aren't there, just that they
> don't become visible.
> And that's typically the kind of bugs that you can get when switching to
> multithreaded, and they are particularly hard to debug...

If I can do anything to help, I will. I can install debug package etc, or even
try to build digikam locally, if it can help :)

Digikam-users mailing list
Digikam-users at kde.org

More information about the Digikam-users mailing list