Pulseaudio Does Not Start Correctly When Randomsound Package is Installed

[Brian Knoll]

Binary package hint: pulseaudio

On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system and it would come back up and consistently have audio. However, once I configured a bridged network on my eth0 device in /etc/network/interfaces, the system would no longer have audio after a reboot.

The bridge is working fine. My /etc/network/interfaces is configured as follows:

--------------------------------------
auto lo
iface lo inet loopback

# The bridge network interface
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

# The primary network interface
auto eth0
iface eth0 inet manual
------------------------------------------

I can usually get my sound back by running "alsa force-reload" from the desktop. Running this from rc.local during system boot does not work, however.

When this happens, my sound hardware is not detected. No sound hardware shows up in "Sound Preferences" under Hardware, and in "Output" all I have is a "Dummy Output". But of course, without the bridge, the hardware is detected and everything works.

Bridging is an important feature, and I think it's rather important to get this fixed in the LTS release. Please let me know how I can help test or fix things.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bknoll 3381 F.... pulseaudio
                      root 3394 F.... arecord
 /dev/snd/pcmC0D0c: root 3394 F...m arecord
 /dev/snd/timer: root 3394 f.... arecord
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
   Mixer name : 'Silicon Image SiI1392 HDMI'
   Components : 'HDA:10ec0883,1043829f,00100002 HDA:10951392,ffffffff,00100000'
   Controls : 40
   Simple ctrls : 22
Date: Sat May 8 12:05:36 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Title: Pulseaudio is not running
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E-VM HDMI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E-VM HDMI
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.32-02063211-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom crontab dialout floppy games kvm lp lpadmin plugdev root sambashare staff users video

---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-020634rc6-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom crontab dialout floppy games kvm lp lpadmin plugdev root sambashare staff users video

[Daniel T Chen (crimsun)]

Please see dmesg and reassign (change affected package) to linux.

On May 8, 2010 12:25 PM, "Brian Knoll" <email address hidden> wrote:

** Attachment added: "AlsaDevices.txt"
  http://launchpadlibrarian.net/48069135/AlsaDevices.txt

** Attachment added: "AplayDevices.txt"
  http://launchpadlibrarian.net/48069136/AplayDevices.txt

** Attachment added: "ArecordDevices.txt"
  http://launchpadlibrarian.net/48069137/ArecordDevices.txt

** Attachment added: "BootDmesg.txt"
  http://launchpadlibrarian.net/48069138/BootDmesg.txt

** Attachment added: "Card0.Amixer.values.txt"
  http://launchpadlibrarian.net/48069139/Card0.Amixer.values.txt

** Attachment added: "Card0.Codecs.codec.0.txt"
  http://launchpadlibrarian.net/48069140/Card0.Codecs.codec.0.txt

** Attachment added: "Card0.Codecs.codec.1.txt"
  http://launchpadlibrarian.net/48069141/Card0.Codecs.codec.1.txt

** Attachment added: "CurrentDmesg.txt"
  http://launchpadlibrarian.net/48069142/CurrentDmesg.txt

** Attachment added: "Dependencies.txt"
  http://launchpadlibrarian.net/48069143/Dependencies.txt

** Attachment added: "PciMultimedia.txt"
  http://launchpadlibrarian.net/48069144/PciMultimedia.txt

** Attachment added: "ProcCpuinfo.txt"
  http://launchpadlibrarian.net/48069145/ProcCpuinfo.txt

--
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bu...

[Brian Knoll (brianknoll)]

Changing affected package at the request of Daniel T. Chen

[Daniel T Chen (crimsun)]

The source package name is linux, not linux-meta.

On May 8, 2010 4:40 PM, "Brian Knoll" <email address hidden> wrote:

Changing affected package at the request of Daniel T. Chen

** Package changed: pulseaudio (Ubuntu) => linux-meta (Ubuntu)

--
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bu...
Status in “linux-meta” package in Ubuntu: New

Bug description:
Binary package hint: pulseaudio

On an install of Ubuntu Lucid 10.04 LTS AMD64, I ...

