Version: 4.0 (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages Running Ubuntu 8.10 with kubuntu kde 4.2 repository enabled. Intel x64, desktop effects disabled. On receipt of an email in KMail, knotify comes up with a crash dialog. This seems to happen if either popup or sound notifications are enabled in KMail. Backtrace from having sound and popup notifications enabled: Application: KNotify (knotify4), signal SIGSEGV 0x00007fc1f17ac621 in nanosleep () from /lib/libc.so.6 Thread 1 (Thread 0x7fc1f44fd6f0 (LWP 16081)): [KCrash Handler] #5 0x00007fc1f3130ec7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #6 0x00007fc1f3b14b01 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged (this=0x7fc1f3d22b80, _t1=2) at /build/buildd/phonon-4.3.0/obj-x86_64-linux-gnu/phonon/moc_audiooutputadaptor_p.cpp:185 #7 0x00007fc1f3affebe in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange (this=0x251d7d0, device2=@0x7ffffc5327a0, type=Phonon::AudioOutputPrivate::FallbackChange) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:366 #8 0x00007fc1f3b0112f in Phonon::AudioOutputPrivate::setupBackendObject (this=0x251d7d0) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:269 #9 0x00007fc1f3aff84f in Phonon::AudioOutputPrivate::init (this=0x251d7d0, c=<value optimized out>) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:85 #10 0x000000000040c919 in PlayerPool::getPlayer (this=0x24d2a98) at /build/buildd/kdebase-runtime-4.2.0/knotify/notifybysound.cpp:59 #11 0x000000000040cff6 in NotifyBySound::notify (this=0x24d2990, eventId=650, config=<value optimized out>) at /build/buildd/kdebase-runtime-4.2.0/knotify/notifybysound.cpp:237 #12 0x000000000040797a in KNotify::emitEvent (this=0x7ffffc533c10, e=0x2440fe0) at /build/buildd/kdebase-runtime-4.2.0/knotify/knotify.cpp:176 #13 0x000000000040809c in KNotify::event (this=0x7ffffc533c10, event=<value optimized out>, appname=<value optimized out>, contexts=<value optimized out>, text=<value optimized out>, pixmap=@0x7ffffc532c00, actions=@0x2441560, winId=31457281) at /build/buildd/kdebase-runtime-4.2.0/knotify/knotify.cpp:126 #14 0x0000000000408508 in KNotifyAdaptor::event (this=0x25030a0, event=@0x25172b0, fromApp=@0x2509e20, contexts=<value optimized out>, text=@0x25173e0, image=@0x25172f0, actions=@0x2441560, winId=31457281) at /build/buildd/kdebase-runtime-4.2.0/knotify/knotify.cpp:235 #15 0x00000000004091a8 in KNotifyAdaptor::qt_metacall (this=0x25030a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffffc532f70) at /build/buildd/kdebase-runtime-4.2.0/obj-x86_64-linux-gnu/knotify/knotify.moc:208 #16 0x00007fc1f3429ea3 in ?? () from /usr/lib/libQtDBus.so.4 #17 0x00007fc1f342b1b0 in ?? () from /usr/lib/libQtDBus.so.4 #18 0x00007fc1f342b791 in ?? () from /usr/lib/libQtDBus.so.4 #19 0x00007fc1f342baa8 in ?? () from /usr/lib/libQtDBus.so.4 #20 0x00007fc1f312ada5 in QObject::event () from /usr/lib/libQtCore.so.4 #21 0x00007fc1f23eac3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #22 0x00007fc1f23f29ba in QApplication::notify () from /usr/lib/libQtGui.so.4 #23 0x00007fc1f3f2a5db in KApplication::notify (this=0x7ffffc533c40, receiver=0x7ffffc533c10, event=0x2508760) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307 #24 0x00007fc1f311bd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #25 0x00007fc1f311c9fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #26 0x00007fc1f31444d3 in ?? () from /usr/lib/libQtCore.so.4 #27 0x00007fc1eeb49d3b in IA__g_main_context_dispatch (context=0x2448c60) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2144 #28 0x00007fc1eeb4d50d in g_main_context_iterate (context=0x2448c60, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2778 #29 0x00007fc1eeb4d6cb in IA__g_main_context_iteration (context=0x2448c60, may_block=1) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2841 #30 0x00007fc1f314415f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #31 0x00007fc1f247ca6f in ?? () from /usr/lib/libQtGui.so.4 #32 0x00007fc1f311a682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #33 0x00007fc1f311a80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #34 0x00007fc1f311ccbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #35 0x0000000000406cdb in main (argc=1, argv=0x7ffffc533fc8) at /build/buildd/kdebase-runtime-4.2.0/knotify/main.cpp:73
*** Bug 183764 has been marked as a duplicate of this bug. ***
Created attachment 31185 [details] Kontact trace running within GDB
Do you have an USB webcam or microphone (or some other audio/media device?) This is probably related to bug 180109
To Dario: I did have a USB webcam plugged in but I have now unplugged it and the problem remains.
(In reply to comment #4) > To Dario: I did have a USB webcam plugged in but I have now unplugged it and > the problem remains. > Ditto, I did have a webcam attached (but unused), removed it and knotify is still crashing.
*** This bug has been marked as a duplicate of bug 180109 ***
*** This bug has been marked as a duplicate of bug 180109 *** How is it a duplicate? That bug was fixed by unplugging the webcam AND it was related to sound. I do not have any sound notifications selected!
David, is it worth my time to explain that? How about you test the patch?
Well maybe if you explain it would help me to help YOU track down similar bugs in future? How about if I just didn't bother in future?
maybe, if that is so I'm happy to explain. It'll probably take as much of my time as I currently have for Phonon per week, which is why I asked.
I realize comment #8 sounds harsh, but that wasn't intended. Sorry. The questions were purely that. Ignore the negativity that can be read into it, it wasn't meant that way... Sorry, can't find the words to express myself better.
If I may intervene, David's problem appears to originally have been reported in http://bugs.kde.org/show_bug.cgi?id=183764 and marked as a dupe of this bug before a proper trace had been submitted. Looking at the gdb trace he submitted in this thread I cannot see that it is a duplicate (although I do not know how to properly compare a gdb trace with kde's own) and thus the same fix may not work for him. It may be that he is not able to compile a the SVN to test, in which case a link to the appropriate guide could be helpful. Otherwise I would suggest his original bug report be re opened with his trace attached or a new one created.