Application: knotify4 (4.0) KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2" Qt Version: 4.6.3 Operating System: Linux 2.6.34-12-default i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: Always, when knotify is notifying me about something, notification is displayed but after notification faded out knotify crashes. knotify also crashes if I click on a notification. The crash can be reproduced every time. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault [KCrash Handler] #6 0xb6f2d4d4 in QVariant::userType (this=0x0) at kernel/qvariant.cpp:1757 #7 0xb70496c9 in QDBusConnectionPrivate::prepareReply (target=0x807f4c0, object=0x8211ea8, idx=0, metaTypes=..., msg=...) at qdbusintegrator.cpp:710 #8 0xb704a423 in QDBusConnectionPrivate::activateSignal (this=0x807f4c0, hook=..., msg=...) at qdbusintegrator.cpp:729 #9 0xb704f56b in QDBusConnectionPrivate::handleSignal (this=0x807f4c0, key=..., msg=...) at qdbusintegrator.cpp:1526 #10 0xb704f7df in QDBusConnectionPrivate::handleSignal (this=0x807f4c0, msg=...) at qdbusintegrator.cpp:1545 #11 0xb704fc1d in QDBusConnectionPrivate::handleMessage (this=0x807f4c0, amsg=...) at qdbusintegrator.cpp:544 #12 0xb7053c79 in qDBusSignalFilter (connection=0x8081918, message=0x0, data=0x807f4c0) at qdbusintegrator.cpp:528 #13 0xb5c5d67b in dbus_connection_dispatch (connection=0x8081918) at dbus-connection.c:4451 #14 0xb704627b in q_dbus_connection_dispatch (this=0x807f4c0) at qdbus_symbols_p.h:113 #15 QDBusConnectionPrivate::doDispatch (this=0x807f4c0) at qdbusintegrator.cpp:1079 #16 0xb704aacd in QDBusConnectionPrivate::socketRead (this=0x807f4c0, fd=5) at qdbusintegrator.cpp:1099 #17 0xb708d3e5 in QDBusConnectionPrivate::qt_metacall (this=0x807f4c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfcdfdc8) at .moc/release-shared/moc_qdbusconnection_p.cpp:99 #18 0xb6f15efd in QMetaObject::metacall (object=0x807f4c0, cl=QMetaObject::InvokeMetaMethod, idx=8, argv=0xbfcdfdc8) at kernel/qmetaobject.cpp:237 #19 0xb6f24fe8 in QMetaObject::activate (sender=0x820a830, m=0xb702c550, local_signal_index=0, argv=0xbfcdfdc8) at kernel/qobject.cpp:3295 #20 0xb6f718a5 in QSocketNotifier::activated (this=0x820a830, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #21 0xb6f2a45f in QSocketNotifier::event (this=0x820a830, e=0xbfce0224) at kernel/qsocketnotifier.cpp:317 #22 0xb6464c64 in QApplicationPrivate::notify_helper (this=0x8088218, receiver=0x820a830, e=0xbfce0224) at kernel/qapplication.cpp:4302 #23 0xb646cbf7 in QApplication::notify (this=0xbfce0540, receiver=0x820a830, e=0xbfce0224) at kernel/qapplication.cpp:3706 #24 0xb74819d1 in KApplication::notify (this=0xbfce0540, receiver=0x820a830, event=0xbfce0224) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302 #25 0xb6f0fe0e in QCoreApplication::notifyInternal (this=0xbfce0540, receiver=0x820a830, event=0xbfce0224) at kernel/qcoreapplication.cpp:726 #26 0xb6f3b708 in sendEvent (source=0x808ab70) at kernel/qcoreapplication.h:215 #27 socketNotifierSourceDispatch (source=0x808ab70) at kernel/qeventdispatcher_glib.cpp:110 #28 0xb5b93b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0xb5b94350 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0xb5b9460e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0xb6f3bd4b in QEventDispatcherGlib::processEvents (this=0x806b338, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #32 0xb651519a in QGuiEventDispatcherGlib::processEvents (this=0x806b338, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #33 0xb6f0f11d in QEventLoop::processEvents (this=0xbfce0484, flags=...) at kernel/qeventloop.cpp:149 #34 0xb6f0f319 in QEventLoop::exec (this=0xbfce0484, flags=...) at kernel/qeventloop.cpp:201 #35 0xb6f13c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #36 0xb6462164 in QApplication::exec () at kernel/qapplication.cpp:3581 #37 0x0804e53f in _start () This bug may be a duplicate of or related to bug 249696, bug 248195. Possible duplicates by query: bug 249696, bug 248749, bug 248195, bug 246417, bug 246379. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 226721 ***