Comment # 3 on bug 937280 from Gian Paolo Sanino

(In reply to Raymond Wooninck from comment #2)
> @Nico,
> 
> As that you updated digikam in KDE:Extra, maybe you can also ensure that the
> other two packages are either there or that they are updated through a
> maintenance update for 13.2
> 
> Furthermore it seems that quite some repos are being mixed here, which could
> issues as well.  I am wondering if Digikam 4.11 compiled against openSUSE
> 13.2 actually crashes if only the update repo and KDE:Extra are enabled

Hi Raymond,

I just tested your proposal (fresh install opensuse 13.2, with default repos +
nvidia repo and KDE:EXTRA). I had to reinstall everything again since my last
update to DK4.13 made digikam to crash when starting with a marble library and
then segfaults. I know this is another issue to the bug listed here. But I
wanted to report that we do have problems despite having only KDE:EXTRA
enabled.
However, now it seems the problem is related to something mixed up with Qt5
despite DK is still Qt4. I have tried with DK 4.10 / 4.11 and 4.13. All of them
crashing with segfault associated to qt5 lib. I cannot even attach the crash
file since even Firefox is having problems (more a KDE issue rather than DK?).
It seems some KDE update mixed badly something qt5 that is creating the
problem. I wanted to post this as a separate bug, but I am having too many
difficulties to just to keep this open. I copy below a section of the crash in
case it helps. I should do a fresh install again, and try to find at which step
this problem is created.
regards 

[KCrash Handler]
#5  0x00007f17795b9936 in __strcmp_sse2 () at /lib64/libc.so.6
#6  0x00007f173fbd0fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags<QMetaType::TypeFlag>, QMetaObject const*) () at
/usr/lib64/libQt5Core.so.5
#7  0x00007f174c261f57 in  () at /usr/lib64/libQt5Gui.so.5