Bug 183256 - KNotify flagged as cause of error durring shutdown.
Summary: KNotify flagged as cause of error durring shutdown.
Status: RESOLVED DUPLICATE of bug 180109
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-05 03:51 UTC by David Swinnard
Modified: 2009-02-15 10:01 UTC (History)
1 user (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 David Swinnard 2009-02-05 03:51:51 UTC
Version:           ? (using KDE 4.2.0)
OS:                Linux
Installed from:    Mandriva RPMs

This is what it reported.  (newby so this may not be complete)  It did not do this while I was running the KDE 4.1.? that came on the Mandriva  2009.0 distribution I loaded initially.  Updated to KDE 4.2 today and this started happening upon shutdown - every time so far.

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.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb63df6d0 (LWP 9159)]
[New Thread 0xb3697b90 (LWP 10178)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe430 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb63df6d0 (LWP 9159))]

Thread 2 (Thread 0xb3697b90 (LWP 10178)):
#0  0xb36aabc3 in pa_mainloop_prepare () from /usr/lib/libpulse.so.0
#1  0xb36aba87 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#2  0xb36abb74 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#3  0xb36b832e in ?? () from /usr/lib/libpulse.so.0
#4  0xb36d9e53 in ?? () from /usr/lib/libpulse.so.0
#5  0xb6a5a315 in start_thread () from /lib/i686/libpthread.so.0
#6  0xb6b93dde in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb63df6d0 (LWP 9159)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6b51ac6 in nanosleep () from /lib/i686/libc.so.6
#2  0xb6b518ae in sleep () from /lib/i686/libc.so.6
#3  0xb7d75a2c in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7d7624e in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb7785aaf in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#7  0xb7b470a5 in ?? () from /usr/lib/libphonon.so.4
#8  0xb7b32e0e in ?? () from /usr/lib/libphonon.so.4
#9  0xb7b33c36 in ?? () from /usr/lib/libphonon.so.4
#10 0xb7b345f8 in ?? () from /usr/lib/libphonon.so.4
#11 0x08054cbf in ?? ()
#12 0x08052ead in ?? ()
#13 0x080531aa in ?? ()
#14 0x0804d68d in _start ()
Comment 1 Dario Andres 2009-02-05 13:06:38 UTC
As you experience the crash every time, 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 David Swinnard 2009-02-05 18:36:25 UTC
After reading the page Dario mentions, I've captured a new backtrace.  I can't find the -debug package to deal with the ?? from /usr/lib/libglib-2.0.so.0

----------------------

Application: KNotify (knotify4), signal SIGSEGV
[Current thread is 1 (Thread 0xb63b96d0 (LWP 10560))]

Thread 2 (Thread 0xb3670b90 (LWP 16814)):
#0  0xb36832a4 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#1  0xb3684a95 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#2  0xb3684b74 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#3  0xb369132e in ?? () from /usr/lib/libpulse.so.0
#4  0xb36b2e53 in ?? () from /usr/lib/libpulse.so.0
#5  0xb6a34315 in start_thread () from /lib/i686/libpthread.so.0
#6  0xb6b6ddde in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb63b96d0 (LWP 10560)):
[KCrash Handler]
#6  QMetaObject::activate (sender=0x0, m=0xb7b36370, local_signal_index=4, argv=0xbff19880) at kernel/qobject.cpp:3097
#7  0xb7b210a5 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged (this=0x0, _t1=0) at /usr/src/debug/phonon-4.3.0/build/phonon/moc_audiooutputadaptor_p.cpp:185
#8  0xb7b0ce0e in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange (this=0x8c27cb0, device2=@0xbff19980, type=Phonon::AudioOutputPrivate::FallbackChange)
    at /usr/src/debug/phonon-4.3.0/phonon/audiooutput.cpp:366
#9  0xb7b0dc36 in Phonon::AudioOutputPrivate::setupBackendObject (this=0x8c27cb0) at /usr/src/debug/phonon-4.3.0/phonon/audiooutput.cpp:269
#10 0xb7b0e5f8 in Phonon::AudioOutputPrivate::init (this=0x8c27cb0, c=Phonon::NotificationCategory) at /usr/src/debug/phonon-4.3.0/phonon/audiooutput.cpp:85
#11 0x08054cbf in Player (this=0x8b6d4e8) at /usr/src/debug/kdebase-runtime-4.2.0/knotify/notifybysound.cpp:59
#12 0x08052ead in PlayerPool::getPlayer (this=0x8bfc08c) at /usr/src/debug/kdebase-runtime-4.2.0/knotify/notifybysound.cpp:99
#13 0x080531aa in NotifyBySound::notify (this=0x8bf0f20, eventId=105, config=0x8bfc610) at /usr/src/debug/kdebase-runtime-4.2.0/knotify/notifybysound.cpp:237
#14 0x0804d68d in KNotify::emitEvent (this=0xbff1a5e0, e=0x8bfc608) at /usr/src/debug/kdebase-runtime-4.2.0/knotify/knotify.cpp:176
#15 0x0804db2e in KNotify::event (this=0xbff1a5e0, event=@0x8c1fa38, appname=@0x8c1f468, contexts=@0xbff19c18, text=@0x8c1efb8, pixmap=@0xbff19bf8, actions=@0x8c1ed58, winId=0)
    at /usr/src/debug/kdebase-runtime-4.2.0/knotify/knotify.cpp:126
