[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#460246: marked as done (xkb-data: Cannot use numlock if placed on shifted key; invokes Pointer_EnableKeys)

Your message dated Sat, 21 Feb 2009 15:36:02 +0100
with message-id <20090221143602.GA10104@loulous.org>
and subject line Re: Bug#464041: xkb-data: Numlock does not work on many ThinkPad models
has caused the Debian Bug report #464041,
regarding xkb-data: Cannot use numlock if placed on shifted key; invokes Pointer_EnableKeys
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
464041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464041
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xkb-data
Version: 1.0~cvs.20070916-1
Severity: normal

Some keyboards, such as those on many IBM ThinkPads, have the num lock
key on the shifted scroll lock key.  (Why they didn't do that the
other way around I wish I knew.)  As a result, when pressing num lock,
it always gets interpreted with the shift modifier, resulting in
Pointer_EnableKeys instead.

I can work around this with xmodmap in my ~/.xsession, but I'd really
like it to just work.

- Josh Triplett

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Mon, Feb 04, 2008 at 12:53:16PM -0800, Josh Triplett wrote:
> Package: xkb-data
> Version: 1.1~cvs.20080104.1-1
> Severity: normal
> 
> I have a ThinkPad T42.  This and many other models of ThinkPad have
> the NumLk key on Shift+ScrLk.  (Why they didn't do that the other way
> around I don't know.)  On a Linux console, pressing Shift+ScrLk
> toggles numlock.  However, in X, pressing Shift+NumLk does not toggle
> numlock; instead, it starts a mode in which the numeric keypad keys
> control the mouse.  Note that this occurs even in a bare X session
> with only xterm running.
> 
> In order to make numlock work, I run this:
> xmodmap -e "keycode 77 = Num_Lock"
> Doing so makes numlock work as expected.
> 
> According to
> <http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work#NumLock>,
> this issue applies to numerous ThinkPad models, including at least
> "the ThinkPad 600, T20, T21, T22, T30, X20, X21, X31, X40, T42p, T43,
> R51, R52".

This has been discussed in the upstream bug at
  https://bugs.freedesktop.org/show_bug.cgi?id=14061
and it looks like it is not going to be fixed by changing
xkb-data.

I am closing this bug.

Brice

--- End Message ---
Reply to: