Bug 25338 - Keyboard map not recognized on Thinkpad T61 (pt-br layout)
Summary: Keyboard map not recognized on Thinkpad T61 (pt-br layout)
Status: RESOLVED NOTOURBUG
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xkb
QA Contact:
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-29 05:29 UTC by Renato S. Yamane
Modified: 2009-11-29 05:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Renato S. Yamane 2009-11-29 05:29:33 UTC
On my last "aptitude upgrade", after restart the Debian Squeeze the keyboard map is not recognized anymore.

My keyboard is pt-br (Lenovo Thinkpad T61), with "ç", and somekeys is not recognized anymore, such slash ("/").

To fix this on KDE, I go to System Config --> Regional and Language --> Keyboard Layout, and set keyboard map to "Thinkpad R60/T60/R61/T1" and map/tag to BR.

After I did this, xev show me:

KeyPress event, serial 31, synthetic NO, window 0x4800001,
    root 0x13c, subw 0x0, time 795411, (710,409), root:(714,826),
    state 0x0, keycode 105 (keysym 0x2f, slash), same_screen YES,
    XKeysymToKeycode returns keycode: 97                         
    XLookupString gives 1 bytes: (2f) "/"                        
    XmbLookupString gives 1 bytes: (2f) "/"                      
    XFilterEvent returns: False                                  

KeyPress event, serial 34, synthetic NO, window 0x4800001,
    root 0x13c, subw 0x0, time 816463, (710,409), root:(714,826),
    state 0x0, keycode 47 (keysym 0xe7, ccedilla), same_screen YES,
    XLookupString gives 2 bytes: (c3 a7) "ç"
    XmbLookupString gives 2 bytes: (c3 a7) "ç"
    XFilterEvent returns: False


----> BUT, this don't fix the problem on console <------

Debian team (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558386) tell me to report this bug here, so here I'm.

Regards,
Renato S. Yamane
Comment 1 Sergey V. Udaltsov 2009-11-29 05:43:15 UTC
If xev displays correct characters, XKB is configured correctly. The rest is up to your toolkit or the application. I'd recommend filing new bug in KDE's bugzilla.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.