Red Hat Bugzilla – Bug 348751
Euro and Dollar keys not working on Acer Laptop
Last modified: 2010-04-21 21:44:46 EDT
Description of problem:
Several Acer laptop models include special keys for Euro and Dollar signs. An
illustrating photo is available at
http://www.notebookreview.com/assets/5468.jpg. However, when pressing these keys
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a terminal window
2. Press Euro or Dollar key
3. Notice how nothing is printed
Euro and Dollar signs output after a keypress.
Might need a kernel change (yes, there's no such key as KEY_EURO in the kernel).
These will be fixed in upstream shortly:
So it's safe to close this one.
Actually, after two years, this still does not work with Fedora 12 Beta - reopening.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Yes this is still an issue but it seems that must wait for upstream:
CC'ing Peter who has provided the information there. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Euro/Dollar keys still not working with F13ß.
Closing as UPSTREAM.
The limit to keycodes < 255 is hardcoded in the X protocol and while it could be worked around doing so is prohibitively expensive. The newly released XI2 (X server 1.7) supports 32 bit keycodes but it'll take a while until toolkits start adopting this new input framework. Meanwhile, these keys won't work until that happens.
Keeping this bug open is not really changing anything much, upstream is quite aware of the issue but the effort to implement it is rather high (and doesn't depend on xkeyboard-config or X.Org alone). So I think deferring this is the best (well, not "best" but "right") resolution here.