** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/202089
Title: Pulseaudio is blocking normal sound after resume Status in PulseAudio sound server: Fix Released Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “pulseaudio” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Intrepid: Invalid Status in “pulseaudio” source package in Intrepid: Fix Released Status in “gnome-power-manager” source package in Jaunty: Invalid Status in “pulseaudio” source package in Jaunty: Won't Fix Status in “gnome-power-manager” package in Baltix: Invalid Bug description: jaunty SRU information follows: Note that this SRU involves two separate bugs, this one and bug 326532. Impact: Users who experience problems with PulseAudio often kill it (using "pulseaudio -k" or "killall pulseaudio", the latter of which is more reliable). Jaunty's current pm-utils sleep hook looks for the session-invoked command line. Users who invoke pulseaudio manually, after killing it, with "pulseaudio -D" (or other variants) do not have this session-invoked command line, and thus, when they suspend to ram or disk, the pm-utils sleep hook does not suspend their pulseaudio daemons. Note that the use case of killing the pulseaudio daemon and allowing it to autospawn afterward is unaffected; jaunty's existing pm-utils sleep hook correctly reaps all pulseaudio instances. This SRU only applies to manually invoked "pulseaudio -D", "pulseaudio -vvv", etc. Resolution: Modify the pm-utils sleep hook to correctly reap all pulseaudio instances regardless of pulseaudio invocation command line. SRU debdiff: http://launchpadlibrarian.net/25941550/pulseaudio_0.9.14-0ubuntu20.1.debdiff TEST CASE: Boot into a jaunty install. In a Terminal, issue "killall pulseaudio;pulseaudio -D". Suspend to ram, then resume. Note the inaudible audio from PulseAudio. Regression potential: No regressions have been identified in production. -- old intrepid SRU information follows: Impact: A portion of users with a default or updated (intrepid- updates) Ubuntu 8.10 install experience inaudible audio from PulseAudio after resuming from suspend-to-ram. This symptom is due to the PulseAudio daemon not having received proper notification to suspend clients and release the sound device(s). Resolution: Configure users' pulseaudio daemons to suspend prior to suspending to ram and to resume after resuming. This sequence is accomplished via a pm-utils sleep hook. The corresponding fixed version (0.9.13-2ubuntu3) is available in jaunty. SRU debdiff: http://launchpadlibrarian.net/20316781/pulseaudio_0.9.10-2ubuntu9.2.debdiff TEST CASE: Boot into a default or updated (intrepid-updates) Ubuntu 8.10 install. Suspend to ram, then resume. Note the inaudible audio from PulseAudio. Regression potential: No regressions have been identified in production. Background information follows: Binary package hint: pulseaudio > aplay squish.au Sonando Audio Sparc 'squish.au' : Mu-Law, Ratio 8000 Hz, Mono [Suspend to Ram/Resume] > aplay squish.au ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave aplay: main:546: error al abrir audio: Dispositivo ó recurso ocupado Then you need to killall pulseaudio for apps that use pcm starts working again. (Question: How you can stop/start/restart pulseudio? In Ubuntu /etc/init.d/pulseaudio script is disabled) If you need more information, please let me know. Thx. ---------------------------------- Hardy Uptodate IBM Thinkpad X41 Tablet pulseaudio 0.9.9-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/202089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
