Application: knotify4 (4.0) KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3" Qt Version: 4.6.3 Operating System: Linux 2.6.34.7-0.3-desktop x86_64 Distribution: "openSUSE 11.3 (x86_64)" -- Information about the crash: Knotify crashes frequently, possibly every time it is called. I'm currently using Gnome as display manager because the whole system was locking up in KDE. This is on a fresh install of Opensue 11.3. The knotify crash does not cause the system to crash. The crash can be reproduced some of the time. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault [KCrash Handler] #5 0x00007ff824c56200 in QVariant::userType() const () from /usr/lib64/libQtCore.so.4 #6 0x00007ff824f6ff7c in QDBusConnectionPrivate::prepareReply (target=0x63d890, object=<value optimized out>, idx=10, metaTypes=..., msg=...) at qdbusintegrator.cpp:710 #7 0x00007ff824f70c47 in QDBusConnectionPrivate::activateSignal (this=<value optimized out>, hook=..., msg=<value optimized out>) at qdbusintegrator.cpp:729 #8 0x00007ff824f75949 in QDBusConnectionPrivate::handleSignal (this=0x63d890, key=..., msg=...) at qdbusintegrator.cpp:1526 #9 0x00007ff824f75bb4 in QDBusConnectionPrivate::handleSignal (this=0x63d890, msg=...) at qdbusintegrator.cpp:1545 #10 0x00007ff824f75f9e in QDBusConnectionPrivate::handleMessage (this=0x63d890, amsg=...) at qdbusintegrator.cpp:544 #11 0x00007ff824f79c2a in qDBusSignalFilter (connection=<value optimized out>, message=<value optimized out>, data=0x63d890) at qdbusintegrator.cpp:528 #12 0x00007ff820f846dc in dbus_connection_dispatch (connection=0x641b20) at dbus-connection.c:4451 #13 0x00007ff824f6cdf9 in q_dbus_connection_dispatch (this=0x63d890) at qdbus_symbols_p.h:113 #14 QDBusConnectionPrivate::doDispatch (this=0x63d890) at qdbusintegrator.cpp:1079 #15 0x00007ff824f712f5 in QDBusConnectionPrivate::socketRead (this=0x63d890, fd=6) at qdbusintegrator.cpp:1099 #16 0x00007ff824fae703 in QDBusConnectionPrivate::qt_metacall (this=0x63d890, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd02c2880) at .moc/release-shared/moc_qdbusconnection_p.cpp:99 #17 0x00007ff824c4ea1f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #18 0x00007ff824c94fde in QSocketNotifier::activated(int) () from /usr/lib64/libQtCore.so.4 #19 0x00007ff824c5399b in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #20 0x00007ff82402c4d4 in QApplicationPrivate::notify_helper (this=0x649ab0, receiver=0x878d10, e=0x7fffd02c2f30) at kernel/qapplication.cpp:4302 #21 0x00007ff824034aca in QApplication::notify (this=<value optimized out>, receiver=0x878d10, e=0x7fffd02c2f30) at kernel/qapplication.cpp:4185 #22 0x00007ff8259eec06 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #23 0x00007ff824c3ae4c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #24 0x00007ff824c63089 in ?? () from /usr/lib64/libQtCore.so.4 #25 0x00007ff8204aaa93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x00007ff8204ab270 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x00007ff8204ab510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x00007ff824c6367f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #29 0x00007ff8240cd14e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #30 0x00007ff824c3a292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007ff824c3a495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #32 0x00007ff824c3e88b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #33 0x0000000000407f3f in _start () This bug may be a duplicate of or related to bug 226721. Possible duplicates by query: bug 250189, bug 250169, bug 249696, bug 248749, bug 248195. Reported using DrKonqi
Fixed in Qt 4.7.0. *** This bug has been marked as a duplicate of bug 226721 ***