[Thinkpad T410s] Mute indicator gets out of sync

So long as the mute button LED is lit, the speakers cannot output any sound. It is possible to mute with the hardware button, unmute in software and be able to use headphones without the speakers being used if the headphones are accidentally unplugged. The speaker mute button functions before any operating system is booted. It would be a good idea to compare the functionality in Windows if someone has a chance, including with the connexant audio utility.

I am also experiencing this behavior on my Thinkpad T410 running Kubuntu 11.04. The hardware and software indicators can get reversed either by toggling the mute on the panel icon or if the hardware mute is enabled on boot or resume from suspend. Pressing the mute button switches both indicators, keeping them reversed. Changing the volume via the hardware buttons will reset the hardware mute indicator and get them back in sync.

I rebooted into the stock Windows 7 install to check its behavior. It functions in a much more logical way: the software and hardware mute indicators are kept in sync at all times.

While it is true that it is desirable at times to disable the speakers while leaving the headphones operable, IMHO the current behavior is not the correct way to expose this functionality to the user.

This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:

apport-collect 788540

and then change the status of the bug back to 'New'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: harald 1991 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:14f15069,17aa214c,00100302 HDA:14f12c06,17aa2122,00100000 HDA:80862804,17aa21b5,00100000'
   Controls : 12
   Simple ctrls : 6
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6IHT38WW-1.13'
   Mixer name : 'ThinkPad EC 6IHT38WW-1.13'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [off]
DistroRelease: Ubuntu 11.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0b363106-7e7f-430a-a831-d3a953f97f1f
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 2537UQF
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=f5d8dcd6-ad7f-45f8-9f35-998d87a1a0b8 ro pcie_aspm=force
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-10-generic N/A
 linux-backports-modules-2.6.38-10-generic N/A
 linux-firmware 1.52
Tags: natty
Uname: Linux 2.6.38-10-generic x86_64
UpgradeStatus: Upgraded to natty on 2011-05-02 (81 days ago)
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
WifiSyslog:

dmi.bios.date: 10/25/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET74WW (1.34 )
dmi.board.name: 2537UQF
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537UQF:pvrThinkPadT410:rvnLENOVO:rn2537UQF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2537UQF
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 788540

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

As nobody added the requested logs I ran:

apport-collect 788540

Why can't I change the status to new? Does the bug reporter have to post the logs? I have exactly the same behavior, I only have slightly different hardware (Thinkpad T410).

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Same problem on Thinkpad W530 with 12.04 LTS

Daniël van Eeden, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

I can reproduce it easily with Ubuntu 13.04 (raring) with kernel 3.8.0-29-generic.

To make clarify what happens:
There are 4 ways to get the current speaker mute status:
1. The mute led on the physical mute button.
2. The /proc/acpi/ibm/volume file
3. The icon (I'm currently using gnome-shell)
4. The PulseAudio Volume Control

To mute/unmute there are 3 methods:
a. The hardware mute button for the speaker.
b. The slider for the volume icon in gnome-shell
c. PulseAudio Volume Control

If I use method a then all four statuses remain in sync. If I use method b or c to mute then 1 and 2 don't change.

This bug is not about the issue with the microphone mute button not working, that's Bug #408903

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

It's also reproducable on 13.10 (saucy) with kernel 3.11.0-2-generic

I've updated the BIOS to "6UET70WW (1.50 )" and I can still easily reproduce it with 13.04 (3.8.0-29-generic).

I've tested it with 3.9.0-030900rc8-generic and it is reproducable
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc8-raring/linux-image-3.9.0-030900rc8-generic_3.9.0-030900rc8.201304211835_amd64.deb

I've removed the bios-outdated-1.49 tag as my bios was upgraded from 1.47 to 1.50 (the most current)

Hello Christopher,

As noted before I upgraded from 1.47 (not 1.49) to 1.50 (latest bios update)

6UET70WW (1.50 )
10/11/2012

Daniël van Eeden, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/ ?

This is a known issue with Lenovo Thinkpads. The workaround is to use a shell script and a recompiled kernel module. You can find the steps here:

http://askubuntu.com/questions/125367/enabling-mic-mute-button-and-light-on-lenovo-thinkpads

It would be nice if this could work out of the box, though.

@Dariel: that's about the microphone mute button (Bug #408903), this bug is about the volume mute button.

apport information

apport information

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

As testing each new release takes quite some time I will only do that if there is some indication about a fix.

I'll leave it on Incomplete.

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

Any news here? This bug still exists in 14.04.2.