Summary: | Application crash with older plugins installed | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Marcel Wiesweg <marcel.wiesweg> |
Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cabster724, caulier.gilles, hirvard, kde, swarfega |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.0.0 |
Description
Marcel Wiesweg
2012-10-03 14:44:17 UTC
Dear ksnapshot guys, this is not your fault! This crash is the inverse to the problems we had with libkipi1 plugins being loaded into a libkipi2 app. 1) A libkipi1 app loads a libkipi2 plugin 2) The plugin's constructor is combined with the KIPI::Plugin constructor from libkipi1, as the symbol name does not differ 3) The plugin's constructor calls setUIBaseName. This symbol does not exist in libkipi1, so the code from libkipi1 is called 4) KIPI::Plugin::setUIBaseName accesses d->uiBaseName. As the constructor of KIPI::Plugin libkipi1 was used, Plugin::Private does not contain this field. 5) Invalid memory is accessed. Ideas? Marcel, This problem is fixed for me since current code from git/master (libkipi and kipi-plugins). libkipi 2.0.0 will only load kipi-plugins 3.0.0. Older version of plugins will be ignored. We use a version id in all plugins desktop file to see which libkipi SO id have been used to compile tools. Gilles Caulier The case of libkipi 2.x loading kipi-plugins <3.0 is fixed. This is about libkipi 1.x loading kipi-plugins 3.0. And libkipi 1.x is out there on users' systems with KDE 4.9, which means we cannot fix it by updating libkipi 1.x anymore. Assuming libkipi 2.x will come with KDE 4.10, there is a time span during which installing digikam 3.0 & associated libraries will, unfriendly, make KDE 4.9 apps crash, not digikam, but KSnapshot etc. I dont have a good idea how to fix it atm. *** Bug 309677 has been marked as a duplicate of this bug. *** *** Bug 313577 has been marked as a duplicate of this bug. *** *** Bug 315033 has been marked as a duplicate of this bug. *** digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier digiKam 4.0.0 is out : http://www.digikam.org/node/713 Please check if this entry still valid with this new version. Thanks in advance Gilles Caulier This file still valid using last digiKam 4.2.0 ? Gilles Caulier New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier With digiKam 5.0.0, this problem is not reproducible. I close this file now. Re-open it if necessary. Gilles Caulier |