kernel-packages team mailing list archive

[matteo sisti sette <1284342@xxxxxxxxxxxxxxxxxx>]

Sorry, no, it would not be possible for me to test the mainline kernel.

If it is for you, however, it should be pretty straight-forward to check
whether the issue is present or not.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1284342

Title:
  [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB
  keyboard screwed up

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 13.04 to 13.10, issue #1250186 with the
  Caps Lock LED is fixed, and now NumLock, which used to work (almost)
  correctly, is srewed up, suffering from exactly the same issue as
  CapsLock used to.

  Steps to reproduce:
  - plug an external USB keyboard
  - turn on NumLock on that keyboard
  => the keyboard's NumLock LED turns on, and the numeric keys start working as numbers, as expected
  - now unplug the keyboard
  - replug the keyboard

  => Expected: the LED status must be consistent with the actual
  behavior. And it used to be!! It used to work in the best possible
  way: numlock status USED TO BE REMEMBERED, and the LED status was
  updated when replugging the keyboard, so after unplug/replug the
  behavior was as before and the displayed status was consistent with
  it.

  => Observed: the actual NumLock status is remembered, meaning the
  numeric keys keep working as number keys, as if num lock was ON, which
  is how it was prior to unplug/replug. But the LED is now off, so it is
  inconsistent with reality.

  
  The fact that the upgrade from 13.04 to 13.10 has fixed #1250186 and has screwed up NumLock behavior which was OK (on the same computer and same external keyboard), demonstrates that both are 100% software issues, i.e. Ubuntu issues, not  hardware ones. And that correct behavior can be achieved.

  
  The only thing that was already wrong with NumLock, and remains wrong after the upgrade, is that the external keyboard's LED status is not updated when the NumLock status is changed from the laptop's builtin keyboard's NumLock key, while the behavior is always the same for both keyboards (leds behave as if keyboard were independent, but they are not). However, this provides a workaround for the bug, so it must NOT be changed before the bug is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-17-generic 3.11.0-17.31
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  teo        2186 F.... pulseaudio
  Date: Mon Feb 24 22:18:44 2014
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-17-generic N/A
   linux-backports-modules-3.11.0-17-generic  N/A
   linux-firmware                             1.116.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342/+subscriptions