[Brian Knoll (brianknoll)]

When I tried to change the package name to "linux", Launchpad stopped me and said that there were too many matches, so it wouldn't allow it. That's when I changed the package name to "linux-2.6.32-22-server", and then Launchpad automatically reassigned it to "linux-meta".

I'm happy to change it to whatever it needs to be, but it looks like "linux" isn't going to be accepted by the system.

[Jeremy Foshee (jeremyfoshee)]

Hi Brian,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Brian Knoll (brianknoll)]

Thanks for helping with this. I have verified that the problem does indeed occur with the upstream 2.6.32-02063211-generic #02063211 kernel, and I have removed the "needs-upstream-testing" tag from this ticket, as requested.

[Brian Knoll (brianknoll)]

I changed the status to "confirmed" after testing against the upstream kernel, because "invalid" didn't seem appropriate any more. If that wasn't correct, please let me know which status you would prefer, and/or change it to another status. Thanks!

[Brian Knoll (brianknoll)]

I've collected additional data from the failed state, using the upstream kernel, and attached it to this case.

[Brian Knoll (brianknoll)]

I have now also tested this issue against the 2.6.34-020634rc6-generic #020634rc6 upstream kernel, and I confirm that the problem also exists when using that kernel.

[David Henningsson (diwic)]

Hi Brian, I tried replacing /etc/network/interfaces with your version and rebooted, and my sound continued to work properly, so I can't confirm the bug.

Perhaps a pulseaudio log would help to analyze this issue? See https://wiki.ubuntu.com/PulseAudio/Log

[Brian Knoll (brianknoll)]

I think I figured out what the problem was.  The problem was that I had the "randomsound" package installed.  When this package is installed, there is a race condition and the sound components don't initialize properly.  I'm not 100% certain whether the bridged network is actually needed in order to trigger the race condition, but I know that on all of my systems where I install "randomsound", I experience this problem.

--- On Thu, 7/29/10, David Henningsson <email address hidden> wrote:

From: David Henningsson <email address hidden>
Subject: [Bug 577509] Re: Pulseaudio Does Not Start Correctly When Using Bridged Networking
To: <email address hidden>
Date: Thursday, July 29, 2010, 2:17 PM

Hi Brian, I tried replacing /etc/network/interfaces with your version
and rebooted, and my sound continued to work properly, so I can't
confirm the bug.

Perhaps a pulseaudio log would help to analyze this issue? See
https://wiki.ubuntu.com/PulseAudio/Log

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

--
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
You received this bug notification because you are a direct subscriber
of the bug.

Status in “linux” package in Ubuntu: Incomplete

Bug description:
Binary package hint: pulseaudio

On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system and it would come back up and consistently have audio.  However, once I configured a bridged network on my eth0 device in /etc/network/interfaces, the system would no longer have audio after a reboot.

The bridge is working fine.  My /etc/network/interfaces is configured as follows:

--------------------------------------
auto lo
iface lo inet loopback

# The bridge network interface
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

# The primary network interface
auto eth0
iface eth0 inet manual
------------------------------------------

I can usually get my sound back by running "alsa force-reload" from the desktop.  Running this from rc.local during system boot does not work, however.

When this happens, my sound hardware is not detected.  No sound hardware shows up in "Sound Preferences" under Hardware, and in "Output" all I have is a "Dummy Output".  But of course, without the bridge, the hardware is detected and everything works.

Bridging is an important feature, and I think it's rather important to get this fixed in the LTS release.  Please let me know how I can help test or fix things.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  bknoll     3381 F.... pulseaudio
                      root       3394 F.... arecord
 /dev/snd/pcmC0D0c:   root       3394 F...m arecord
 /dev/snd/timer:      root       3394 f.... arecord
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Inte...

[Brian Knoll (brianknoll)]

I updated the bug title to correctly reflect the current idea of what actually triggers this bug.

[Brian Knoll (brianknoll)]

I reset status back to "New" since the nature of the bug has changed and there is new information. "Incomplete" didn't seem appropriate any more.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 577509

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]