No sound under Karmic after upgrade from 9.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pulseaudio
I have tried a number of other hints in bug reports (e.g. sudo /sbin/alsa force-unload && sudo modprobe snd-hda-intel model=ref && speaker-test -c2 -Dplug:front) and once (and only once) have a managed to get some pink noise from the speakers. Unable to replicate.
I also note that I am no longer in the audio group. The only real user in that group (via /etc/group) is alphabetically the first real (non-system) user. Aside: this also seems to be the case for the video group, and some others.
But even switching to that user that is in the group, I cannot get audio.
Prior to running speaker-test, I have disabled autospawn for pulseaudio, and ensured that the daemon is not running. No success. I have unmuted and unzeroed everything in alsamixer.
I see the following significant results from syslog:
Oct 4 23:46:05 baryon pulseaudio[6279]: reserve-wrap.c: Failed to acquire reservation lock on device 'Audio0': Input/output error
And, since disabling autospawn:
Oct 5 00:05:05 baryon pulseaudio[2482]: reserve-wrap.c: Unable to contact D-Bus session bus: org.freedesktop
Oct 5 00:05:06 baryon pulseaudio[2482]: reserve-wrap.c: Unable to contact D-Bus session bus: org.freedesktop
Oct 5 00:05:06 baryon pulseaudio[2482]: main.c: Unable to contact D-Bus: org.freedesktop
ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: tony 2843 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2500000 irq 16'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10951392,
Controls : 44
Simple ctrls : 23
Date: Mon Oct 5 00:10:55 2009
DistroRelease: Ubuntu 9.10
Package: pulseaudio 1:0.9.18-0ubuntu3
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: pulseaudio
Uname: Linux 2.6.31-11-generic x86_64
And now it appears to be working. Perhaps I wasn't as rigorous in my unmuting of muted settings as I had hoped.
Please invalidate; I will re-raise bug if something resurfaces