Bug 277415 - KNotify crashes - probably system sound related
Summary: KNotify crashes - probably system sound related
Status: RESOLVED DUPLICATE of bug 232068
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knotify (show other bugs)
Version: 4.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-09 11:55 UTC by John Mansfield
Modified: 2011-07-09 13:11 UTC (History)
0 users

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 John Mansfield 2011-07-09 11:55:21 UTC
Application: knotify4 (4.0)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.8-0.2-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
Crashes at times when system sounds would be played (I am not hearing these).  Specifically, I get crashes at KDE startup; also when power adapter is disconnected or reconnected.

I have recently installed XBMC Media centre and UPnP tools (Both of which appear to be working correctly).  The issue appeared subsequently.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f866227f710 (LWP 16664)):
#0  0x00007f867971e6b3 in poll () from /lib64/libc.so.6
#1  0x00007f8677ba741f in ?? () from /usr/lib64/libpulse.so.0
#2  0x00007f8677b991e6 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0
#3  0x00007f8677b99819 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0
#4  0x00007f8677b998d0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0
#5  0x00007f8677ba73bb in ?? () from /usr/lib64/libpulse.so.0
#6  0x00007f86749138e8 in ?? () from /usr/lib64/libpulsecommon-0.9.21.so
#7  0x00007f867801aa4f in start_thread () from /lib64/libpthread.so.0
#8  0x00007f867972782d in clone () from /lib64/libc.so.6
#9  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f867be9c760 (LWP 16566)):
[KCrash Handler]
#5  0x00007f866c4effe9 in snd_pcm_ioplug_close (pcm=<value optimized out>) at pcm_ioplug.c:743
#6  0x00007f866c4ae4a5 in snd_pcm_close (pcm=0x833d10) at pcm.c:706
#7  0x00007f866c4ccdb5 in snd_pcm_plug_close (pcm=<value optimized out>) at pcm_plug.c:71
#8  0x00007f866c4ae4a5 in snd_pcm_close (pcm=0x82ea00) at pcm.c:706
#9  0x00007f8666493818 in ?? () from /usr/lib64/gstreamer-0.10/libgstalsa.so
#10 0x00007f866aed0c9c in gst_audioringbuffer_close_device (buf=<value optimized out>) at gstaudiosink.c:365
#11 0x00007f866aec2dd3 in gst_ring_buffer_close_device (buf=0x81a070) at gstringbuffer.c:687
#12 0x00007f866aecd5a6 in gst_base_audio_sink_change_state (element=0x82f800, transition=GST_STATE_CHANGE_READY_TO_NULL) at gstbaseaudiosink.c:1996
#13 0x00007f866b78e83c in gst_element_change_state (element=0x82f800, transition=<value optimized out>) at gstelement.c:2718
#14 0x00007f866b78f222 in gst_element_set_state_func (element=0x82f800, state=GST_STATE_NULL) at gstelement.c:2674
#15 0x00007f866bfb360a in Phonon::Gstreamer::AudioOutput::setOutputDevice (this=0x83b430, newDevice=...) at /usr/src/debug/phonon-4.4.2/gstreamer/audiooutput.cpp:217
#16 0x00007f867b49ee4c in callSetOutputDevice (this=0x74c680) at /usr/src/debug/phonon-4.4.2/phonon/audiooutput.cpp:70
#17 Phonon::AudioOutputPrivate::setupBackendObject (this=0x74c680) at /usr/src/debug/phonon-4.4.2/phonon/audiooutput.cpp:314
#18 0x00007f867b49f453 in Phonon::AudioOutputPrivate::createBackendObject (this=0x74c680) at /usr/src/debug/phonon-4.4.2/phonon/audiooutput.cpp:139
#19 0x00007f867b49c5d8 in Phonon::AudioOutputPrivate::init (this=0x74c680, c=Phonon::NotificationCategory) at /usr/src/debug/phonon-4.4.2/phonon/audiooutput.cpp:106
#20 0x000000000040cec1 in _start ()

This bug may be a duplicate of or related to bug 248238.

Possible duplicates by query: bug 265229, bug 248238.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-07-09 13:11:12 UTC

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