[opensuse-kde] KDE:Current wonkyness on libkdecore4
My gwenview has been broken for some time now and I think I finally figured it out. I develop to qt5 but of course I use kde 4 so I have both installed. I noticed this while poking around, finally getting to the bottom of a nasty stack trace that somehow lead KIPI to load qt5 gui from qt4 core. rpm -ql libkdecore4-4.13.2-55.1.x86_64 /usr/lib64/libkdecore.so.5 /usr/lib64/libkdecore.so.5.13.2 /usr/lib64/libkdefakes.so.5 /usr/lib64/libkdefakes.so.5.13.2 /usr/lib64/libkpty.so.4 /usr/lib64/libkpty.so.4.13.2 /usr/share/doc/packages/libkdecore4 /usr/share/doc/packages/libkdecore4/COPYING /usr/share/doc/packages/libkdecore4/COPYING.DOC /usr/share/doc/packages/libkdecore4/COPYING.LIB /usr/share/doc/packages/libkdecore4/README How in the world did 5.13.2 get there? I looked over the current spec file (and last 2 recent changes) and I couldn't find anything obvious. Looks like all my kde applications are linked against it such that mving it to it's proper location breaks everything - so that's a bummer. -Jason -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data lunedì 14 luglio 2014 23:22:32, Jason Newton ha scritto: Hello,
How in the world did 5.13.2 get there? I looked over the current spec file (and last 2 recent changes) and I couldn't find anything obvious.
That is the SO version of the library, which has no direct relation to the version of the package (kdelibs4). (FYI, kdecore by itself does not exist anymore in KDE Frameworks 5). -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
Fair enough although I don't think it's normal to bump the SO version
outside of the project major.minor versions (not saying I haven't seen
it done but it is more bizarre here). Here's the lovely stacktrace
I've gotten for gwenview:
[KCrash Handler]
#5 0x00007fcbb0b33f3c in __strcmp_ssse3 () from /lib64/libc.so.6
#6 0x00007fcb8f08b09e in QMetaType::registerNormalizedType(QByteArray
const&, void (*)(void*), void* (*)(void const*), void (*)(void*),
void* (*)(void*, void const*), int, QFlagsQMetaType::TypeFlag,
QMetaObject const*) () from /usr/lib64/libQt5Core.so.5
#7 0x00007fcb8e7b5907 in ?? () from /usr/lib64/libQt5Gui.so.5
#8 0x00007fcbb56b985a in call_init.part () from /lib64/ld-linux-x86-64.so.2
#9 0x00007fcbb56b9943 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#10 0x00007fcbb56bdaa8 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#11 0x00007fcbb56b96e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#12 0x00007fcbb56bd29b in _dl_open () from /lib64/ld-linux-x86-64.so.2
#13 0x00007fcbadcf902b in dlopen_doit () from /lib64/libdl.so.2
#14 0x00007fcbb56b96e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#15 0x00007fcbadcf95dd in _dlerror_run () from /lib64/libdl.so.2
#16 0x00007fcbadcf90c1 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#17 0x00007fcbb464630c in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007fcbb464128a in ?? () from /usr/lib64/libQtCore.so.4
#19 0x00007fcbb4641893 in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007fcbb1a624a8 in KPluginLoader::load() () from
/usr/lib64/libkdecore.so.5
#21 0x00007fcbb1a62748 in KPluginLoader::factory() () from
/usr/lib64/libkdecore.so.5
#22 0x00007fcbb3e82bc4 in KIPI::PluginLoader::Info::plugin() const ()
from /usr/lib64/libkipi.so.11
#23 0x0000000000470420 in Gwenview::KIPIInterface::loadOnePlugin
(this=0x1c148b0) at app/kipiinterface.cpp:310
#24 0x00007fcbb466d11e in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#25 0x00007fcbb21588ac in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib64/libQtGui.so.4
#26 0x00007fcbb215ee70 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib64/libQtGui.so.4
#27 0x00007fcbb2e6f5ea in KApplication::notify(QObject*, QEvent*) ()
from /usr/lib64/libkdeui.so.5
#28 0x00007fcbb46550ad in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib64/libQtCore.so.4
#29 0x00007fcbb46580ff in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() from /usr/lib64/libQtCore.so.4
#30 0x00007fcbb4682493 in ?? () from /usr/lib64/libQtCore.so.4
#31 0x00007fcbada40316 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#32 0x00007fcbada40668 in ?? () from /usr/lib64/libglib-2.0.so.0
#33 0x00007fcbada4070c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#34 0x00007fcbb4681d55 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
() from /usr/lib64/libQtCore.so.4
#35 0x00007fcbb21f5936 in ?? () from /usr/lib64/libQtGui.so.4
#36 0x00007fcbb4653d0f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib64/libQtCore.so.4
#37 0x00007fcbb4654005 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#38 0x00007fcbb465913b in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#39 0x000000000044ed88 in main (argc=<optimized out>, argv=<optimized
out>) at app/main.cpp:145
Gwenview will stop crashing when I rpm -e --no-verify libqt5gui5.
Looks like this is not quite a new issue:
https://bugs.kde.org/show_bug.cgi?id=322558
On Tue, Jul 15, 2014 at 12:05 AM, Luca Beltrame
In data lunedì 14 luglio 2014 23:22:32, Jason Newton ha scritto:
Hello,
How in the world did 5.13.2 get there? I looked over the current spec file (and last 2 recent changes) and I couldn't find anything obvious.
That is the SO version of the library, which has no direct relation to the version of the package (kdelibs4).
(FYI, kdecore by itself does not exist anymore in KDE Frameworks 5).
-- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 15 of July 2014 10:19:33 Jason Newton wrote:
Fair enough although I don't think it's normal to bump the SO version outside of the project major.minor versions (not saying I haven't seen it done but it is more bizarre here). Here's the lovely stacktrace
Do you have locally built openCV? Cheers, Hrvoje
In data martedì 15 luglio 2014 01:19:33, Jason Newton ha scritto:
Gwenview will stop crashing when I rpm -e --no-verify libqt5gui5. Looks like this is not quite a new issue: https://bugs.kde.org/show_bug.cgi?id=322558
From the backtrace, it looks to me that the fault lies entirely in KIPI, as you have suggested, and I can say I'm not too surprised (KIPI has always lots of issues). That said, how do you trigger the crash? I couldn't do so on my KDE:Unstable:SC system. From where you got Qt 5.x installed? -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
kde:current plus kde:qt5 with 5.3 installed, all are only a few days out of
date and its been doing this for a few months. I develop programs against
qt5.
I cant say I did anything really, gwenview window pops up and vanishes an
instant later. i do use opencv for work but i dont think that has any
bearing, i also build my packages in home:jenewton:science, you can test
with that installed if you cant reproduce it - happens on all my machines.
-Jason
On Tue, Jul 15, 2014 at 1:41 AM, Luca Beltrame
In data martedì 15 luglio 2014 01:19:33, Jason Newton ha scritto:
Gwenview will stop crashing when I rpm -e --no-verify libqt5gui5. Looks like this is not quite a new issue: https://bugs.kde.org/show_bug.cgi?id=322558
From the backtrace, it looks to me that the fault lies entirely in KIPI, as you have suggested, and I can say I'm not too surprised (KIPI has always lots of issues).
That said, how do you trigger the crash? I couldn't do so on my KDE:Unstable:SC system. From where you got Qt 5.x installed?
-- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 15 of July 2014 11:54:00 Jason Newton wrote:
... i do use opencv for work but i dont think that has any bearing, i also build my packages in home:jenewton:science, you can test with that installed if you cant reproduce it - happens on all my machines. There's your problem - you build openCV against Qt5. One of kipi-plugins loads libopencv, which tries to load Qt5. And you can't have Qt4 and Qt5 loaded in the same process space...
Cheers, Hrvoje
-Jason
Ugh, dll hell. Why in the world does kipi need highgui I wonder - aux
imread/imwrite but highgui sucks at that anyway. That's the only
library that has anything to do with gui toolkit. The others don't
touch that stuff - in general at least. Well that gives me something
to poke around to next I guess.
On Tue, Jul 15, 2014 at 3:01 AM, šumski
On Tuesday 15 of July 2014 11:54:00 Jason Newton wrote:
... i do use opencv for work but i dont think that has any bearing, i also build my packages in home:jenewton:science, you can test with that installed if you cant reproduce it - happens on all my machines. There's your problem - you build openCV against Qt5. One of kipi-plugins loads libopencv, which tries to load Qt5. And you can't have Qt4 and Qt5 loaded in the same process space...
Cheers, Hrvoje
-Jason -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Culprit was Kipi plugin removeredeyes. I took the lazy way out after
triaging the removal of highgui in the linking. They presently use 3
different cmake FindOpenCV scripts rather than the one that comes with
opencv (didn't always, but they shouldn't be supporting that madness).
They don't specify what components they need (esp when using
MACRO_OPTIONAL_FIND_PACKAGE) which means defaults get linked in which
typically include highgui. libkface and digikam also link against all
these libs. From what I can tell they don't use any highgui
functionality. So that looks like it'll take some time to remove out
which I currently don't have for this.... so I'm just going to live
with a rm'ing the removeredye plugin from the filesysem as that seems
to achieve the desired affect of not crashing for a plugin I never use
anyway.
On Tue, Jul 15, 2014 at 3:17 AM, Jason Newton
Ugh, dll hell. Why in the world does kipi need highgui I wonder - aux imread/imwrite but highgui sucks at that anyway. That's the only library that has anything to do with gui toolkit. The others don't touch that stuff - in general at least. Well that gives me something to poke around to next I guess.
On Tue, Jul 15, 2014 at 3:01 AM, šumski
wrote: On Tuesday 15 of July 2014 11:54:00 Jason Newton wrote:
... i do use opencv for work but i dont think that has any bearing, i also build my packages in home:jenewton:science, you can test with that installed if you cant reproduce it - happens on all my machines. There's your problem - you build openCV against Qt5. One of kipi-plugins loads libopencv, which tries to load Qt5. And you can't have Qt4 and Qt5 loaded in the same process space...
Cheers, Hrvoje
-Jason -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 15 July 2014 12:57:01 Jason Newton wrote:
Culprit was Kipi plugin removeredeyes. I took the lazy way out after triaging the removal of highgui in the linking. They presently use 3 different cmake FindOpenCV scripts rather than the one that comes with opencv (didn't always, but they shouldn't be supporting that madness). They don't specify what components they need (esp when using MACRO_OPTIONAL_FIND_PACKAGE) which means defaults get linked in which typically include highgui. libkface and digikam also link against all these libs. From what I can tell they don't use any highgui functionality.
If you have ideas for improvements inside KIPI/digiKam sources or build system, please discuss them on kde-imaging mailing list. Thanks. -- Christoph Feck http://kdepepo.wordpress.com/ KDE Quality Team -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data martedì 15 luglio 2014 02:54:00, Jason Newton ha scritto: (no need to CC me - I'm subscribed)
kde:current plus kde:qt5 with 5.3 installed, all are only a few days out of date and its been doing this for a few months. I develop programs against qt5.
I've been doing that myself occasionally but I've yet to see a crash in Gwenview. The main difference is that I'm not using openCV. From which repo do KIPI plugins come from? -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
participants (4)
-
Christoph Feck
-
Jason Newton
-
Luca Beltrame
-
šumski