Michael B. Trausch, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingSoundProblems ?
As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux <replace-with-bug-number> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: needs-upstream-testing This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: needs-upstream-testing If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. Please let us know your results. Thank you for your understanding. Helpful Bug Reporting Links: https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug ** This bug is no longer a duplicate of bug 494099 subwoofer stops working after playback ends ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Low => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: jaunty kernel-sound lucid needs-upstream-testing ** Description changed: Binary package hint: pulseaudio I don't know if this is actually a PulseAudio bug or a bug in some lower-level like ALSA; it seems like it's PulseAudio only because sometimes restarting it makes it work for longer or restore sound at all (more below). I have a SB Live! 5.1 (see /proc/asound/cards just below this ¶), which works mostly okay in Jaunty but now is exceedingly unreliable in Karmic. In Jaunty, I just told PulseAudio that it had 6 channels to output and set the mixer controls on the ALSA mixer so that I had sound coming out of all the speakers in a configuration that I liked. - 0 [Live ]: EMU10K1 - SB Live! 5.1 [SB0060] - SB Live! 5.1 [SB0060] (rev.7, serial:0x80611102) at 0xdc00, irq 19 + 0 [Live ]: EMU10K1 - SB Live! 5.1 [SB0060] + SB Live! 5.1 [SB0060] (rev.7, serial:0x80611102) at 0xdc00, irq 19 I was very happy to see the ability to just select "Output Analog Surround 5.1" as an option. This is what I did in my (fresh) Karmic install (the full profile name is "Output Analog Surround 5.1 + Input Analog Stereo"). Now, this unreliability manifests in different, multiple ways. I don't know if this should be broke out into separate bugs, but if so, please feel free to do so: - * If the profile is switched while sound is playing, sound may stop playing at all until PulseAudio is restarted (I did this by running "pulseaudio -k" at the terminal; PA started right back up on its own after I did that). - * 5.1 only actually works when the profile is switched while sound is playing, until the next skip in sound (this is independent of the program sending audio; verified with Banshee and mpg321). This is easily reproduceable with the new control panel widget and mpg321: Start to play a song, switch the profile to 5.1. It sounds great. Send SIGINT (Ctrl+C) to mpg321, and start to play the same song with it again. It seems to revert back to regular stereo, after a few messages about ALSA underruns. Sometimes, you can get the ALSA underrun message _while_ mpg321 is playing, after setting to 5.1: once it hits those underruns, you're back to stereo. + * If the profile is switched while sound is playing, sound may stop playing at all until PulseAudio is restarted (I did this by running "pulseaudio -k" at the terminal; PA started right back up on its own after I did that). + * 5.1 only actually works when the profile is switched while sound is playing, until the next skip in sound (this is independent of the program sending audio; verified with Banshee and mpg321). This is easily reproduceable with the new control panel widget and mpg321: Start to play a song, switch the profile to 5.1. It sounds great. Send SIGINT (Ctrl+C) to mpg321, and start to play the same song with it again. It seems to revert back to regular stereo, after a few messages about ALSA underruns. Sometimes, you can get the ALSA underrun message _while_ mpg321 is playing, after setting to 5.1: once it hits those underruns, you're back to stereo. While it reverts back to stereo in reality, the sound preferences panel will still say that it's outputting 5.1 surround sound audio. To bring 5.1 back, one much switch to a different profile and back to 5.1 while the sound is still playing. There are no messages in the kernel ring buffer which indicate any audio issues at the driver level; the only visible diagnostic is getting this message while playing mpg321 music (and once the first one is emitted, it's back to stereo): - mbt@zest:~/Music/M$ mpg123 MIA\ -\ Paper\ Planes.mp3 + mbt@zest:~/Music/M$ mpg123 MIA\ -\ Paper\ Planes.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.59q (2002/03/23). Written and copyrights by Joe Drew. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! - Title : Paper Planes Artist: M.I.A. + Title : Paper Planes Artist: M.I.A. Album : Paper Planes - Homeland Securi Year : 2008 - Comment: XL Genre : + Comment: XL Genre : Playing MPEG stream from MIA - Paper Planes.mp3 ... MPEG 1.0 layer III, 320 kbit/s, 44100 Hz joint-stereo ALSA: underrun, at least 0ms. ALSA: underrun, at least 0ms. Every time an underrun occurs, the song skips by some small amount of time. If you see 30 or so of those messages, a good chunk (maybe 10-20 seconds?) is skipped in the song. In short, when the sound works properly, it's *really* good. After a skip, it's *really* bad. + + Architecture: amd64 + AudioDevicesInUse: + USER PID ACCESS COMMAND + /dev/snd/controlC0: mbt 4117 F.... pulseaudio + Card0.Amixer.info: + Card hw:0 'Live'/'SB Live! 5.1 [SB0060] (rev.7, serial:0x80611102) at 0xdc00, irq 19' + Mixer name : 'SigmaTel STAC9708,11' + Components : 'AC97a:83847608' + Controls : 224 + Simple ctrls : 45 + CurrentDmesg: + + DistroRelease: Ubuntu 9.10 + NonfreeKernelModules: nvidia + Package: pulseaudio 1:0.9.16~test7-14-g7ca81-0ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + ProcVersionSignature: Ubuntu 2.6.31-9.29-generic + Uname: Linux 2.6.31-9-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Tags added: maverick ** Attachment removed: "AlsaDevices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410049/+files/AlsaDevices.txt ** Attachment removed: "AplayDevices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410050/+files/AplayDevices.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410052/+files/BootDmesg.txt ** Attachment removed: "ArecordDevices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410051/+files/ArecordDevices.txt ** Attachment removed: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410053/+files/Card0.Codecs.codec.0.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410055/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410056/+files/Dependencies.txt ** Attachment removed: "Card1.Amixer.values.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410054/+files/Card1.Amixer.values.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410058/+files/ProcCpuinfo.txt ** Attachment removed: "modified.conffile..etc.pulse.daemon.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410059/+files/modified.conffile..etc.pulse.daemon.conf.txt ** Attachment removed: "PciMultimedia.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+attachment/1410057/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/406582 Title: 5.1 on SB Live! 5.1 [SB0060] is very unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/406582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
