← Back to team overview

kernel-packages team mailing list archive

  1. kernel-packages team
  2. Mailing list archive
  3. Message #06671

[Bug 596627] Re: Turning on NumLock on USB keyboard disables MacBook's (and possibly others') built-in keyboard

  Thread Previous • Date Previous • • Thread Next 
jiteo, 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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

** Description changed:

- This is the same bug as 374012 - I was asked to open a new one since
- 374012 was tagged as Expired.
- 
  Most of the keys on my MacBook 4,1's keyboard will stop responding...
  sometimes. I've tried to figure out a consistent way to reproduce the
  bug, but I've been unable to do so, hence my use of "sometimes". If I
  open xev, I see that no event is being generated by most keypresses.
  This only happens when logged in to a GNOME session - the keyboard works
  in the loging screen, both before I login, and after I logout.
  
- I can confirm that the workaround described in 374012 does work. If I
- empty out the contents of
+ WORKAROUND: If I empty out the contents of
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>,
- logout and login, the keyboard starts working again. Note that just
- logging out and back in does not fix it. Also note that the contents of
+ logout and login, the keyboard starts working again.
+ 
+ Note that just logging out and back in does not fix it. Also note that
+ the contents of
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>
  do not have to be absent for the keyboard to work. I am currently typing
  on said keyboard and
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>
  contains its usual folder "0" and file "%gconf.xml". Also also note that
  a USB keyboard will work fine throughout all of this.
  
  This may have something to do with my external monitor setup. This is a
  work laptop, and at work I have a second screen. At home I do not. I
  *believe* this only happens when I switch from one setup to the other -
  ie powering on my laptop at work with the second screen plugged in after
  it had been powered on at home without a second screen, and powering it
  on at home without a second screen after it had been powered on at work
  with one.
  
- I really don't know what package this bug would apply to. I'm running a
- new install of 10.04 LTS. It's a white plastic (not unibody) MacBook
- 4,1, with a Canadian French keyboard, for what that's worth.
- 
- Cheers!
- --- 
+ ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
-  USER        PID ACCESS COMMAND
-  /dev/snd/controlC0:  artom      1424 F.... pulseaudio
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC0:  artom      1424 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
-  Card hw:0 'Intel'/'HDA Intel at 0xd0700000 irq 20'
-    Mixer name	: 'Realtek ALC889A'
-    Components	: 'HDA:10ec0885,106b3600,00100103'
-    Controls      : 34
-    Simple ctrls  : 21
+  Card hw:0 'Intel'/'HDA Intel at 0xd0700000 irq 20'
+    Mixer name	: 'Realtek ALC889A'
+    Components	: 'HDA:10ec0885,106b3600,00100103'
+    Controls      : 34
+    Simple ctrls  : 21
  DistroRelease: Ubuntu 10.04
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=af011cd3-ab89-47e9-a335-c5694df4b7e6
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Apple Inc. MacBook4,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=bf299143-f64b-478d-84f8-4f9267ae8762 ro quiet splash
  ProcEnviron:
-  LANG=en_CA.utf8
-  SHELL=/bin/bash
+  LANG=en_CA.utf8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2
  Regression: No
  RelatedPackageVersions: linux-firmware 1.34
  Reproducible: No
  RfKill:
-  0: hci0: Bluetooth
-  	Soft blocked: no
-  	Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  Tags: lucid  needs-upstream-testing
  Uname: Linux 2.6.32-22-generic-pae i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB41.88Z.00C1.B00.0802091535
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F22788A9
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788A9
  dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
  dmi.product.name: MacBook4,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

** Tags added: lucid needs-upstream-testing

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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/596627

Title:
  Turning on NumLock on USB keyboard disables MacBook's (and possibly
  others') built-in keyboard

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Most of the keys on my MacBook 4,1's keyboard will stop responding...
  sometimes. I've tried to figure out a consistent way to reproduce the
  bug, but I've been unable to do so, hence my use of "sometimes". If I
  open xev, I see that no event is being generated by most keypresses.
  This only happens when logged in to a GNOME session - the keyboard
  works in the loging screen, both before I login, and after I logout.

  WORKAROUND: If I empty out the contents of
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>,
  logout and login, the keyboard starts working again.

  Note that just logging out and back in does not fix it. Also note that
  the contents of
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>
  do not have to be absent for the keyboard to work. I am currently
  typing on said keyboard and
  /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<hostname>
  contains its usual folder "0" and file "%gconf.xml". Also also note
  that a USB keyboard will work fine throughout all of this.

  This may have something to do with my external monitor setup. This is
  a work laptop, and at work I have a second screen. At home I do not. I
  *believe* this only happens when I switch from one setup to the other
  - ie powering on my laptop at work with the second screen plugged in
  after it had been powered on at home without a second screen, and
  powering it on at home without a second screen after it had been
  powered on at work with one.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  artom      1424 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd0700000 irq 20'
     Mixer name	: 'Realtek ALC889A'
     Components	: 'HDA:10ec0885,106b3600,00100103'
     Controls      : 34
     Simple ctrls  : 21
  DistroRelease: Ubuntu 10.04
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=af011cd3-ab89-47e9-a335-c5694df4b7e6
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Apple Inc. MacBook4,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=bf299143-f64b-478d-84f8-4f9267ae8762 ro quiet splash
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2
  Regression: No
  RelatedPackageVersions: linux-firmware 1.34
  Reproducible: No
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags: lucid  needs-upstream-testing
  Uname: Linux 2.6.32-22-generic-pae i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB41.88Z.00C1.B00.0802091535
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F22788A9
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22788A9
  dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
  dmi.product.name: MacBook4,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596627/+subscriptions
  Thread Previous • Date Previous • • Thread Next