I believe there are two changes that should be made. The most obvious is that "conf_pulse_hook_load_if_running" needs to connect to PA and confirm it's really running, in that specifically if it's suspended or not. I believe it would be fine if PA was suspended for another reason for applications to 'skip' trying to use it. These should be rare cases and what's the worst that could happen? My though is that an application, like xmms, will start using the hardware and PA won't ever be able to get it back. However, after the unsuspend, applications will start transitioning back to PA... Even with xmms still hogging the HW sink.
The second change is for PA to reject a second attempt to suspend, this should be an error or warning that pasuspender should handle with a stop and exit without running the application it was supposed to. An issue here is that if PA is suspended for another reason, but that's up to the user to discover and fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944295 Title: pasuspender does not stop alsa-lib from defaulting to pulseaudio plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/944295/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
