Bug 180109 - knotify4 crashes when receiving a message in kopete
Summary: knotify4 crashes when receiving a message in kopete
Status: RESOLVED FIXED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
: 181579 183256 183485 183728 184389 185116 185389 185914 190872 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-09 10:36 UTC by Christophe Prud'homme
Modified: 2009-04-28 00:49 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Prud'homme 2009-01-09 10:36:47 UTC
Version:           0.60.82 (using 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-1-686-bigmem

when receiving a message (msn) in  kopete, knotify4 crashes

all other notifications from kopete or other apps don't crash (at least none that I have seen.
Comment 1 Dario Andres 2009-01-09 12:17:14 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Christophe Prud'homme 2009-01-09 16:52:14 UTC
The crash  is in fact in phonon

I suspect that it has to do with the type of device. I managed
I fixed the bug by unplugging my usbwebcam (with a mic) and plugging a USB
headset (with a mic)

here  is a backtrace

Application: KNotify (knotify4), signal SIGSEGV

Thread 1 (Thread 0xb66016c0 (LWP 6493)):
[KCrash Handler]
#6  QMetaObject::activate (sender=0x0, m=0xb7c1e430, local_signal_index=4,
argv=0xbf8f570c) at kernel/qobject.cpp:3097
#7  0xb7c17433 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged
(this=0x0, _t1=-3) at ./moc_audiooutputadaptor_p.cpp:185
#8  0xb7c00676 in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange
(this=0x9e5fc88, device2=@0xbf8f5804,
type=Phonon::AudioOutputPrivate::FallbackChange) at
../../phonon/audiooutput.cpp:366The crash  is in fact in phonon

I suspect that it has to do with the type of device. I managed
I fixed the bug by unplugging my usbwebcam (with a mic) and plugging a USB
headset (with a mic)

here  is a backtrace

Application: KNotify (knotify4), signal SIGSEGV

Thread 1 (Thread 0xb66016c0 (LWP 6493)):
[KCrash Handler]
#6  QMetaObject::activate (sender=0x0, m=0xb7c1e430, local_signal_index=4,
argv=0xbf8f570c) at kernel/qobject.cpp:3097
#7  0xb7c17433 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged
(this=0x0, _t1=-3) at ./moc_audiooutputadaptor_p.cpp:185
#8  0xb7c00676 in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange
(this=0x9e5fc88, device2=@0xbf8f5804,
type=Phonon::AudioOutputPrivate::FallbackChange) at
../../phonon/audiooutput.cpp:366
#9  0xb7c0190a in Phonon::AudioOutputPrivate::setupBackendObject
(this=0x9e5fc88) at ../../phonon/audiooutput.cpp:269
#10 0xb7bfffe5 in Phonon::AudioOutputPrivate::init (this=0x9e5fc88,
c=Phonon::NotificationCategory) at ../../phonon/audiooutput.cpp:85
#11 0x08053204 in _start ()

  190a in Phonon::AudioOutputPrivate::setupBackendObject
(this=0x9e5fc88) at ../../phonon/audiooutput.cpp:269
#10 0xb7bfffe5 in Phonon::AudioOutputPrivate::init (this=0x9e5fc88,
c=Phonon::NotificationCategory) at ../../phonon/audiooutput.cpp:85
#11 0x08053204 in _start ()

  
Comment 3 Christophe Prud'homme 2009-01-13 12:02:21 UTC
here is another backtrace: crash is kmail while selecting a file to be added as attachment

Application: KMail (kmail), signal SIGSEGV

