Description of problem: Haven't tried to debug but while testing noticed that selecting China or Korea xkb layouts in input-pad results in USA layout being selected. Version-Release number of selected component (if applicable): input-pad-1.0.0-1.fc14 How reproducible: every time Steps to Reproduce: 1. start input-pad 2. select China or Korea keyboard 3. Actual results: USA keyboard selected Expected results: China (or Korea) layout
Currently input-pad supports layouts only. I agree to support variants and options. I guess the main issue is kr(kr104). I also noticed another issue. GDK clients sometimes don't call XkbGetUpdatedMap() because MappingNotify event is not received.
Fixed to add variants: https://github.com/fujiwarat/input-pad/commit/9abdbeed14755231281d43b766d2cc4ac12ec0ea http://koji.fedoraproject.org/koji/taskinfo?taskID=3080540
input-pad-1.0.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/input-pad-1.0.1-1.fc15
input-pad-1.0.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/input-pad-1.0.1-2.fc14
input-pad-1.0.1-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/input-pad-1.0.1-2.fc13
Package input-pad-1.0.1-2.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing input-pad-1.0.1-2.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/input-pad-1.0.1-2.fc14 then log in and leave karma (feedback).
input-pad-1.0.1-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
input-pad-1.0.1-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
input-pad-1.0.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.