ABNT2 Numpad Keyboard keys misbehaving

Here is xev for dot in numeric key (above enter):

KeyRelease event, serial 33, synthetic NO, window 0x3000001,
    root 0x5c, subw 0x0, time 869347, (521,363), root:(525,412),
    state 0x10, keycode 129 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

And here it's for comma (beside enter):

KeyRelease event, serial 33, synthetic NO, window 0x3000001,
    root 0x5c, subw 0x0, time 990964, (769,432), root:(773,505),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XKeysymToKeycode returns keycode: 129
    XLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

I have the same error and output of xev.
In a contour solution I put the follow file .desktop entry in "/etc/xdg/autostart":
$ cat dot.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Keymap modifier
Comment=Keymap modifier to dot in numeric keypad
Icon=
Exec=xmodmap -e "keycode 129 = period"
Terminal=false
Type=Application
Categories=
OnlyShowIn=GNOME;XFCE;

Is this bug still open?

If the answer is yes...

So, It's NOW the time to fix it.

(to anyone with the proper credentials/rights)

https://bugs.launchpad.net/ubuntu/intrepid/+bugs

One week to go.

It is still open.

I've just booted the latest daily-live and this issue persists.

Everybody using ABNT2 will notice right away, because it is a such helpful key while you are typing numbers and currency values.

IMHO, it is a CRITICAL one.

It will be really great to have this bug fixed before Ibex release.

Thanks for reading this.

@Emmerson: another way to implement your nice fix tip:

sudo echo 'xmodmap -e "keycode 129 = period"' > /etc/init.d/keymap_modifier-abnt_numpad_dot.sh
sudo chmod +x /etc/init.d/keymap_modifier-abnt_numpad_dot.sh

Can someone please fix this bug? It is very annoying.
I am on Ubuntu 8.10 64bit.

xev for dot in numeric key (above enter):

KeyPress event, serial 31, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 49731679, (-760,347), root:(496,406),
    state 0x10, keycode 129 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

And for comma in numeric key (beside enter):

KeyPress event, serial 34, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 49774072, (-106,8), root:(1150,67),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XKeysymToKeycode returns keycode: 129
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

working on it, and trying to figure out why it worked before..

Uploaded a new version to intrepid-proposed, please test when it's built. It changes <I129> to use keycode 60 (dot) instead of 129.

