Bug 161795 - kcmnotify crashes after playing a sound
Summary: kcmnotify crashes after playing a sound
Status: RESOLVED DUPLICATE of bug 158088
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_notify (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Carsten Pfeiffer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-08 15:59 UTC by Stefan Majewsky
Modified: 2008-07-21 18:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Error description and backtrace from GDB (1.80 KB, text/plain)
2008-06-21 15:57 UTC, Stefan Majewsky
Details
KCrash output (6.96 KB, text/plain)
2008-06-21 15:58 UTC, Stefan Majewsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Majewsky 2008-05-08 15:59:07 UTC
Version:            (using KDE 4.0.3)
Installed from:    SuSE RPMs

systemsettings crashes on my openSUSE 11.0 Beta 2 _after_ playing a notification sound. The crash does not occur if I close systemsettings while the sound is playing. The same behavior occurs when kcmnotify is used with kcmshell4.
Comment 1 Stefan Majewsky 2008-05-08 16:02:54 UTC
Please change the product from kcontrol to systemsettings or such. I searched for "kcmnotify" in the bug report wizard, that gave me two equal entries.
Comment 2 FiNeX 2008-05-09 10:38:01 UTC
Could you post a backtrace following the instructions on:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks a lot.
Comment 3 FiNeX 2008-06-21 12:22:59 UTC
@Stefan: Please could you provide a backtrace with the -debug symbols?
Comment 4 Stefan Majewsky 2008-06-21 15:57:43 UTC
Created attachment 25499 [details]
Error description and backtrace from GDB
Comment 5 Stefan Majewsky 2008-06-21 15:58:12 UTC
Created attachment 25500 [details]
KCrash output
Comment 6 Will Stephenson 2008-06-26 09:47:57 UTC
Looks like it's in phonon
Comment 7 Matthias Kretz 2008-06-27 13:37:47 UTC
The second backtrace shows an XIO error handler in the main thread which calls exit() which makes the other thread crash. The crash in phonon_xine is a symptom of a different problem (i.e. the XIO error). From this information alone I can't see that any part of Phonon is "guilty".
Comment 8 David Geiger 2008-07-06 23:17:23 UTC
Same problem for me (KDE 4.0.4, openSUSE 11.0, ).
Backtrace:

[?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65808e0 (LWP 13692)]
[New Thread 0xae5d0b90 (LWP 14126)]
[New Thread 0xaf1dcb90 (LWP 14125)]
[New Thread 0xafafeb90 (LWP 14119)]
[New Thread 0xb02ffb90 (LWP 14118)]
[New Thread 0xb134bb90 (LWP 14117)]
[New Thread 0xb1b4cb90 (LWP 14116)]
[New Thread 0xb251ab90 (LWP 14107)]
[New Thread 0xb2d1bb90 (LWP 14106)]
[New Thread 0xb351cb90 (LWP 14105)]
[New Thread 0xb3d1db90 (LWP 14102)]
[KCrash handler]
#6  0xb4ec4a5e in stream_rewire_video () from /usr/lib/libxine.so.1
#7  0xb2519dfc in ?? ()
#8  0xb4f2e9db in Phonon::Xine::XineThread::event (this=0x83faf30, e=0x852dfb8)
    at /usr/src/debug/kdebase-runtime-4.0.4/phonon/xine/xinethread.cpp:98
#9  0xb6bbfecc in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#10 0xb6bc631e in QApplication::notify () from /usr/lib/libQtGui.so.4
#11 0xb7bd736d in KApplication::notify (this=0xbf90582c, receiver=0x83faf30, 
    event=0x852dfb8)
    at /usr/src/debug/kdelibs-4.0.4/kdeui/kernel/kapplication.cpp:314
#12 0xb765db51 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#13 0xb765e411 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#14 0xb768632a in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#15 0xb765c2ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#16 0xb765c48a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#17 0xb7580be3 in QThread::exec () from /usr/lib/libQtCore.so.4
#18 0xb4f2e728 in Phonon::Xine::XineThread::run (this=0x83faf30)
    at /usr/src/debug/kdebase-runtime-4.0.4/phonon/xine/xinethread.cpp:111
#19 0xb75839b7 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb7527175 in start_thread () from /lib/libpthread.so.0
#21 0xb690ddce in clone () from /lib/libc.so.6

Thread 7 (Thread 0xb1b4cb90 (LWP 14116)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb69041c7 in poll () from /lib/libc.so.6
#2  0xb465ff6c in ao_alsa_handle_event_thread ()
   from /usr/lib/xine/plugins/1.23/xineplug_ao_out_alsa.so
#3  0xb7529bdc in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 6 (Thread 0xb134bb90 (LWP 14117)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb752ac15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4edd9cc in ao_loop () from /usr/lib/libxine.so.1
#3  0x083fe808 in ?? ()

Thread 5 (Thread 0xb02ffb90 (LWP 14118)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb752ac15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4ecf068 in fifo_buffer_get () from /usr/lib/libxine.so.1
#3  0x00000001 in ?? ()

Thread 4 (Thread 0xafafeb90 (LWP 14119)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb752ac15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4ee0ab8 in listener_loop () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 3 (Thread 0xaf1dcb90 (LWP 14125)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb752ac15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4edd9cc in ao_loop () from /usr/lib/libxine.so.1
#3  0x00000001 in ?? ()
#4  0xa1650000 in ?? ()

Thread 2 (Thread 0xae5d0b90 (LWP 14126)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb752af42 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#2  0xb4ed9cde in video_out_loop () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 1 (Thread 0xb65808e0 (LWP 13692)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6906ef1 in select () from /lib/libc.so.6
#2  0xb76848d0 in QEventDispatcherUNIX::select () from /usr/lib/libQtCore.so.4
#3  0xb6c49d2b in ?? () from /usr/lib/libQtGui.so.4
#4  0xb76853af in QEventDispatcherUNIXPrivate::doSelect ()
   from /usr/lib/libQtCore.so.4
#5  0xb7686391 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#6  0xb6c4a0a2 in ?? () from /usr/lib/libQtGui.so.4
#7  0xb765c2ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#8  0xb765c48a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#9  0xb765e66d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#10 0xb6bbfd47 in QApplication::exec () from /usr/lib/libQtGui.so.4
#11 0x0805b847 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 9 Matthias Kretz 2008-07-07 09:25:58 UTC
David Geiger: your backtrace shows a bug introduced by an opensuse patch to phonon-xine. AFAICS this is not the same as the rest of this report.
Comment 10 Olivier Goffart 2008-07-21 18:02:01 UTC

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