volume/mute keys no longer work

[Max Waterman]

After upgrading from 15.10 to 16.04, my volume keys no longer work. In 15.10, pressing the volume up/down resulted in the volume going up/down as indicated in the applet in the top menu, accompanied by a blip. Since upgrading, there is no response to the keys.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: davidmaxwaterman 2348 F.... pulseaudio
 /dev/snd/controlC0: davidmaxwaterman 2348 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 17:27:24 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=f6a6d0a5-8059-4f25-9b03-f560ceb68f6d
InstallationDate: Installed on 2015-05-20 (342 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20CM001QUK
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
dmi.bios.date: 04/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET33W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CM001QUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CM001QUK
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Max Waterman (b-ubuntuone)]

This seems to be caused by :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575260

worked around by making a symlink :

sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0 /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

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'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

[Max Waterman (b-ubuntuone)]

I am currently running with that kernel :

[~]$ uname -ar
Linux mwaterm1-x250 4.6.0-040600rc6-generic #201605012031 SMP Mon May 2 00:33:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[~]$

The problem now doesn't occur, but I'm am uncertain if it is because of the kernel (and any fix in it) or the symlink I made as per comment #3. I could quite believe that the symlink workaround could fix a variety of problems, but there were several issues in the upgrade and the first thing I was told to do was to upgrade the kernel.

I'm happy to defer to your own judgement on that. If you think this issue is fixed (I mean the actual problem, not just for my case), then I have no problem with you closing this.

[Launchpad Janitor (janitor)]

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