Thread 1 (Thread 0xb40066c0 (LWP 17766)):
[KCrash Handler]
#6  QMetaObject::activate (sender=0x0, m=0xb58ef430, local_signal_index=4, argv=0xbfba8fdc) at kernel/qobject.cpp:3097
#7  0xb58e8433 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged (this=0x0, _t1=-3) at ./moc_audiooutputadaptor_p.cpp:185
#8  0xb58d1676 in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange (this=0x97134e0, device2=@0xbfba90d4, type=Phonon::AudioOutputPrivate::FallbackChange) at ../../phonon/audiooutput.cpp:366
#9  0xb58d290a in Phonon::AudioOutputPrivate::setupBackendObject (this=0x97134e0) at ../../phonon/audiooutput.cpp:269
#10 0xb58d0fe5 in Phonon::AudioOutputPrivate::init (this=0x97134e0, c=Phonon::NoCategory) at ../../phonon/audiooutput.cpp:85
#11 0xb0b19b05 in KFileAudioPreview (this=0x945da50, parent=0x9216ec8) at ../../../../interfaces/kmediaplayer/kfileaudiopreview/kfileaudiopreview.cpp:81
#12 0xb0b1a631 in KPluginFactory::createInstance<KFileAudioPreview, QWidget> (parentWidget=0x9216ec8, parent=0x9216ec8, args=@0xbfba9304) at ../../../../kdecore/util/kpluginfactory.h:461
#13 0xb7b833bf in KPluginFactory::create (this=0x933b6e0, iface=0xb526ebc0 "KPreviewWidgetBase", parentWidget=0x9216ec8, parent=0x9216ec8, args=@0xbfba9304, keyword=@0xbfba92fc)
    at ../../kdecore/util/kpluginfactory.cpp:191
