[Dell Inspiron 7537] Wireless key does not work in 14.04.1

[Po-Hsu Lin]

CID: 201306-13867 Dell Inspiron 7537

This bug should be fixed in Trusty, see bug 1339456,
however, the wireless key still not working on this system with 3.13.0-39.

Note that for another system reported in that bug, 201306-13869 Dell Inspiron 7737, wireless key could work after applying update.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1591 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 1591 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Mon Nov 24 04:52:46 2014
HibernationDevice: RESUME=UUID=bfa7a3e7-f4e1-4d1b-b5ca-a349ed36f827
InstallationDate: Installed on 2014-11-24 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 7537
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=340be28b-7b42-48f7-a311-257ee21c5c2c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/28/2014:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Inspiron 7537
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Po-Hsu Lin (cypressyew)]

Look back into that bug report (bug 1339456) I think it's just because the fix haven't been pushed to -released yet.
Therefore I will mark this bug as duplicated.
Thanks