Bug 714845 - Numeric pad doesn't work in most applications
Summary: Numeric pad doesn't work in most applications
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-keyboard
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:conf_input]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 04:29 UTC by Andrig Miller
Modified: 2018-04-11 14:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-29 04:38:13 UTC
Type: ---


Attachments (Terms of Use)
Xorg log file (42.16 KB, text/plain)
2011-06-21 19:12 UTC, Andrig Miller
no flags Details
xkbcomp command output (54.72 KB, text/plain)
2011-06-21 19:13 UTC, Andrig Miller
no flags Details
evtest output (12.13 KB, text/plain)
2011-06-21 19:28 UTC, Andrig Miller
no flags Details

Description Andrig Miller 2011-06-21 04:29:39 UTC
Description of problem:

I have an HP Envy 17", and the keyboard has a full numeric key pad on the right.  It worked fine up until sometime during the F14 lifecycle.  I am now on F15, and it is still broken.

It only works in the calculator application, and not all keys work there.  In all other applications, the numeric key pad doesn't work at all.

Version-Release number of selected component (if applicable):

xorg-x11-drv-keyboard-1.5.99.901-2.fc15.x86_64

How reproducible:

All the time.

Steps to Reproduce:
1. Type any number on the numeric key pad, and it doesn't work at all. 
2.
3.
  
Actual results:

I get either a error sound (like in a password dialog), or simply nothing happens, or sometimes I get odd results, like when I hit the 2 on the numeric key pad while typing this, the cursor went to the next line.

Expected results:

Should type the numbers 0-9, as well as /, *, - + and ., as well as the enter key.

Additional info:

Comment 1 Matěj Cepl 2011-06-21 12:43:33 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of "xkbcomp -xkb $DISPLAY -",
* evtest against the device file (/dev/input/<find in /var/log/Xorg.0.log which one it is for your keyboard>), and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Andrig Miller 2011-06-21 19:12:38 UTC
Created attachment 505880 [details]
Xorg log file

Comment 3 Andrig Miller 2011-06-21 19:13:14 UTC
Created attachment 505881 [details]
xkbcomp command output

Comment 4 Andrig Miller 2011-06-21 19:28:14 UTC
Created attachment 505883 [details]
evtest output

My /var/log/messages files are empty.

Comment 5 Peter Hutterer 2011-08-11 23:13:45 UTC
kernel events look good, what does xev say about the events?

Comment 6 Andrig Miller 2011-11-21 05:54:08 UTC
I have been able to get this working with the following workaround.  I went into the keyboard layout settings, and into the miscellaneous compatibility options, and selected that the numeric keyboard should work like on the Macintosh.

Then it all works as expected.

Comment 7 Peter Hutterer 2011-11-29 04:27:29 UTC
heh. all that changes is that the default level of the numpad are the numbers, not the cursor keys. Pressing numlock should've had the same effect, no?

Comment 8 Andrig Miller 2011-11-29 04:34:15 UTC
(In reply to comment #7)
> heh. all that changes is that the default level of the numpad are the numbers,
> not the cursor keys. Pressing numlock should've had the same effect, no?



There is no numlock key on the HP Envy laptops.

Comment 9 Peter Hutterer 2011-11-29 04:38:13 UTC
ah, that explains it then. I'll close this as WORKSFORME, this is the simplest option you have if you don't have a numlock key.


Note You need to log in before you can comment on or make changes to this bug.