User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.8.1.4) Gecko/20070531 Firefox/2.0.0.4 Build Identifier: Whenever i restart the alsa daemon, the mixer icon in the panel disappears (for good, until readded) and a strange thing happens to all other panels. The best way to describe it is "gtk2 layout suddenly starts looking like ulgy gtk1 layout". I've learned that this is because the mixer keeps the audio control open and when alsa gets killed the mixer dies. The solution might be redesigning this applet so that there always is a backend process handling the mixer, and the applet contacting it through IPC. Reproducible: Always
This is a big problem for me. I almost never shut my notebook down, but instead i use tuxonice to suspend to disk. As part of the suspend/resume process, tuxonice shuts down alsa, presumably because it can't handle being suspended. Every time I suspend, I lose my volume control panel plugin and have to readd it (it's gone for good). The mixer plugin should survive the loss of the sound service and should resume functioning when the sound service comes back.
I have a similar problem - I'm using pulse audio with alsa plugin, so that I can control the volume with xfce volume control plugin. But when I suspend pulse audio because of unsupported application (which probably disconnects pulse and switches to pure ALSA) - the volume control stops working. It still sits in the panel but when I use mouse wheel to change the volume, volume doesn't change and the bar resets to the previous level. Opening plugin properties and clicking Ok fixes the bad behavior. The same thing has to be done when pulse audio comes back from suspension.
is this scenario supported by the ALSA API? I've no idea how to find out that ALSA will soon go over the jordan. Does alsa-lib have a callback or something I could use?
Ok, maybe I have a way. Check the 4.4 branch, I committed something that should detect when the driver is being removed (ALSA only)...
*** Bug 2167 has been marked as a duplicate of this bug. ***