Hi, On Sat, Apr 14, 2012 at 1:43 PM, Paul Menzel <paulepanter at users.sourceforge.net> wrote: > Dear Mira, > > > Am Samstag, den 14.04.2012, 01:51 +0200 schrieb Jarom?r Mike?: > >> I am experiencing lost of audio from iceweasel browser after every suspend of system. > > 1. does sound work with other applications after resume? > 2. Is that a regression or has this not been working since the > beginning? > 3. What are you doing exactly? You use Iceweasel, open a movie/audio > file, play it in the integrated player, suspend, resume and then audio > does not work anymore? I can't reproduce this problem on a similar configuration of debian testing amd64, so I'm going to wager a guess that this may be hardware-specific. We may need to know more information about Mira's hardware. For my part, can't reproduce the problem with an Intel 82801JI (ICH10R) HD Audio chipset from the onboard sound of an Asus P6T Deluxe motherboard (based on Intel X58 chipset). My manual test script is as follows: 1. Start Firefox or Iceweasel 2. Play audio through Adobe Flash *and* through the built-in support for e.g. VP8 or Ogg/Vorbis and ensure that it works correctly, then stop the audio (didn't test the case where you suspend *while* audio is playing) 3. Suspend to RAM 4. Resume back from Suspend to RAM 5. Play more audio and ensure that it works correctly By "correctly" I mean, it doesn't skip or pop after testing it for 5 or 10 seconds. Doesn't mean that it's 100% reliable or as low-latency as it should be :P Not sure what other ill effects suspend to RAM might have if I were to rapidly suspend and resume dozens of times... did not test that. Lastly: one thing I always suggest to those who have problems with PulseAudio is, try killing PA and playing audio through a plain ALSA application. Try something like `aplay` or `gst-launch-0.10` with alsa hw:0 device or similar, to avoid going through PA. If you can reproduce the defect with pure ALSA without pulseaudio involved, 99.9999% chance it's not a PA bug, but an alsa-lib or alsa-kernel bug. That should be reported upstream IMHO, esp. if you're using the latest stable kernel or newer. HTH, Sean > >> Exists any solution for this behavior? >> >> pulseaudio 1.1-3 >> debian amd64 testing > > Please take a look at the Debian bug tracking system [1]. Can you find a > report mentioning a ?similar problem? If not please report a bug using > `reportbug pulseaudio`. Although PulseAudio the maintenance of these > reports are at a bad state. (I will open a separate thread about that.) > >> Please let me know if you need any additional information. > > I could not find the debugging page in the Wiki moved to freedesktop.org > [2]. So please read the Wiki pages from Fedora [3] and Ubuntu [4]. The > manual pages explain the options pretty well too. You can access them > running the following in a terminal. > > ? ?man pulse-client.conf > > > Thanks, > > Paul > > > [1] http://bugs.debian.org/pulseaudio > [2] http://www.freedesktop.org/wiki/Software/PulseAudio > [3] http://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems > [4] https://wiki.ubuntu.com/PulseAudio/Log > > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss >
