| Summary: | Plasma crash after start when loading an image in a Frame (XMP-libkexiv2 related) | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] libkexiv2 | Reporter: | Kasper Cęcek <kcecek> |
| Component: | General | Assignee: | imaging-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | ahuggel, andresbajotierra, annma, caulier.gilles, dan_poz, kde, maris.kde, robert.andersson, rz |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.8 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Kasper Cęcek
2010-11-23 23:13:21 UTC
Andreas, libkexiv2 is now used in KDE Plasma component. I think it's a image slideshow tool. Look Thread 7 where crash appears. It's XMP parser. Kasper, We need to know which Exiv2 and libkexiv2 version you use exactly. Gilles Caulier digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier Gilles I'm not sure if that is what you asked for :(, anyway there is yum info: [root@odyn log]# yum list installed '*exiv2*' Wczytane wtyczki: auto-update-debuginfo, presto, refresh-packagekit Zainstalowane pakiety exiv2.x86_64 0.20-1.fc14 installed exiv2-debuginfo.x86_64 0.20-1.fc14 @fedora-debuginfo exiv2-libs.i686 0.20-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 exiv2-libs.x86_64 0.20-1.fc14 installed I will try to upgrade digikam - however personally I would like wait for "normal" fedora package. I didn't add in bug description that this issue is not common - I had it once but next time when KDE was starting everything was ok. However from time to time I had issues with plasma crashing (or not starting ... no idea how and what to check) at the begining. In such case I had to kill all plasma processes and then start it again. I'm not sure if these problems are related to one that were issued - generally difference is in style how crash is done - reported issue was the first time when crash was detected and I was asked for details (so I did). I'm not Suse specialist but i suspect that you mix 32 and 64 bits version of Exiv2 library. Right ? i recommend to install only one version. Here Andreas can guide better than me. Also, if you can identify the image responsible to the crash and provide it somewhere to test in local, it will be nice. Gilles Caulier Updating digiKam will not help. The component used by Plasma is libkexiv2, which is a KDE interface for Exiv2 library. libkexiv2 is included in KDE core, into kdegraphics/libs. This library is maintained by digiKam team Gilles Caulier This looks like an issue for Plasma: The crash happens somewhere in Exiv2::XmpParser::initialize() which is called from Exiv2::XmpParser::decode(). That indicates that the application doesn't initialize the XMP parser correctly: It has to make sure the call to Exiv2::XmpParser::initialize() is serialized. See http://dev.exiv2.org/projects/exiv2/wiki/Thread_safety Andreas Thanks Andreas. You is right here. To Plasma developper, XMP Sdk from Exiv2 must be initialized as it's done in digiKam & co program. Look here for ex: http://lxr.kde.org/source/extragear/graphics/digikam/digikam/main.cpp#91 http://lxr.kde.org/source/extragear/graphics/digikam/digikam/main.cpp#215 This is not the fault to libkexiv2 or Exiv2. It's a wrong design of XMP sdk from Adobe... Gilles Caulier *** Bug 256705 has been marked as a duplicate of this bug. *** One day we should fix this in the XMP-SDK. *** Bug 260300 has been marked as a duplicate of this bug. *** *** Bug 260350 has been marked as a duplicate of this bug. *** I can confirm that removing the picture frame from the desktop prevents the crash I reported in Bug 260350 (which is a dupe of this one) completely. I'm just wondering why so few picture frame users have this problem. Is there an alternative or workaround short of having no picture frame? Created attachment 57631 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
- What I was doing when the application crashed:
It's still crashing with 4.6.0.
[IP-] [ ] kde-base/libkexiv2-4.6.0:4.6
[IP-] [ ] media-gfx/exiv2-0.21-r1:0
-- Backtrace (Reduced):
#6 _M_begin (namespaceURI=<value optimized out>, prefix=<value optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/include/g++-v4/bits/stl_tree.h:482
#7 lower_bound (namespaceURI=<value optimized out>, prefix=<value optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/include/g++-v4/bits/stl_tree.h:745
#8 lower_bound (namespaceURI=<value optimized out>, prefix=<value optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/include/g++-v4/bits/stl_map.h:701
#9 operator[] (namespaceURI=<value optimized out>, prefix=<value optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/include/g++-v4/bits/stl_map.h:447
#10 XMPMeta::RegisterNamespace (namespaceURI=<value optimized out>, prefix=<value optimized out>) at XMPMeta.cpp:1049
Is this still valid with KDE 4.9? It works for me now with KDE 4.8. KDE 4.9 hasn't hit Fedora 16 quite yet. Thank you for the feedback. *** Bug 345720 has been marked as a duplicate of this bug. *** |