Summary: | Crash in libkdecore.so.5 with Qt5-based app using GStreamer. | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | madcatx |
Component: | kdecore | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | Ben.Kevan, cfeck, thomas, vit |
Priority: | NOR | ||
Version: | 4.10.97 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=353784 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
madcatx
2013-08-12 10:54:50 UTC
> I tried to build kdelibs with -DCMAKE_BUILD_TYPE=Debug but it did not seem to generate a better backtrace.
If you are using some PKGBUILD to build and install kdelibs, do not forget to add '!strip' into the options array.
Thanks, that was it. The top of the backtrace now looks like this: #0 QBasicAtomicInt::ref (this=0x7ffff798c270 <QHashData::shared_null+16>) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 ret = <optimized out> #1 0x00007ffff1c2f160 in __static_initialization_and_destruction_0 (__priority=65535, __initialize_p=1) at /home/madcat/abs/kdelibs/src/kdelibs-4.10.97/kdecore/auth/kauthactionwatcher.cpp:44 No locals. #2 0x000000325c20ea9a in call_init () from /lib64/ld-linux-x86-64.so.2 #3 0x000000325c20eb6c in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2 ... That's an odd backtrace. Does your Qt5 application use GStreamer directly, or do you use Phonon libraries? The issue here is that some "libproxy" tries to load KDE libraries, but the Qt 4 versions, which will of course cause symbol conflicts with Qt5. I suggest to ask gstreamer or glibc developers, where to report issues about library "libproxy". In my opening post is a link to a MWE which crashes for me. "libproxy" appears to be a library for automatic proxy configuration management and it's a dependency of libsoup which in turn is used by GStreamer to access network resources. Very brief research suggests that "libproxy" can interface with kdelibs which is probably why it loads the incorrect libs and bombs the application. This is obviously not a KDE issue, I'm sorry to bother you with this... *** Bug 337597 has been marked as a duplicate of this bug. *** *** Bug 346209 has been marked as a duplicate of this bug. *** *** Bug 359586 has been marked as a duplicate of this bug. *** |