#14 0xb51de630 in KFileMetaPreview::createAudioPreview (parent=0x9216ec8) at ../../kdecore/util/kpluginfactory.h:491
#15 0xb51de967 in KFileMetaPreview::previewProviderFor (this=0x95fe808, mimeType=@0xbfba93b4) at ../../kio/kfile/kfilemetapreview.cpp:109
#16 0xb51de447 in KFileMetaPreview::showPreview (this=0x95fe808, url=@0x9436e50) at ../../kio/kfile/kfilemetapreview.cpp:140
#17 0xb0a93642 in KDirOperator::Private::_k_showPreview (this=0x9436de0) at ../../kfile/kdiroperator.cpp:2418
#18 0xb0a93cfd in KDirOperator::Private::_k_triggerPreview (this=0x9436de0, index=@0x9608538) at ../../kfile/kdiroperator.cpp:2408
#19 0xb0aa04aa in KDirOperator::qt_metacall (this=0x93da470, _c=QMetaObject::InvokeMetaMethod, _id=63, _a=0xbfba952c) at ./kdiroperator.moc:246
#20 0xb6fe8be0 in QMetaObject::activate (sender=0x93b8920, from_signal_index=35, to_signal_index=35, argv=0xbfba952c) at kernel/qobject.cpp:3031
#21 0xb6fe9962 in QMetaObject::activate (sender=0x93b8920, m=0xb6e7b644, local_signal_index=4, argv=0xbfba952c) at kernel/qobject.cpp:3101
#22 0xb6b87213 in QAbstractItemView::entered (this=0x93b8920, _t1=@0x9608538) at .moc/release-shared/moc_qabstractitemview.cpp:337
#23 0xb6b9272b in QAbstractItemView::mouseMoveEvent (this=0x93b8920, event=0xbfba9f2c) at itemviews/qabstractitemview.cpp:1531
#24 0xb6baa512 in QListView::mouseMoveEvent (this=0x93b8920, e=0xbfba9f2c) at itemviews/qlistview.cpp:801
#25 0xb672162b in QWidget::event (this=0x93b8920, event=0xbfba9f2c) at kernel/qwidget.cpp:7148
#26 0xb6a54d43 in QFrame::event (this=0x93b8920, e=0xbfba9f2c) at widgets/qframe.cpp:651
#27 0xb6aeb46f in QAbstractScrollArea::viewportEvent (this=0x93b8920, e=0x0) at widgets/qabstractscrollarea.cpp:943
#28 0xb6b9692f in QAbstractItemView::viewportEvent (this=0x93b8920, event=0xbfba9f2c) at itemviews/qabstractitemview.cpp:1429
#29 0xb6aeda15 in QAbstractScrollAreaFilter::eventFilter (this=0x93932d8, o=0x9392960, e=0xbfba9f2c) at widgets/qabstractscrollarea_p.h:96
#30 0xb6fd32ca in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x85c2fb0, receiver=0x9392960, event=0xbfba9f2c) at kernel/qcoreapplication.cpp:694
#31 0xb66c977a in QApplicationPrivate::notify_helper (this=0x85c2fb0, receiver=0x9392960, e=0xbfba9f2c) at kernel/qapplication.cpp:3799
#32 0xb66d1fd1 in QApplication::notify (this=0xbfbab518, receiver=0x9392960, e=0xbfba9f2c) at kernel/qapplication.cpp:3528
#33 0xb7da97fd in KApplication::notify (this=0xbfbab518, receiver=0x9392960, event=0xbfba9f2c) at ../../kdeui/kernel/kapplication.cpp:307
#34 0xb6fd40e1 in QCoreApplication::notifyInternal (this=0xbfbab518, receiver=0x9392960, event=0xbfba9f2c) at kernel/qcoreapplication.cpp:587
#35 0xb66d125e in QApplicationPrivate::sendMouseEvent (receiver=0x9392960, event=0xbfba9f2c, alienWidget=0x9392960, nativeWidget=0xbfbaa5a8, buttonDown=0xb6e8c670, lastMouseReceiver=@0xb6e8c674)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212
#36 0xb673ae2d in QETWidget::translateMouseEvent (this=0xbfbaa5a8, event=0xbfbaa418) at kernel/qapplication_x11.cpp:4044
#37 0xb6739c11 in QApplication::x11ProcessEvent (this=0xbfbab518, event=0xbfbaa418) at kernel/qapplication_x11.cpp:3162
#38 0xb67641d8 in QEventDispatcherX11::processEvents (this=0x85bb460, flags={i = -1078287176}) at kernel/qeventdispatcher_x11.cpp:128
#39 0xb6fd27aa in QEventLoop::processEvents (this=0xbfbaa52c, flags={i = -1078287112}) at kernel/qeventloop.cpp:143
#40 0xb6fd296a in QEventLoop::exec (this=0xbfbaa52c, flags={i = -1078287052}) at kernel/qeventloop.cpp:194
#41 0xb6b32647 in QDialog::exec (this=0xbfbaa5a8) at dialogs/qdialog.cpp:447
#42 0xb73364cc in ?? () from /usr/lib/libkmailprivate.so.4
#43 0xb7357c46 in ?? () from /usr/lib/libkmailprivate.so.4
#44 0xb6fe8be0 in QMetaObject::activate (sender=0x929b120, from_signal_index=5, to_signal_index=6, argv=0xbfbaa74c) at kernel/qobject.cpp:3031
#45 0xb6fe8fe0 in QMetaObject::activate (sender=0x929b120, m=0xb6e703d8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfbaa74c) at kernel/qobject.cpp:3121
#46 0xb66c34a1 in QAction::triggered (this=0x929b120, _t1=false) at .moc/release-shared/moc_qaction.cpp:216
#47 0xb66c3e0f in QAction::activate (this=0x929b120, event=QAction::Trigger) at kernel/qaction.cpp:1125
#48 0xb6ae52a2 in QToolButton::nextCheckState (this=0x0) at ../../include/QtGui/../../src/gui/kernel/qaction.h:195
#49 0xb6a08a63 in QAbstractButtonPrivate::click (this=0x9329a58) at widgets/qabstractbutton.cpp:520
#50 0xb6a08d36 in QAbstractButton::mouseReleaseEvent (this=0x92ff168, e=0xbfbaae1c) at widgets/qabstractbutton.cpp:1110
#51 0xb6ae579c in QToolButton::mouseReleaseEvent (this=0x92ff168, e=0xbfbaae1c) at widgets/qtoolbutton.cpp:671
#52 0xb67217c2 in QWidget::event (this=0x92ff168, event=0xbfbaae1c) at kernel/qwidget.cpp:7163
#53 0xb6a06d4e in QAbstractButton::event (this=0x92ff168, e=0xbfbaae1c) at widgets/qabstractbutton.cpp:1072
#54 0xb6ae5264 in QToolButton::event (this=0x92ff168, e=0xbfbaae1c) at widgets/qtoolbutton.cpp:1103
#55 0xb66c979c in QApplicationPrivate::notify_helper (this=0x85c2fb0, receiver=0x92ff168, e=0xbfbaae1c) at kernel/qapplication.cpp:3803
#56 0xb66d1fd1 in QApplication::notify (this=0xbfbab518, receiver=0x92ff168, e=0xbfbaae1c) at kernel/qapplication.cpp:3528
#57 0xb7da97fd in KApplication::notify (this=0xbfbab518, receiver=0x92ff168, event=0xbfbaae1c) at ../../kdeui/kernel/kapplication.cpp:307
#58 0xb6fd40e1 in QCoreApplication::notifyInternal (this=0xbfbab518, receiver=0x92ff168, event=0xbfbaae1c) at kernel/qcoreapplication.cpp:587
#59 0xb66d125e in QApplicationPrivate::sendMouseEvent (receiver=0x92ff168, event=0xbfbaae1c, alienWidget=0x92ff168, nativeWidget=0x923c988, buttonDown=0xb6e8c670, lastMouseReceiver=@0xb6e8c674)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212
#60 0xb673ae2d in QETWidget::translateMouseEvent (this=0x923c988, event=0xbfbab308) at kernel/qapplication_x11.cpp:4044
#61 0xb6739c11 in QApplication::x11ProcessEvent (this=0xbfbab518, event=0xbfbab308) at kernel/qapplication_x11.cpp:3162
#62 0xb67641d8 in QEventDispatcherX11::processEvents (this=0x85bb460, flags={i = -1078283352}) at kernel/qeventdispatcher_x11.cpp:128
#63 0xb6fd27aa in QEventLoop::processEvents (this=0xbfbab420, flags={i = -1078283288}) at kernel/qeventloop.cpp:143
#64 0xb6fd296a in QEventLoop::exec (this=0xbfbab420, flags={i = -1078283224}) at kernel/qeventloop.cpp:194
#65 0xb6fd5025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#66 0xb66c9617 in QApplication::exec () at kernel/qapplication.cpp:3331
#67 0x0804a6a0 in _start ()

