Bug 226721

Summary: KNotify4 crashes on login [invalid QVariant::userType, QDBusConnectionPrivate::prepareReply, QDBusConnectionPrivate::activateSignal]
Product: [Frameworks and Libraries] kdelibs Reporter: RoDrIgO <caidoberco>
Component: knotifyAssignee: Olivier Goffart <ogoffart>
Status: RESOLVED UPSTREAM    
Severity: crash CC: andresbajotierra, ara, chris.sergent, dair, danil_kl, jbrsubscribe, juntunen, kctcom, kde, lshurr, mail, michael, netman4ttm, nn.dm55, oneforall, ricardoespsanto, Ronny.Standtke, schaiba, tcech, thiago, tingay, trr813, w1az, xmms
Priority: NOR    
Version: 4.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: Qt 4.7.1
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi

Description RoDrIgO 2010-02-13 20:47:21 UTC
Application: knotify4 (4.0)
KDE Platform Version: 4.4.00 (KDE 4.4.0) "release 222"
Qt Version: 4.6.2
Operating System: Linux 2.6.31.12-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

-- Information about the crash:
crash at first time after upgrade to kde 4.4 
just login and system crashes.

 -- Backtrace:
Application: KNotify (knotify4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f36b4a2d7f0 (LWP 4100))]

Thread 5 (Thread 0x7f36a2a53910 (LWP 4285)):
#0  0x00007f36b081f2cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f36a8ab8621 in metronom_sync_loop () from /usr/lib64/libxine.so.1
#2  0x00007f36b081a65d in start_thread () from /lib64/libpthread.so.0
#3  0x00007f36b2254e1d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f36a1550910 (LWP 4287)):
#0  0x00007f36b224bd03 in poll () from /lib64/libc.so.6
#1  0x00007f36af07059c in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f36af0708e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f36b35ee986 in QEventDispatcherGlib::processEvents (this=0x7353d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f36b35c3d42 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f36b35c411c in QEventLoop::exec (this=0x7f36a154ff50, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f36b34ce969 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007f36a8d14a32 in Phonon::MediaSource::type() const () from /usr/lib64/kde4/plugins/phonon_backend/phonon_xine.so
#8  0x00007f36b34d1385 in QThreadPrivate::start (arg=0x6a35e0) at thread/qthread_unix.cpp:248
#9  0x00007f36b081a65d in start_thread () from /lib64/libpthread.so.0
#10 0x00007f36b2254e1d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f36a0b45910 (LWP 4298)):
#0  0x00007f36a0b4bc4e in ao_alsa_handle_event_thread () from /usr/lib64/xine/plugins/1.27/xineplug_ao_out_alsa.so
#1  0x00007f36b081a65d in start_thread () from /lib64/libpthread.so.0
#2  0x00007f36b2254e1d in clone () from /lib64/libc.so.6
#3  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f36a0344910 (LWP 4299)):
#0  0x00007f36b081f049 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f36a8ac9673 in ao_loop () from /usr/lib64/libxine.so.1
#2  0x00007f36b081a65d in start_thread () from /lib64/libpthread.so.0
#3  0x00007f36b2254e1d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f36b4a2d7f0 (LWP 4100)):
[KCrash Handler]
#5  QVariant::userType (this=0x30) at kernel/qvariant.cpp:1752
#6  0x00007f36b38f52b7 in QDBusConnectionPrivate::prepareReply (target=<value optimized out>, object=<value optimized out>, idx=<value optimized out>, metaTypes=<value optimized out>, 
    msg=<value optimized out>) at qdbusintegrator.cpp:710
