[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [digikam] [Bug 342010] Digikam crash, apparently in xcb
From:       Christoph Feck <cfeck () kde ! org>
Date:       2014-12-20 0:36:53
Message-ID: bug-342010-17878-xGIUAMc7Kp () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=342010

Christoph Feck <cfeck@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |UNMAINTAINED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #6 from Christoph Feck <cfeck@kde.org> ---
Okey, this confirms my suspicion. Unfortunately kDebug() does not make sure
KMessageBox is called in the main thread. To avoid this crash, set any other
output method for digikam, because it is highly multi-threaded.

I am closing this as UNMAINTAINED, because we will not fix kDebug().
Applications should be ported to qCDebug, which is hopefully more thread-safe.

Regarding the error thrown by libexiv2, Gilles decides if this should be
reported upstream to libexiv2 developers, or if this is a digikam issue. I am
not sure if .xcf files are supposed to support metadata at all.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]