Plugging in headphones no longer disables built in speakers.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Hello.
When I plug headphones into the headphone jack, the builtin laptop speakers are not disabled. Sound plays through the laptop speakers as well as any speakers attached to the headphone port.
The intended operation is for the builtin laptop speakers to be disabled when headphones are plugged in.
This worked in 10.04 for sure, and I believe it did for 10.10 at release as well.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: wyatt 7554 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xf3f38000 irq 23'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,
Controls : 10
Simple ctrls : 6
Date: Wed Jan 5 18:28:32 2011
HibernationDevice: RESUME=
HotplugNewDevices:
HotplugNewMounts:
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: ASUSTeK Computer INC. T91MT
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
dmi.bios.date: 10/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.
dmi.board.name: T91MT
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: T91MT
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
tags: | added: hda-jack-sense |
tags: |
added: regression-update removed: regression-potential |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
posi, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command in a supported release from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux <replace- with-bug- number>
Also, if you could 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/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.
Helpful Bug Reporting Links: /help.ubuntu. com/community/ ReportingBugs# Bug_Reporting_ Etiquette /help.ubuntu. com/community/ ReportingBugs# A3._Make_ sure_the_ bug_hasn. 27t_already_ been_reported /help.ubuntu. com/community/ ReportingBugs# Adding_ Apport_ Debug_Informati on_to_an_ Existing_ Launchpad_ Bug /help.ubuntu. com/community/ ReportingBugs# Adding_ Additional_ Attachments_ to_an_Existing_ Launchpad_ Bug
https:/
https:/
https:/
https:/