Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Number pad oddity

5 views
Skip to first unread message

rmg

unread,
Jul 14, 2011, 9:49:57 AM7/14/11
to
Somehow the number pad in this login no longer works - in xterms or (for
instance) emacs - Numlock LED on or not. It's fine in other logins.

Any clues about where to look? It must be something in $(HOME) surely but I
can't see anything likely.

--
Dick Georgeson
Whenever you find that you are on the side of the majority, it is time
to reform. -- Mark Twain

Geoff Clements

unread,
Jul 14, 2011, 2:24:11 PM7/14/11
to
rmg wrote:

> Somehow the number pad in this login no longer works - in xterms or (for
> instance) emacs - Numlock LED on or not. It's fine in other logins.
>
> Any clues about where to look? It must be something in $(HOME) surely but
> I can't see anything likely.
>

$ grep -R xmodmap ~

--
Geoff

rmg

unread,
Jul 14, 2011, 6:51:23 PM7/14/11
to

Nuttin', nor for the other logins where the number pad works.

Nix

unread,
Jul 15, 2011, 7:25:14 AM7/15/11
to
On 14 Jul 2011, Geoff Clements stated:

xkbcomp :0 - | less

might throw some light, or at least confusion.

--
NULL && (void)

Geoff Clements

unread,
Jul 15, 2011, 1:29:12 PM7/15/11
to
Nix wrote:

Try logging in at the console and see if the problem persists. If not then
it's either X or your desktop. If the above sheds no light then I'd look at
your desktop settings. Under KDE there are quite a few options for the
numpad and also it's just possible that the wrong type of keyboard has been
selected.

--
Geoff

rmg

unread,
Jul 16, 2011, 12:30:23 PM7/16/11
to
Geoff Clements wrote:
> Nix wrote:
>
>> On 14 Jul 2011, Geoff Clements stated:
>>
>>> rmg wrote:
>>>
>>>> Somehow the number pad in this login no longer works - in xterms or (for
>>>> instance) emacs - Numlock LED on or not. It's fine in other logins.
>>>>
>>>> Any clues about where to look? It must be something in $(HOME) surely
>>>> but I can't see anything likely.
>>>>
>>> $ grep -R xmodmap ~
>> xkbcomp :0 - | less
>>
>> might throw some light, or at least confusion.
>>

Not wanting to dump the whole on the ng, the following snippets may be relevant:

<KP7> = 79;
<KP8> = 80;
<KP9> = 81;
<KPSU> = 82;
<KP4> = 83;
<KP5> = 84;
<KP6> = 85;
<KPAD> = 86;
<KP1> = 87;
<KP2> = 88;
<KP3> = 89;
<KP0> = 90;

and

xkb_types "complete" {
virtual_modifiers NumLock,Alt,LevelThree,LAlt,RAlt,RControl,LControl,ScrollL
ock,LevelFive,AltGr,Meta,Super,Hyper;

<...>
type "KEYPAD" {
modifiers= Shift+NumLock;
map[Shift]= Level2;
map[NumLock]= Level2;
level_name[Level1]= "Base";
level_name[Level2]= "Number";
};

I'm afraid it's not very meaningful to me.

>
> Try logging in at the console and see if the problem persists. If not then
> it's either X or your desktop. If the above sheds no light then I'd look at
> your desktop settings. Under KDE there are quite a few options for the
> numpad and also it's just possible that the wrong type of keyboard has been
> selected.
>

<CTRL><ALT><f1>
login

number pad works as intended.

I'm using gnome, Keyboard preferences include Numeric keypad layout selection
(currently 'Default') and the keyboard type is right. Doesn't seem to be much
else to play with.

But all this stuff gives the same answers when logged in as a different user,
only difference is the keypad works, just as it used to for this user; it's
possible this problem is associated with a gtk prog running under the debugger
going wrong but I'm far from certain.

0 new messages