1. The alsa-utils initscript (re)stores mixer settings. It has nothing to do with reloading sound drivers. Instead, see the /sbin/alsa script. Likewise, the pulseaudio initscript should not touch the sound drivers.
2. Providing a GUI method to kill processes as root already exists, but special-casing a "kill all other sound processes" [that would run as root] GUI method is very bad. It does not resolve the actual bug, which is that a badly configured application will prevent others from having audible sound. The correct solution is to fix the applications. Any other way is just shoddily papering over the bug. On Nov 26, 2009 1:36 PM, "doobiest" <[email protected]> wrote: This is the most relevant bug I can find related to my issue. I dont believe this issue is related to any specific process in particular, I've noticed various times my sound stops working. I'll do an fuser /dev/snd/* and I'll kill any PIDs that it returns. Upon killing those PIDs I instantly hear sound from what ever application was waiting it's turn to get access to my sound device. I've had this issue for years actually, on various versions of ubuntu. 2 things: 1) I'd like /etc/init.d/alsa.utils restart or /tec/init.d/pulseaudio restart to forcefully terminate any processes attached to /dev/snd/* 2) In the interest of customer satisfaction and user-friendliness. Add an option under the context menu for the volume control systray app to kill any of these processes in one click. An option like 'refresh sound device'. That way when any of my less experience friends, who I've convinced to switch to linux, calls me and says, "Hey my sound isnt working", I'll only have to say, "right click on the volume icon and click refresh". No diving into the command line or rebooting to correct this. It's a terrible user experience. More and more end users/low skilled users are giving ubuntu a try because it's awesome and secure and free. Stuff like this will make them switch back to XP and make me cry. I've had this happen often on ubuntu 7 and 8 on several computers. I cannot recall right now if that happens on jaunty. However if no method has been introduced to determine if something is hanging on the sound card's socket then a GUI based option to kill it all off should be added. Everytime I find a little bug that need some console intervention, I wish there was a point and click solution for the less experience people out there. Like a window containing buttons which describe point and click fixes, which invoke a backend script to provide the solution. Something like this could even output the details of the script which can help new users understand how their system just got fixed. Thanks. -- Sound stop working in Intrepid Ibex https://bugs.launchpad.net/bugs/348115 You received this bu... Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: It rarely stop by itself, if I'm only listening to music it can work for hours. However, most of the... -- Sound stop working in Intrepid Ibex https://bugs.launchpad.net/bugs/348115 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