#16 0x0804dd9e in KNotifyAdaptor::event (this=0x8c0f3f0, event=@0x8c1fa38, fromApp=@0x8c1f468, contexts=@0x8c1f228, text=@0x8c1efb8, image=@0x8c1f7f8, actions=@0x8c1ed58, winId=<value optimized out>)
    at /usr/src/debug/kdebase-runtime-4.2.0/knotify/knotify.cpp:235
#17 0x0804e552 in KNotifyAdaptor::qt_metacall (this=0x8c0f3f0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbff19db8) at /usr/src/debug/kdebase-runtime-4.2.0/build/knotify/knotify.moc:208
#18 0xb7854ce5 in QDBusConnectionPrivate::deliverCall (this=0x8b69180, object=0x8c0f3f0, msg=@0x8c10590, metaTypes=@0x8b6e44c, slotIdx=8) at qdbusintegrator.cpp:849
#19 0xb7856172 in QDBusConnectionPrivate::activateCall (this=0x8b69180, object=0x8c0f3f0, flags=273, msg=@0x8c10590) at qdbusintegrator.cpp:761
#20 0xb78567e2 in QDBusConnectionPrivate::activateObject (this=0x8b69180, node=@0x8c1057c, msg=@0x8c10590, pathStartPos=1) at qdbusintegrator.cpp:1283
#21 0xb7856b38 in QDBusActivateObjectEvent::placeMetaCall (this=0x8c10550) at qdbusintegrator.cpp:1400
#22 0xb7759782 in QObject::event (this=0xbff1a5e0, e=0x8c10550) at kernel/qobject.cpp:1155
#23 0xb6dfaffc in QApplicationPrivate::notify_helper (this=0x8b75768, receiver=0xbff1a5e0, e=0x8c10550) at kernel/qapplication.cpp:3803
#24 0xb6e03255 in QApplication::notify (this=0xbff1a5f4, receiver=0xbff1a5e0, e=0x8c10550) at kernel/qapplication.cpp:3393
#25 0xb7ce3e20 in KApplication::notify (this=0xbff1a5f4, receiver=0xbff1a5e0, event=0x8c10550) at /usr/src/debug/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307
#26 0xb7749853 in QCoreApplication::notifyInternal (this=0xbff1a5f4, receiver=0xbff1a5e0, event=0x8c10550) at kernel/qcoreapplication.cpp:587
#27 0xb774a535 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8b5c640) at kernel/qcoreapplication.h:209
#28 0xb774a71c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1091
#29 0xb777572d in postEventSourceDispatch (s=0x8b79500) at kernel/qcoreapplication.h:214
#30 0xb66a17ca in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb66a4ee8 in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb66a50a8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb777534a in QEventDispatcherGlib::processEvents (this=0x8b758e8, flags={i = -1074682680}) at kernel/qeventdispatcher_glib.cpp:319
#34 0xb6e99dca in QGuiEventDispatcherGlib::processEvents (this=0x8b758e8, flags={i = -1074682632}) at kernel/qguieventdispatcher_glib.cpp:198
#35 0xb7747ec3 in QEventLoop::processEvents (this=0xbff1a570, flags={i = -1074682568}) at kernel/qeventloop.cpp:143
#36 0xb7748081 in QEventLoop::exec (this=0xbff1a570, flags={i = -1074682504}) at kernel/qeventloop.cpp:194
#37 0xb774a7f2 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#38 0xb6dfae64 in QApplication::exec () at kernel/qapplication.cpp:3331
#39 0x0804cf93 in main (argc=-1074682028, argv=0x14) at /usr/src/debug/kdebase-runtime-4.2.0/knotify/main.cpp:73

Comment 3 Dario Andres 2009-02-05 21:43:37 UTC
@David: the backtrace is already useful, you don't have to install any other package.
Comment 4 Dario Andres 2009-02-05 21:46:21 UTC
Do you have an USB webcam or microphone (or some other audio/media device?)
This is probably related to bug 180109
Comment 5 David Swinnard 2009-02-06 01:20:45 UTC
(In reply to comment #4)
> Do you have an USB webcam or microphone (or some other audio/media device?)
> This is probably related to bug 180109
> 

No web cam and I don't think there is a built in microphone. The only "audio" device would be the CD/DVD drive and the onboard speakers. The laptop is an old Toshiba Satellite 5200 that I have from work.  (it's slow but it has a great screen).

I will check out bug 180109.

Dave
Comment 6 Matthias Kretz 2009-02-15 10:01:11 UTC
it's a bug in the fallback/init code

*** This bug has been marked as a duplicate of bug 180109 ***