I've learned more about what I think is happening here.  I've upgraded
three other computers to Hardy w/o this behavior, so I don't think it's
an upgrade problem.

Adding my username to the above mentioned groups solved the audio problem until 
the machine was rebooted, whereupon the same problem reappeared.  I tried 
launching pulseaudio from the command line to see what was happening, and kept 
getting:
E: alsa-util.c: Error opening PCM device hw:0: Device or resource busy
E: module.c: Failed to load  module "module-alsa-sink" (argument: "device_id=0 
sink_name=alsa_output.pci_8086_24d5_sound_card_0_alsa_playback_0"): 
initialization failed.

Humm... More investigation on what would be occupying the hardware and
preventing pulseaudio from completely launching led me to the
Gizmoproject soft phone.  Output of lsof | grep /dev/snd indicated Gizmo
was occupying the hardware.  Exited Gizmo, and pulseaudio launched
properly and all is happy.

Apparently Gizmo has an incompatibility with PulseAudio
(http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=330).

SO,  I'm guessing that this incompatibility kept pulse from launching
and completing the installation which included the group assignments
mentioned above.

Also, I checked to see if order of launching makes a difference - gizmo
then pulseaudio vs. pulseaudio then gizmo.  In both cases gizmo grabbed
the hardware and pulse rolled over dead without a fight causing system
audio to go down.  Gizmo continued to work fine in either case.

I'll see what else I can learn about this.

Thanks,
Mike

-- 
In upgrade to 8.04, Pulse Audio group permissions don't get set
https://bugs.launchpad.net/bugs/224367
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to