IBM Thinkpad T61 key slash/question doenst works in Gutsy

Bug #182062 reported by Jose Carlos
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xkeyboard-config (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xmodmap

I have a IBM Thinkpad T61 (Type 7663-B93) that has a Brazillian ABNT2 keyboard.
Talking with IBM Support I discover thar this key is a Right Control , and was changed to slash/question.

To solve this problem I create a .Xmodmap file with:
-----------
keycode 109 = slash question degree
-----------

Tags: patch
Revision history for this message
Jose Carlos (jcnascimento) wrote :

Hi,

Debian already solved this bug, adding this code.

> | // ABNT2 Keyboard to IBM/Lenovo Thinkpads
> | // by Piter PUNK <email address hidden>
> | //
> | partial alphanumeric_keys
> | xkb_symbols "thinkpad" {
> |
> | include "br(abnt2)" // for consistent naming
> | name[Group1]="Brazil";
> |
> | key <RCTL> { [ slash, question, degree, questiondown ] };
> | };

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi jcnascimento,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in xkeyboard-config:
status: New → Incomplete
Revision history for this message
Jose Carlos (jcnascimento) wrote : Re: [Bug 182062] Re: IBM Thinkpad T61 key slash/question doenst works in Gutsy

Hi,

Well this bug is really old. It was already solved in Debian and in Ubuntu.

You can close it.

Regards,
Jose Carlos

2008/11/7 Bryce Harrington <email address hidden>:
> Hi jcnascimento,
>
>
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
>
> If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> Thanks in advance.
>
>
> The output of lspci -vvnn would also be worth having.
>
>
> ** Changed in: xkeyboard-config (Ubuntu)
> Status: New => Incomplete
>
> --
> IBM Thinkpad T61 key slash/question doenst works in Gutsy
> https://bugs.launchpad.net/bugs/182062
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "xkeyboard-config" source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: xmodmap
>
> I have a IBM Thinkpad T61 (Type 7663-B93) that has a Brazillian ABNT2 keyboard.
> Talking with IBM Support I discover thar this key is a Right Control , and was changed to slash/question.
>
> To solve this problem I create a .Xmodmap file with:
> -----------
> keycode 109 = slash question degree
> -----------
>

--
[]'s
José Carlos

Revision history for this message
Bryce Harrington (bryce) wrote :

Great, thanks for letting us know.

Changed in xkeyboard-config:
status: Incomplete → Fix Released
Revision history for this message
Adrovane Marques Kade (adrovane) wrote :

Hi.

I have a T61 myself, and everything was working fine with Ubuntu 8.10. However, after an upgrade I did today (Dec. 12, 2008), the slash/question/degree key stopped working. I tried the .Xmodmap trick and got no answer. Xev returns keycode 105, and not 109. So I changed Jose Carlos code, and it is working now. Any hints?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Also happened with my T61 when I upgraded to Intrepid. I opened another bug about it: bug #309042

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.