Bug 83793 - In gEdit I can't write the numbers from keypad
In gEdit I can't write the numbers from keypad
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: gedit (Show other bugs)
9
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Havoc Pennington
: MoveUpstream, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-08 15:45 EST by Antonio Sanna
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-10-06 17:42:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Antonio Sanna 2003-02-08 15:45:32 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030203

Description of problem:
I have an italian keyboard and I can't write the numbers (except 5) from keypad
in gEdit (with blocknum activated, naturally): the cursor moves like if the
blocknum is off. With Mozilla and OpenOffice all is ok.
The keyboard is PS/2.
Comment 1 Havoc Pennington 2003-02-12 16:57:51 EST
Do you get the same problem in other gtk 2 applications, for example 
in "gtk-demo" double click "text widget" on the left side and 
try typing into the text area that pops up?
Comment 2 Antonio Sanna 2003-02-13 11:21:54 EST
No, in gtk-demo all is ok.
N.B.: the system language is english, only the keyboard is italian: I don't know
if this can help you.
Comment 3 Antonio Sanna 2003-02-21 10:10:05 EST
In beta3 all is ok! Thank you: you can to close the bug.
Comment 4 Owen Taylor 2003-10-06 17:42:47 EDT
There were some fixes in GTK+ related to numeric keypad handling if
you disabled the XKB extension. This might be related to that.

In any case, if it works now, there's not much more we can to debug
what was going on :-)

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