#7  0x00007f36b38f5447 in QDBusConnectionPrivate::activateSignal (this=0x30, hook=..., msg=...) at qdbusintegrator.cpp:729
#8  0x00007f36b38f7041 in QDBusConnectionPrivate::handleSignal (this=<value optimized out>, key=..., msg=...) at qdbusintegrator.cpp:1526
#9  0x00007f36b38f738b in QDBusConnectionPrivate::handleSignal (this=0x63e860, msg=...) at qdbusintegrator.cpp:1545
#10 0x00007f36b39007b1 in QDBusConnectionPrivate::handleMessage (this=<value optimized out>, amsg=...) at qdbusintegrator.cpp:544
#11 0x00007f36b3904107 in qDBusSignalFilter (connection=<value optimized out>, message=<value optimized out>, data=<value optimized out>) at qdbusintegrator.cpp:530
#12 0x00007f36af91b306 in dbus_connection_dispatch (connection=0x642af0) at dbus-connection.c:4446
#13 0x00007f36b38f4ec9 in q_dbus_connection_dispatch (connection=<value optimized out>) at qdbus_symbols_p.h:113
#14 QDBusConnectionPrivate::doDispatch (connection=<value optimized out>) at qdbusintegrator.cpp:1079
#15 0x00007f36b38f554d in QDBusConnectionPrivate::socketRead (this=0x63e860, fd=5) at qdbusintegrator.cpp:1099
#16 0x00007f36b393a08b in QDBusConnectionPrivate::qt_metacall (this=0x63e860, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff25cce7e0) at .moc/release-shared/moc_qdbusconnection_p.cpp:99
#17 0x00007f36b35d820f in QMetaObject::activate (sender=0x6fa320, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x2) at kernel/qobject.cpp:3285
#18 0x00007f36b362452e in QSocketNotifier::activated (this=0x30, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#19 0x00007f36b35df353 in QSocketNotifier::event (this=0x6fa320, e=0x7fff25ccee90) at kernel/qsocketnotifier.cpp:317
#20 0x00007f36b29a791c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#21 0x00007f36b29adefb in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#22 0x00007f36b43e86a6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#23 0x00007f36b35c542c in QCoreApplication::notifyInternal (this=0x7fff25ccf1d0, receiver=0x6fa320, event=0x7fff25ccee90) at kernel/qcoreapplication.cpp:704
#24 0x00007f36b35eecea in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#25 socketNotifierSourceDispatch (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:110
#26 0x00007f36af06cdee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f36af0707b8 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f36af0708e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#29 0x00007f36b35ee933 in QEventDispatcherGlib::processEvents (this=0x6281b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#30 0x00007f36b2a558fe in ?? () from /usr/lib64/libQtGui.so.4
#31 0x00007f36b35c3d42 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#32 0x00007f36b35c411c in QEventLoop::exec (this=0x7fff25ccf0f0, flags=) at kernel/qeventloop.cpp:201
#33 0x00007f36b35c7e6b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#34 0x0000000000407f5f in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2010-03-09 23:02:40 UTC
*** Bug 230101 has been marked as a duplicate of this bug. ***
Comment 2 Beat Wolf 2010-06-29 13:37:22 UTC
*** Bug 243134 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-06-30 21:17:29 UTC
*** Bug 243231 has been marked as a duplicate of this bug. ***
Comment 4 Tomáš Čech 2010-07-27 10:15:22 UTC
Created attachment 49517 [details]
New crash information added by DrKonqi

knotify4 (4.0) on KDE Platform 4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723)) using Qt 4.6.3

- What I was doing when the application crashed:
Any KDE notification causes the crash - Firefox notification, WICD notifications, etc

-- Backtrace (Reduced):
#6  QVariant::userType (this=0x7f2d00000000) at kernel/qvariant.cpp:1757
#7  0x00007f2d76a1df7c in QDBusConnectionPrivate::prepareReply (target=0x641ac0, object=<value optimized out>, idx=10, metaTypes=..., msg=...) at qdbusintegrator.cpp:710
#8  0x00007f2d76a1ec47 in QDBusConnectionPrivate::activateSignal (this=<value optimized out>, hook=..., msg=<value optimized out>) at qdbusintegrator.cpp:729
#9  0x00007f2d76a23949 in QDBusConnectionPrivate::handleSignal (this=0x641ac0, key=..., msg=...) at qdbusintegrator.cpp:1526
#10 0x00007f2d76a23bb4 in QDBusConnectionPrivate::handleSignal (this=0x641ac0, msg=...) at qdbusintegrator.cpp:1545
Comment 5 Christoph Feck 2010-07-29 23:53:51 UTC
*** Bug 246193 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2010-07-31 23:20:13 UTC
*** Bug 246379 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2010-08-01 23:32:23 UTC
*** Bug 246417 has been marked as a duplicate of this bug. ***
Comment 8 chris 2010-08-07 02:39:23 UTC
Created attachment 49893 [details]
New crash information added by DrKonqi

