Activity log for bug #315971

Date Who What changed Old value New value Message
2009-01-11 02:26:05 Peter Clifton bug added bug
2009-01-11 06:45:54 Daniel T Chen pulseaudio: status New Incomplete
2009-01-11 06:45:54 Daniel T Chen pulseaudio: statusexplanation Is this symptom reproducible with the latest pulseaudio package (0.9.13-2ubuntu5) in jaunty?
2009-01-12 23:41:14 Daniel T Chen title No audio HP 6730b 'Front' mixer control element should be unmuted by default on HDA platforms
2009-01-12 23:48:04 Daniel T Chen title 'Front' mixer control element should be unmuted by default on HDA platforms 'Front' and 'PCM' mixer control elements must be unmuted by default on HDA platforms
2009-01-13 21:26:58 Bryce Harrington pulseaudio: importance Undecided High
2009-01-13 21:26:58 Bryce Harrington pulseaudio: statusexplanation Is this symptom reproducible with the latest pulseaudio package (0.9.13-2ubuntu5) in jaunty? This turned out to be the root cause of a sound issue I was having. After updating to latest jaunty this morning and manually re-adding "options snd-hda-intel model=mitac" to enable my 82801H [8086:284b] audio chip (bug #210865), I found that alsa had re-muted my Front and other channels. On reboot sound acted as if it were muted, but I was quite confused that alsamixer showed only a single channel, unmuted and at full volume. (My System/Preferences/Sound applet is missing and I've no idea what happened to it, but that's a separate issue). I found by killing pulseaudio, I could unmute in alsamixer, restart pulseaudio, and everything worked again. I also tested using alsamixer -c 0 and believe that should do it too. alsamixer -c 0 is nice to learn about and something I'll definitely keep in my back pocket for future troubleshooting. However, this doesn't seem to be a very discoverable solution to this problem.
2009-01-13 21:26:58 Bryce Harrington pulseaudio: milestone jaunty-alpha-4
2009-01-13 21:55:10 Bryce Harrington description Binary package hint: pulseaudio On HP 6730b, got no sound output from any application. Turns out that the PCM channel on the hardware mixer was set to zero / muted, and none of the standard knobs on the Gnome desktop could adjust it. Fixed on my box with "alsamixer -c 0", although I guess not every new user will immediately jump on that one. This is tested on Jaunty. Binary package hint: pulseaudio [Problem] Pulseaudio does not directly expose or allow adjustment of arbitrary mixers on the underlying card. [Workaround] a. alsamixer -c 0 # where 0 is the hw id of the audio card b. alsamixer -Dhw:0 # ditto c. with the gnome panel applet, if you right-click, choose preferences, and adjust the "Master" and "PCM" channels. d. shutdown pulseaudio, run alsamixer, and restart pulseaudio `sudo alsactl store` may need to be run to make the changes persistent. [Original Report] On HP 6730b, got no sound output from any application. Turns out that the PCM channel on the hardware mixer was set to zero / muted, and none of the standard knobs on the Gnome desktop could adjust it. Fixed on my box with "alsamixer -c 0", although I guess not every new user will immediately jump on that one. This is tested on Jaunty. pulseaudio package (0.9.13-2ubuntu5) Pulse audio doesn't appear to expose or allow adjustment of arbitrary mixers on the underlying card. Is there any mechanism by which pulseaudio can reliably expect the various mixer channels it is relying on to be raised?
2009-01-13 21:56:10 Bryce Harrington pulseaudio: status Incomplete Confirmed
2009-01-13 21:56:10 Bryce Harrington pulseaudio: statusexplanation This turned out to be the root cause of a sound issue I was having. After updating to latest jaunty this morning and manually re-adding "options snd-hda-intel model=mitac" to enable my 82801H [8086:284b] audio chip (bug #210865), I found that alsa had re-muted my Front and other channels. On reboot sound acted as if it were muted, but I was quite confused that alsamixer showed only a single channel, unmuted and at full volume. (My System/Preferences/Sound applet is missing and I've no idea what happened to it, but that's a separate issue). I found by killing pulseaudio, I could unmute in alsamixer, restart pulseaudio, and everything worked again. I also tested using alsamixer -c 0 and believe that should do it too. alsamixer -c 0 is nice to learn about and something I'll definitely keep in my back pocket for future troubleshooting. However, this doesn't seem to be a very discoverable solution to this problem.
2009-04-23 08:30:59 Jeffonline attachment added Select Mixer.png http://launchpadlibrarian.net/25873387/Select%20Mixer.png
2009-04-28 07:45:47 Nicolò Chieffo removed subscriber Nicolò Chieffo
2009-04-30 13:26:06 Matteo Gazzoni removed subscriber Matteo Gazzoni
2009-06-08 05:44:06 Launchpad Janitor branch linked lp:~crimsun/pulseaudio/ubuntu
2009-06-08 05:48:27 Daniel T Chen pulseaudio (Ubuntu): status Confirmed Fix Committed
2009-06-08 05:48:27 Daniel T Chen pulseaudio (Ubuntu): milestone jaunty-alpha-4 karmic-alpha-2
2009-06-08 05:48:27 Daniel T Chen pulseaudio (Ubuntu): assignee Daniel T Chen (crimsun)
2009-06-09 01:00:07 Launchpad Janitor pulseaudio (Ubuntu): status Fix Committed Fix Released
2010-01-13 06:02:17 Launchpad Janitor branch linked lp:ubuntu/pulseaudio