You are not logged in.
Hail there, my friends. Don't know if this would be the correct forum for such a post, but it was the closest I could find. Well, I have a brazilian keyboard using ABNT2 layout. Don't know if you're familiarized with it, but in Brazil the decimal separator is a ',' (comma) and the thousands separator is a '.' (dot). Thus, the numpad layout has a ',' between the '0' and 'ENTER' keys and a '.' between the '+' and 'ENTER' keys. The problem was that both my dot and comma keys from my numpad printed a ',' (comma) character in the screen. Digging around the internet I ended up tracking the issue to my xkb configuration and, possibly, to the "xkeyboard-config 1.6-1" package. Here are some related links:
* https://bugzilla.redhat.com/show_bug.cgi?id=470153
- confirmation of bug in Fedora
* https://bugs.launchpad.net/ubuntu/+sour … bug/272606
- bug report for Ubuntu
Well, from the reading of the posts from both links, it certainly seems to be the package mentioned before. Ubuntu seems to have assimilated the fix to their version of the package, "xkeyboard-config - 1.6-1ubuntu2". I managed to 'fix' the bug (don't know if it can be called a fix; maybe someone with more experience could point out the correct way to do it, if any) by commenting out a line in the 'inet' file, as mentioned in the Ubuntu bug report. In details:
- use preferred text editor to edit (as root) 'inet' file located under /usr/share/X11/xkb/symbols (e.g. "vi /usr/share/X11/xkb/symbols/inet")
- find and comment out (with //) the line that reads: key <I129> { [ KP_Separator ] };
- save and exit the document;
- restart X or reboot the PC.
It seems like there really is a bug with the ABNT2 layout, as it was declared and recognized as one by both Ubuntu and Fedora. It started happening with the newer versions of the aforementioned package (xkeyboard-config). Many people from other distros reported that downgrading may fix the issue. Maybe something was messed in the package configuration for newer versions, and the above modifications seem to stop the issue from ocurring. However I do not really know if the above could be considered a 'fix'. Anyone else having this problem? Maybe we could confirm it for Arch too...
Thanks for any attention given.
Last edited by gabscic (2009-08-23 07:31:18)
Offline