Comment 4 Cassiano Leal 2009-01-16 13:57:34 UTC
I have a similar problem. Debian Sid with packages from kde42.debian.net. 

kdebase-runtime's svn revision is 906968.

The backtrace doesn't seem to be very useful, though. Is there a way I can make it work better? Follows:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[Thread debugging using libthread_db enabled]
0xb7f5b424 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb65976c0 (LWP 4178))]

Thread 1 (Thread 0xb65976c0 (LWP 4178)):
#0  0xb7f5b424 in __kernel_vsyscall ()
#1  0xb6beaed0 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6bead0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7dfd048 in KCrash::startDrKonqi (argv=0xbfc76608, argc=17) at ../../kdeui/util/kcrash.cpp:412
#4  0xb7dfda54 in KCrash::defaultCrashHandler (sig=11) at ../../kdeui/util/kcrash.cpp:337
#5  <signal handler called>
#6  QMetaObject::activate (sender=0x0, m=0xb7bb4430, local_signal_index=4, argv=0xbfc769bc) at kernel/qobject.cpp:3097
#7  0xb7bad433 in ?? () from /usr/lib/libphonon.so.4
#8  0x00000000 in ?? ()
Comment 5 Dario Andres 2009-01-16 13:59:56 UTC
@Cassiano:
Read: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

If you get an *exactly* backtrace as the one reported in comment 0, you can add your information in this report. If it's different you need to file a new bug report. Thanks :)
Comment 6 Dario Andres 2009-02-05 21:46:55 UTC
*** Bug 181579 has been marked as a duplicate of this bug. ***
Comment 7 Jay Ambee 2009-02-10 16:48:51 UTC
Instead of constantly hooking on formalia it would be nicer if you would SOLVE the problem, which is the same for me and constantly gives the same report pointing to libphonon.so.4