Knotify crashed with every application needing a motifications
Comment 9 chris 2010-08-07 20:26:36 UTC
Created attachment 49905 [details]
New crash information added by DrKonqi

I was just starting OpenSUSE 11.3. then Kbugbuster reported a segmentation fault when I entered in LXDE.
Comment 10 Christoph Feck 2010-08-18 02:31:09 UTC
*** Bug 248195 has been marked as a duplicate of this bug. ***
Comment 11 Nicolas L. 2010-08-23 09:09:52 UTC
*** Bug 248749 has been marked as a duplicate of this bug. ***
Comment 12 Christoph Feck 2010-08-27 17:18:40 UTC
*** Bug 249220 has been marked as a duplicate of this bug. ***
Comment 13 oneforall 2010-08-28 16:48:37 UTC
ok mine was a dupe . I did try checking but these are a bit hard:) anyway mine was  Bug 249220 . this all i se so far is more dupes. So what Bug number should we be looking at to keep looking for a fix ?
Comment 14 Christoph Feck 2010-09-01 04:58:51 UTC
*** Bug 249696 has been marked as a duplicate of this bug. ***
Comment 15 Christoph Feck 2010-09-02 04:28:10 UTC
Olivier, the following happens:

knotify receives a dbus message, and Qt converts that to a signal. The message received and the slot called should of course have matching paramters. But looking at the backtrace, this is not the case: the slot expects more parameters than the message had.

What could be the reason for that? Is there something that makes sure messages are only sent with a valid number of parameters?

I also reported http://bugreports.qt.nokia.com/browse/QTBUG-13348 to request some sanity checking for that.
Comment 16 Christoph Feck 2010-09-02 15:20:36 UTC
The bug report mentioned in comment #15 got accepted upstream, resolving this one.

If everything works well, the fix will be in Qt 4.7.1.
Comment 17 Christoph Feck 2010-09-02 15:51:06 UTC
*** Bug 243138 has been marked as a duplicate of this bug. ***
Comment 18 Thiago Macieira 2010-09-02 17:16:34 UTC
Patch landed in Qt 4.7.1
Comment 19 Thiago Macieira 2010-09-02 17:42:35 UTC
Actually, I can't reproduce the bug.
Comment 20 Christoph Feck 2010-09-04 15:21:05 UTC
*** Bug 250169 has been marked as a duplicate of this bug. ***
Comment 21 Christoph Feck 2010-09-05 02:29:08 UTC
*** Bug 250189 has been marked as a duplicate of this bug. ***
Comment 22 Christoph Feck 2010-09-09 00:50:06 UTC
*** Bug 243140 has been marked as a duplicate of this bug. ***
Comment 23 Christoph Feck 2010-09-09 00:50:38 UTC
*** Bug 243137 has been marked as a duplicate of this bug. ***
Comment 24 Christoph Feck 2010-09-09 00:51:15 UTC
*** Bug 192714 has been marked as a duplicate of this bug. ***
Comment 25 Christoph Feck 2010-10-13 17:03:43 UTC
*** Bug 254078 has been marked as a duplicate of this bug. ***
Comment 26 Christoph Feck 2010-10-20 03:12:41 UTC
*** Bug 254718 has been marked as a duplicate of this bug. ***
Comment 27 Christoph Feck 2010-11-10 01:18:34 UTC
*** Bug 256484 has been marked as a duplicate of this bug. ***
Comment 28 Dario Andres 2010-12-17 17:12:32 UTC
*** Bug 260383 has been marked as a duplicate of this bug. ***
Comment 29 Christoph Feck 2010-12-20 15:04:13 UTC
*** Bug 260793 has been marked as a duplicate of this bug. ***
Comment 30 Christoph Feck 2011-02-08 22:10:12 UTC
*** Bug 265841 has been marked as a duplicate of this bug. ***
Comment 31 Christoph Feck 2011-03-24 13:26:47 UTC
*** Bug 269288 has been marked as a duplicate of this bug. ***
Comment 32 Christoph Feck 2012-02-06 01:42:23 UTC
*** Bug 293171 has been marked as a duplicate of this bug. ***
Comment 33 Christoph Feck 2012-02-22 11:07:20 UTC
*** Bug 294588 has been marked as a duplicate of this bug. ***