Bug 250285 - Knotify crashes on system start-up
Summary: Knotify crashes on system start-up
Status: RESOLVED DUPLICATE of bug 232068
Alias: None
Product: phonon-backend-gstreamer
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Martin Sandsmark
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-05 16:18 UTC by Richard
Modified: 2011-04-27 21:18 UTC (History)
2 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 Richard 2010-09-05 16:18:13 UTC
Application: knotify4 (4.0)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.5-desktop586-2mnb i686
Distribution: "Mandriva Linux 2010.1"

-- Information about the crash:
Each time i reboot on several machines i get the Knotify crash which also buggers up my sound config in Kmix which is set for onboard sound chip and dvb-t card.
Sound still works but Kmix has become a utter mess and unable to configure sound correctly between apps/dvb-t/system sounds, volume needs to be whacked up high to hear anything with vlc/kaffeine using dvb-t but system sounds so loud it knock my ear wax flying out

The crash can be reproduced every time.

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

Thread 2 (Thread 0xad3c9b70 (LWP 16897)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6166b16 in poll () from /lib/i686/libc.so.6
#2  0xb5e1e1c6 in poll_func (ufds=0x9344560, nfds=2, timeout=-1, userdata=0x9345618) at pulse/thread-mainloop.c:75
#3  0xb5e0aeca in pa_mainloop_poll (m=0x91a9310) at pulse/mainloop.c:879
#4  0xb5e0c70d in pa_mainloop_iterate (m=0x91a9310, block=1, retval=0x0) at pulse/mainloop.c:961
#5  0xb5e0c7e4 in pa_mainloop_run (m=0x91a9310, retval=0x0) at pulse/mainloop.c:979
#6  0xb5e1e0ae in thread (userdata=0x9343d00) at pulse/thread-mainloop.c:94
#7  0xb59f3996 in internal_thread_func (userdata=0x9344420) at pulsecore/thread-posix.c:83
#8  0xb5e7dae5 in start_thread () from /lib/i686/libpthread.so.0
#9  0xb617203e in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb55466d0 (LWP 16798)):
[KCrash Handler]
#6  0xb367ff0c in snd_pcm_ioplug_close (pcm=0x9347c08) at pcm_ioplug.c:743
#7  0xb363b1ee in snd_pcm_close (pcm=0x9347c08) at pcm.c:706
#8  0xb1bbe0af in gst_alsasink_close (asink=0x9334b88) at gstalsasink.c:783
#9  0xb3128ee0 in gst_audioringbuffer_close_device (buf=0x93372e8) at gstaudiosink.c:365
#10 0xb3118468 in gst_ring_buffer_close_device (buf=0x93372e8) at gstringbuffer.c:714
#11 0xb3123292 in gst_base_audio_sink_change_state (element=0x9334b88, transition=GST_STATE_CHANGE_READY_TO_NULL) at gstbaseaudiosink.c:1888
#12 0xb31cb55b in gst_element_change_state () from /usr/lib/libgstreamer-0.10.so.0
#13 0xb31ced37 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#14 0xb31ca8a1 in gst_element_set_state () from /usr/lib/libgstreamer-0.10.so.0
#15 0xb3409db6 in Phonon::Gstreamer::AudioOutput::setOutputDevice (this=0x91a8360, newDevice=...) at /usr/src/debug/phonon-4.4.1/gstreamer/audiooutput.cpp:217
#16 0xb731dcfb in Phonon::callSetOutputDevice (d=0x9194f00, dev=...) at /usr/src/debug/phonon-4.4.1/phonon/audiooutput.cpp:70
#17 0xb731e695 in Phonon::AudioOutputPrivate::setupBackendObject (this=0x9194f00) at /usr/src/debug/phonon-4.4.1/phonon/audiooutput.cpp:314
#18 0xb731f260 in Phonon::AudioOutputPrivate::createBackendObject (this=0x9194f00) at /usr/src/debug/phonon-4.4.1/phonon/audiooutput.cpp:139
#19 0xb731f4e9 in Phonon::AudioOutputPrivate::init (this=0x9194f00, c=Phonon::NotificationCategory) at /usr/src/debug/phonon-4.4.1/phonon/audiooutput.cpp:106
#20 0x0805310c in _start ()

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

Possible duplicates by query: bug 248238, bug 244191, bug 237744.

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2010-09-05 21:49:16 UTC

*** This bug has been marked as a duplicate of bug 232068 ***
Comment 2 Myriam Schweingruber 2011-04-27 21:18:07 UTC
reassigning to the new bugzilla product for better bug tracing of the various backends. Sorry for the noise.