and as far as I am concerned, from my experiences during the last weeks:

PHONON SUCKS!!! Give me back alsa!!

I could name about a dozen reasons where phonon produces crashes in applications you wouldn't dream of ...

Sorry for being rude but this software is crap if you ask me ... 

Jay

In reply to comment #5)
> @Cassiano:
> Read:
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> 
> If you get an *exactly* backtrace as the one reported in comment 0, you can add
> your information in this report. If it's different you need to file a new bug
> report. Thanks :)
> 

Comment 8 Dario Andres 2009-02-10 17:22:14 UTC
(In reply to comment #7)
> Instead of constantly hooking on formalia it would be nicer if you would SOLVE
> the problem, which is the same for me and constantly gives the same report
> pointing to libphonon.so.4

I'm not a Phonon developer (I can't triage the crash or solve it) , I'm just only trying to organize the bugtracker reports (in order to help the real developers to focus their time and effort into developing instead of looking for tons of useless and duplicate reports) and I need some information from the reporters.

> and as far as I am concerned, from my experiences during the last weeks:
> Give me back alsa!!

You can use a custom application to play notifications instead of Phonon. (for example: the "play" command from the SOX package). You can configure it in SystemSettings/Notifications/Player Settings(tab)

Regards
Comment 9 George Kiagiadakis 2009-02-10 17:46:41 UTC
Can you please try using the phonon-xine backend? We had some similar reports in debian about phonon crashing when using the gstreamer backend, because gstreamer packages don't install by default all the required codecs.

Thanks.
Comment 10 Matthias Kretz 2009-02-11 20:32:11 UTC
*** Bug 183728 has been marked as a duplicate of this bug. ***
Comment 11 Matthias Kretz 2009-02-11 20:34:41 UTC
Can any of you that can reproduce the problem please test the Phonon 4.3 branch? I'm fairly certain that http://websvn.kde.org/branches/phonon/4.3/phonon/audiooutput.cpp?r1=914375&r2=921034 fixes it. Please somebody confirm.
Comment 12 vivaelamor84 2009-02-11 23:24:48 UTC
(In reply to comment #11)
> Can any of you that can reproduce the problem please test the Phonon 4.3
> branch? I'm fairly certain that
> http://websvn.kde.org/branches/phonon/4.3/phonon/audiooutput.cpp?r1=914375&r2=921034
> fixes it. Please somebody confirm.
> 

Hi, I just compiled phonon 4.3 SVN as you said and can confirm that so far.. new message in kmail doesn't crash. Incidentally, knotify tells me that my default audio device isn't set right, and that it is falling back to 'default' which is presumably what triggered the whole thing in the first place.

Thanks, and here's hoping it works for everyone else :)
Comment 13 Matthias Kretz 2009-02-15 09:53:58 UTC
*** Bug 183485 has been marked as a duplicate of this bug. ***
Comment 14 Matthias Kretz 2009-02-15 09:55:00 UTC
fixed in branch/trunk
Comment 15 Matthias Kretz 2009-02-15 10:01:11 UTC
*** Bug 183256 has been marked as a duplicate of this bug. ***
Comment 16 Matthias Kretz 2009-02-15 13:54:19 UTC
*** Bug 184389 has been marked as a duplicate of this bug. ***
Comment 17 Matthias Kretz 2009-02-15 13:55:31 UTC
BTW, you should be able to work around this bug by going to system settings -> multimedia and there change the device preference such that a valid device is on top. The bug triggers when it starts out with a non-working device.
Comment 18 Dario Andres 2009-02-21 13:37:19 UTC
*** Bug 185116 has been marked as a duplicate of this bug. ***
Comment 19 Dario Andres 2009-02-24 23:26:37 UTC
*** Bug 185389 has been marked as a duplicate of this bug. ***
Comment 20 Dario Andres 2009-03-06 14:28:37 UTC
*** Bug 185914 has been marked as a duplicate of this bug. ***
Comment 21 Dario Andres 2009-04-28 00:49:18 UTC
*** Bug 190872 has been marked as a duplicate of this bug. ***