No separation between internal speaker and line-out after Quantal upgrade

Bug #1068336 reported by Shea Lovan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I upgraded from 12.04.1 to 12.10 this morning. Prior to the upgrade, audio worked perfectly. After the reboot, audio playback is coming through both the internal speaker and (at a much lower volume) the speakers attached to the line-out plug.

Looking at the sound control, it isn't clear that ALSA is differentiating between any of the playback devices; the only device listed is "Speakers built-in audio".

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: alsa-base 1.0.25+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: xxxx 2551 F.... pulseaudio
 /dev/snd/controlC0: xxxx 2551 F.... pulseaudio
Date: Thu Oct 18 14:09:16 2012
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to quantal on 2012-10-18 (0 days ago)
dmi.bios.date: 05/03/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K51 v01.02
dmi.board.asset.tag: xxxxx
dmi.board.name: 1790
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: xxxxx
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK51v01.02:bd05/03/2012:svnHewlett-Packard:pnHPZ220CMTWorkstation:pvr:rvnHewlett-Packard:rn1790:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z220 CMT Workstation
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Shea Lovan (shea-lovan) wrote :
Shea Lovan (shea-lovan)
description: updated
Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1068336] Re: No separation between internal speaker and line-out after Quantal upgrade

According to the information provided in your report, the bug reporter was unable to get some information about your audio hardware, as seen by PulseAudio. Do you by any chance have pulseaudio to run as a system service, or have you made any other custom pulseaudio configuration?

Revision history for this message
Raymond (superquad-vortex2) wrote :

you have to enable auto mute

Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Speaker Only' 'Line Out+Speaker'
  Item0: 'Disabled'

Revision history for this message
Shea Lovan (shea-lovan) wrote :

Luke-

I haven't made any changes to the default audio configuration. Pulse audio seems to be running as well.

   $ ps -ef | grep pulse
   lovan 2551 1 1 Oct18 ? 00:15:40 /usr/bin/pulseaudio --start --log-target=syslog
   lovan 2584 2551 0 Oct18 ? 00:00:00 /usr/lib/pulseaudio/pulse/gconf-helper
   pulse 3148 1 0 Oct18 ? 00:00:00 /usr/bin/pulseaudio --system --daemonize --high-priority --log-target=syslog --disallow-
   exit --disallow-module-loading=1

Revision history for this message
Shea Lovan (shea-lovan) wrote :

Raymond-

Poking auto-mute solved the immediate problem. Thanks!

So I guess the bug is actually, "How did this get set incorrectly during the upgrade process?"

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.