I rejected the current upload in -proposed queue. It removes a lot of debian/patches/* stuff, and changes other files:

$ mdebdiff -s intrepid xkeyboard-config_1.3-2ubuntu4.1.dsc |lsdiff
xkeyboard-config-1.3/patches/series
xkeyboard-config-1.3/patches/100_abnt2.diff
xkeyboard-config-1.3/patches/100_abnt2_jp106.diff
xkeyboard-config-1.3/rules/base.lst
xkeyboard-config-1.3/rules/evdev.lst
xkeyboard-config-1.3/rules/base.xml
xkeyboard-config-1.3/rules/evdev
xkeyboard-config-1.3/rules/base
xkeyboard-config-1.3/rules/evdev.xml.in
xkeyboard-config-1.3/rules/evdev.xml
xkeyboard-config-1.3/po/POTFILES
xkeyboard-config-1.3/debian/changelog
xkeyboard-config-1.3/debian/patches/100_abnt2_jp106.diff

I don't suppose that this is intended. If it is, please upload it again and describe the rationale in the changelog. Thanks!

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Bad news,,,,,
Now the dot/period key in numeric keypad key does NOT work anymore and the main dot/period key is displaying a COMMA too,,, :(
Jesus,,,, Cant you guys just copy the old package from hardy????

That's wonderful. Now I can't even type a whole URL in the browser.

Probably I'll hack this tomorrow and post here a solution for both
"dots". I would warn the maintainer to do not touch in something that
is working so far ok, as it was long time ago, or at least, check with
someone (any user with an ABNT2 keyboard, for example) that has the
right keyboard to test every keystroke.

2008/11/14 sergio <email address hidden>:
> Bad news,,,,,
> Now the dot/period key in numeric keypad key does NOT work anymore and the main dot/period key is displaying a COMMA too,,, :(
> Jesus,,,, Cant you guys just copy the old package from hardy????
--
Márcio Bremm -- http://vtnc.org/

Pessoas não mudam, apenas mascaram sua real identidade.
People don't change, only mask their real identity.
Люди не меняются, только маскируют свою реальную идентичность.

I had the same problems here with the package in proposed. And had to 'downgrade' to the package in the main repository.

I have found a solution to the problem.
In System -> Preferences -> Keyboard
Go to Layouts, then Other Options. In "Numeric keypad layout selection" choose "Legacy keypad". That is it.

Now please, can someone remove the package from proposed and put the "Legacy keypad" option as default?

Sorry but it doesn't work that way. I have no idea what 'legacy keypad' does.. please provide the output of 'xprop -root |grep XKB'.

I don't understand (yet) why the patch worked exactly the opposite way, but this is what -proposed is for (testing). You can downgrade the package by running 'apt-get install xkb-data=1.3-2ubuntu4' and wait for a new version.

I have the same problem here,
Here's the output off 'xprop -root |grep XKB':
_XKB_RULES_NAMES(STRING) = "evdev", "abnt2", "br", "", ""

I just installed Intrepid on a Dell Latitude 120L laptop with ABNT2 keyboard, so I have only one 'dot' key, which I guess maps to the regular dot key on standard keyboards, and I can confirm that the 'dot' inputs a comma with xkb-data-1.3-2ubuntu4.1.

The 'solution' for the time being seems to be downgrading to xkb-data-1.3-2ubuntu4.

I'm waiting for a better solution and willing to help with testing, if needed.

Please update your Ubuntu after day 15 - Nov, All key point now is comma,

Timo,

After I downgraded to 1.3-2ubuntu4, the both keys worked. If I can help somehow, tell me. I'm using Intrepid with KDE.

I had the same problem in my Notebook after install the update of my Ubuntu Iterpid, today, including the package xkb-data1.3-2ubuntu4.1.
I make a downgrade the package to previous version (xkb-data-1.3-2ubuntu4), as suggested by TIMO, and the kay worked properly.
I am ready to assist where necessary to resolve, finally, this bug

My point key have the same problem. Now is comma key (and "greater" disappear)

I see this differences from xkb-data1.3-2ubuntu4.1 to xkb-data1.3-2ubuntu4

diff -ur xkb/keycodes/evdev /root/xkb/keycodes/evdev
--- xkb/keycodes/evdev 2008-09-17 07:26:52.000000000 -0300
+++ /root/xkb/keycodes/evdev 2008-11-14 08:30:21.000000000 -0200
@@ -311,6 +311,7 @@
 // For brazilian ABNT2 keyboard.
 xkb_keycodes "abnt2" {
     include "evdev(evdev)"
+ <I129> = 60;
 };

 // PC98
root@ltdesk:/usr/share/X11#

so the "<I129> = 60;" entry was deleted , and cause the problem.

My keyboard is a ABNT2, Brazilian generic.

This bug came back today after an update of package xkb-data in the proposed repository.
I had to revert the upgrade to solve the problem.
The version "1.3-2ubuntu4" of package xbk-data (in main repository) it's working fine.

I might have have found the problem.

The generic Brazil ABNT2 keyboard layout is attached.
The main difference in keypad is that the key besides the enter is a comma and there is a key above enter (dot).

In /usr/share/X11/xkb/geometry/pc there is the ABNT2 layout map. The numpad dot key is <KPPT> and comma is <KPDL>.

In /usr/share/X11/xkb/keycodes/evdev there is the following code:

// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
    include "evdev(evdev)"
};

In evdev, the keycode for <KPDL> is 91, which correctly outputs a comma. But there is no definition for the <KPPT> key, which should have the keycode 129 (dot).

So, I modified the ABNT2 code in the evdev file to:
// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
    include "evdev(evdev)"
    <KPPT> = 129;
};

And now everything is working how is supposed to.
I am a completely newbie in this stuff, so I am not sure about this.

Here is my output from 'xprop -root | grep XKB' and xev:
_XKB_RULES_NAMES(STRING) = "evdev", "abnt2", "br", "", ""

xev for numpad comma:

KeyPress event, serial 33, synthetic NO, window 0x3000001,
    root 0x1a6, subw 0x0, time 2036170, (298,-52), root:(309,643),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x3000001,
    root 0x1a6, subw 0x0, time 2036286, (296,-69), root:(307,626),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

xev for numpad dot

KeyPress event, serial 33, synthetic NO, window 0x3000001,
    root 0x1a6, subw 0x0, time 2073656, (58,-4), root:(69,691),
    state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XmbLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x3000001,
    root 0x1a6, subw 0x0, time 2073738, (58,-4), root:(69,691),
    state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

Hi

After my upgrades this morning, the comma and dot from the keypad
and from the "regular" keyboard stopped working. I just could
get commas.

Downgrading as Timo Aaltonen suggested (with 'apt-get install xkb-data=1.3-2ubuntu4')
didn't help.

Suggestion from Leonardo Couto kind of worked, with a small add:

In /usr/share/X11/xkb/keycodes/evdev there should be only:

// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
    include "evdev(evdev)"
    <KPPT> = 129;
};

If there's a:
    <I129> = 60;

in it, like Leonardo Marques de Souza said it was earlier in
the xkb-data1.3-2ubuntu4 , it doesn't work.

So, after downgrading and editing the /usr/share/X11/xkb/keycodes/evdev,
mine looks now:

// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
    include "evdev(evdev)"
    // <I129> = 60 Removed!!!!
    <KPPT> = 129;
};

Thanks, hope it helps!

Walter Ribeiro de Oliveira Jr

Update:

-> my ' xprop -root | grep XKB' :

_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "abnt2", "br", "", ""
_XKB_RULES_NAMES(STRING) = "evdev", "abnt2", "br", "", ""

-> my xev for:

1 - keypad dot:
KeyPress event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 769476, (287,268), root:(949,317),
    state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XmbLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 769636, (287,268), root:(949,317),
    state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

2 - keypad comma:
KeyPress event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 797337, (205,918), root:(867,967),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 797442, (205,918), root:(867,967),
    state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

3 - Keyboard dot:
KeyPress event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 824701, (61,715), root:(723,764),
    state 0x10, keycode 60 (keysym 0x2e, period), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XmbLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 824800, (61,715), root:(723,764),
    state 0x10, keycode 60 (keysym 0x2e, period), same_screen YES,
    XLookupString gives 1 bytes: (2e) "."
    XFilterEvent returns: False

4 - Keyboard comma:
KeyPress event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 845875, (41,797), root:(703,846),
    state 0x10, keycode 59 (keysym 0x2c, comma), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XmbLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3600001,
    root 0x8b, subw 0x0, time 845953, (41,797), root:(703,846),
    state 0x10, keycode 59 (keysym 0x2c, comma), same_screen YES,
    XLookupString gives 1 bytes: (2c) ","
    XFilterEvent returns: False

Bye!

Ok, now I really don't get it!
I downgraded to 1.3-2ubuntu4 and the Update Manager
told me there was an upgrade for this buggy one...
But it says this in the "changes" tab:

Version 1.3-2ubuntu4.1:
  * 100_abnt2_jp106.diff: Fix keycode 129 to produce a dot instead of
    a comma. (LP: #272606)

What the hell? If things aren't fixed, why does it say so?

Man, this bug is one month old already...
That's sad :(

This bug is actually almost 2 months old already.

Regarding your doubt, version 4.1 was supposed to fix this, but it didn't.
If you downgrade to version 4, Update Manager will tell you there's an update, since the 4.1 package wasn't dropped off the repository.

You just have to keep ignoring version 4.1 until there's a proper fix released.

You also can pin the old version using Synaptic.

2008/11/17 Leon Nardella <email address hidden>:

> You just have to keep ignoring version 4.1 until there's a proper fix
> released.
--
Márcio Bremm -- http://vtnc.org/

Pessoas não mudam, apenas mascaram sua real identidade.
People don't change, only mask their real identity.
Люди не меняются, только маскируют свою реальную идентичность.

Leonardo: thanks for doing the research, it looks like you found the cure! I'll upload a new package tomorrow. Sorry and thanks for your patience. Ignore 4.1 for now and wait for 4.2.

Accepted updated package, please test:

 xkeyboard-config (1.3-2ubuntu4.2) intrepid-proposed; urgency=low
 .
   * 100_abnt2_jp106.diff: The previous fix was wrong. ABNT2 has KPPT
     which should produce keycode 129. Thanks Leonardo Couto!
     (LP: #272606)

It solved for me.

Just needed to restart the X after the upgrade.

Congrats.

Version 4.2 did the trick for me too.

Solved. 4.2 works.

2008/11/21 Leon Nardella <email address hidden>:
> Version 4.2 did the trick for me too.
>
> --
> ABNT2 Numpad Keyboard keys misbehaving
> https://bugs.launchpad.net/bugs/272606
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "xkeyboard-config" source package in Ubuntu: Fix Committed
> Status in xkeyboard-config in Ubuntu Intrepid: Fix Committed
>
> Bug description:
> Binary package hint: xkeyboard-config
>
> The ABNT2 numpad keyboard have some keys misbehaving on the latest intrepid ibex.
>
> The dot/period (.) key is actually printing a comma ( , ) instead of a period/dot ( . )
>
> ubuntu@ubuntu:~$ apt-cache policy xkb-data
> xkb-data:
> Instalado: 1.3-2ubuntu4
> Candidato: 1.3-2ubuntu4
> Tabela de versão:
> *** 1.3-2ubuntu4 0
> 500 http://archive.ubuntu.com intrepid/main Packages
> 100 /var/lib/dpkg/status
>

--
Leonardo Marques de Souza

Back using Ubuntu. This time, Jaunty.

I'm glad to see this bug wiped out.

Please, don't forget to make this fix available for Jaunty too!

Congrats to everyone involved.

It solved for me.

This bug was fixed in the package xkeyboard-config - 1.3-2ubuntu4.2

---------------
xkeyboard-config (1.3-2ubuntu4.2) intrepid-proposed; urgency=low

  * 100_abnt2_jp106.diff: The previous fix was wrong. ABNT2 has KPPT
    which should produce keycode 129. Thanks Leonardo Couto!
    (LP: #272606)

 -- Timo Aaltonen <email address hidden> Tue, 18 Nov 2008 07:17:59 +0200

Copied to intrepid-updates and jaunty.

It solved for me too. Thanks.

It solved for me too. Thank you very much!!

T.P.

Tested in 5 computers and solved

now fixed in upstream too

Dont work for me :(

This bug is back on the very latest karmic koala updates.

On the numpad the dot/period (.) key is again printing a comma ( , ) instead of a period/dot ( . )

$ apt-cache policy xkb-data
xkb-data:
  Instalado: 1.6-1ubuntu1
  Candidato: 1.6-1ubuntu1
  Tabela de versão:
 *** 1.6-1ubuntu1 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Can anyone else confirm the return of this bug?

Thanks for reading

I can confirm myself.

This bug is back!

bump

Hm, current karmic /usr/share/X11/xkb/keycodes/evdev has

        <I129> = 129; // #define KEY_KPCOMMA 121
        // For Brazilian ABNT2
        alias <KPPT> = <I129>;

which still looks pretty much the same as in the upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=18712

Does changing the alias line to

  <KPPT> = 129

work for you?

This is related: http://bugs.freedesktop.org/show_bug.cgi?id=22303

here's the upstream fix, feel free to fix it locally for now.

http://cgit.freedesktop.org/xkeyboard-config/commit/?id=fd7fa190c4f817bacac23c98e43c61b60064bffd

Edit the file:

$ sudo gedit /usr/share/X11/xkb/symbols/inet

removing the line 'key <I129> { [ KP_Separator ] };'

It works!

This bug was fixed in the package xkeyboard-config - 1.6-1ubuntu2

---------------
xkeyboard-config (1.6-1ubuntu2) karmic; urgency=low

  * Add abnt2-mapping-of-dot-key.patch, to fix ABNT2 numpad keyboards to
    print period/dot instead of comma. Cherrypick from upstream.
    (LP: #272606)

 -- Bryce Harrington <email address hidden> Thu, 20 Aug 2009 10:42:47 -0700

I can confirm this bug in a beta Karmic Koala with all the updates.

Please note, however, that this "coma" [,] instead of "dot" [.], as far as I could tell, only happens in OpenOffice, but not on other applications, such as Gedit, Firefox or even in Terminal for they correctly handle the dot [.] sign of the dot [.] key.

I was going to try the fix Herbert suggested, but could not find the line mentioned but only:

 key <I129> { [ KP_Decimal ] };

Which means -- at least according to my understand, please correct me if I'm wrong -- that the fix mentioned by Timo Aaltonen has already been applied. But I still get "comas" [,] while pressing the "dot" [.] key at the numeric side of the keyboard.

I'm not sure how I could help with this matter, but please advice and I would be willing to provide further info and/or attach my config or log files.

Thank you
____________________________________________

uname -a
Linux fabio-desktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

Thank you for your report, but in the ABNT2 keyboard (pt-BR), you are
supposed to get a [,] (coma) instead of a [.] (dot) at the numerical
keyboard.

We do not dot a decimal number in portugues... we PUT A COMA.

This is the expected behavior. Do NOT try to fix what aint broken.

By the way, it works for me at karmic koala (9.10) under evry single
application I could test, including Firefox, Google Chrome, OpenOffice
(all), Gedit.

2009/10/21 Fabio M. P. Bugnon <email address hidden>

> I can confirm this bug in a beta Karmic Koala with all the updates.
>
> Please note, however, that this "coma" [,] instead of "dot" [.], as far
> as I could tell, only happens in OpenOffice, but not on other
> applications, such as Gedit, Firefox or even in Terminal for they
> correctly handle the dot [.] sign of the dot [.] key.
>
> I was going to try the fix Herbert suggested, but could not find the
> line mentioned but only:
>
> key <I129> { [ KP_Decimal ] };
>
> Which means -- at least according to my understand, please correct me if
> I'm wrong -- that the fix mentioned by Timo Aaltonen has already been
> applied. But I still get "comas" [,] while pressing the "dot" [.] key at
> the numeric side of the keyboard.
>
> I'm not sure how I could help with this matter, but please advice and I
> would be willing to provide further info and/or attach my config or log
> files.
>
> Thank you
> ____________________________________________
>
> uname -a
> Linux fabio-desktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01
> UTC 2009 x86_64 GNU/Linux
>
>
> ** Attachment added: "inet"
> http://launchpadlibrarian.net/34120500/inet
>
> --
> ABNT2 Numpad Keyboard keys misbehaving
> https://bugs.launchpad.net/bugs/272606
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Fábio Leitão
..-. .- -... .. --- .-.. . .. - .- --- ...-.-
&#70;&#97;&#98;&#105;&#111;&#32;&#76;&#101;&#105;&#74;&#97;&#111;
h0x46 h0x61 h0x62 h0x69 h0x6F h0x20 h0x4C h0x65 h0x69 h0x74 h0x61 h0x6F

Sorry - I might have not stressed out the circumstances clearly:

The problem -- as previously noted [Leonardo Couto wrote on 2008-11-17] -- is that in ABNT2 (or in "some" ABNT2 - even if this shouldn't be possible, right?) we have BOTH keys: the coma [,] and the dot [.].

So, even if we do use comas as decimal separator in pt_BR I guess one could expect -- since we have both keys -- that [.] act like [.] and [,] as [,] ;). Even because we do (or some of us at least) use dots as thousands separator, so it's good to have it at hand when typing big figures.

Furthermore, as mentioned, they actually already do work as expected (coma-coma, dot-dot) in most -- if not all -- applications, except for OpenOffice.

The layout showing both keys was attached by Leonardo Couto and could be seen at http://launchpadlibrarian.net/19709373/output1.pdf

I am sorry I did not understand it properly before, there was a similar
issue in a previous release.
I have tested now in my system as described and I actually do get the same
problem you have (i.e in the numeric keypad the dot gives a coma when typed
in the OpenOffice suite)

2009/10/22 Fabio M. P. Bugnon <email address hidden>

> Sorry - I might have not stressed out the circumstances clearly:
>
> The problem -- as previously noted [Leonardo Couto wrote on 2008-11-17]
> -- is that in ABNT2 (or in "some" ABNT2 - even if this shouldn't be
> possible, right?) we have BOTH keys: the coma [,] and the dot [.].
>
> So, even if we do use comas as decimal separator in pt_BR I guess one
> could expect -- since we have both keys -- that [.] act like [.] and [,]
> as [,] ;). Even because we do (or some of us at least) use dots as
> thousands separator, so it's good to have it at hand when typing big
> figures.
>
> Furthermore, as mentioned, they actually already do work as expected
> (coma-coma, dot-dot) in most -- if not all -- applications, except for
> OpenOffice.
>
> The layout showing both keys was attached by Leonardo Couto and could be
> seen at http://launchpadlibrarian.net/19709373/output1.pdf
>
> --
> ABNT2 Numpad Keyboard keys misbehaving
> https://bugs.launchpad.net/bugs/272606
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Fábio Leitão
..-. .- -... .. --- .-.. . .. - .- --- ...-.-
&#70;&#97;&#98;&#105;&#111;&#32;&#76;&#101;&#105;&#74;&#97;&#111;
h0x46 h0x61 h0x62 h0x69 h0x6F h0x20 h0x4C h0x65 h0x69 h0x74 h0x61 h0x6F

Take a look at http://www.openoffice.org/issues/show_bug.cgi?id=1820

It's a OOo problem, not a keyboard - keymap - keypad one.

Since it works ok in all applications (at least, the few ones I tested)
but doesn't work in OOo, who should fix it is the OOo team.

Bye!

This bug still happen to me on gnome-terminal, openoffice writer and in the text mode (ctrl+alt+f1-f6).

Hello guys,

    What a persistent bug! I'm in Ubuntu 10.4 and it is still there: when pressing the dot in the numeric keypad, I get Comma. That's pretty much consistent in several machines with ABNT2 keyboards.

     Any quick fixes?

cheers!

On Tue, Nov 23, 2010 at 10:02:28PM -0000, Breno Jacinto wrote:
> Any quick fixes?

If you're looking for quick technical support to work around issues,
please use askubuntu.com or one of the other support options listed at
www.ubuntu.com/support.