Japanese pc 106 keyboard closing curley brace is showing |

Bug #81994 reported by rashomon
8
Affects Status Importance Assigned to Milestone
xkeyboard-config (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am using ubuntu 6.10.
So far, I did not find any problem with
my japanese keyboard layout except one.
The closing curley brace is showing |(pipe).

Revision history for this message
suntin (gerard-payne) wrote :

same, curly brace is | and closing square bracket is \

oddly backslash is \ and pipe is |, on the pipe key yen shows as \
and on backslash key the underbar shows as _

Revision history for this message
Angus77 (andrewmcintosh-yahoo) wrote :

It's the same problem in Gutsy now. Strange, as it wasn't a problem in Feisty.

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

Hi himu11,

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
Angus77 (andrewmcintosh-yahoo) wrote :

I figured out what needed to be done on Gutsy. I think it had something to do with the difference between a keyboard _layout_ and a keyboard _model_. The problem was that picking one did get the other set automatically.

On Hardy and Intrepid it hasn't been a problem.

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

Thanks for letting us know it's no longer an issue; closing as fixed.

Changed in xkeyboard-config:
status: Incomplete → Fix Released
Revision history for this message
dareka (battosai00) wrote :

I would like to confirm what release was the bug fix incorporated. That is because the problem still persist on Ubuntu 9.04. This is a big deal for me since my laptop has a Japanese keyboard layout and I can't write a proper C code without close curlies!

Changed in xkeyboard-config (Ubuntu):
status: Fix Released → New
Revision history for this message
dareka (battosai00) wrote :

I would also like to add report things I have found out regarding the bug which I hope would help in debugging the problem.

I am not really knowledgeable on this, but with the help of the internet, I tried looking at the /usr/share/X11/xkb/symbols/jp file and the key layout seems to be according to what I was expecting.

Below is a part of the file:

    key <AC01> { [ a, A ] };
    key <AC02> { [ s, S ] };
    key <AC03> { [ d, D ] };
    key <AC04> { [ f, F ] };
    key <AC05> { [ g, G ] };
    key <AC06> { [ h, H ] };
    key <AC07> { [ j, J ] };
    key <AC08> { [ k, K ] };
    key <AC09> { [ l, L ] };
    key <AC10> { [ semicolon, plus ] };
    key <AC11> { [ colon, asterisk ] };
    key <AC12> { [ bracketright, braceright ] };

The key that is not working properly is the <AC12>. It is now currently outputting "\" and "|" instead of "]" and "}".

I have also noticed an interesting observation:
There is no such thing as AC12 on a normal US keyboard. (There are only 11 character keys on the row - asdfghjkl;'). However, if I switch the layout to US, the AC12 key (since I am using a Japanese keyboard it has the 12th key) will also output "\" and "|".

Revision history for this message
dareka (battosai00) wrote :
Revision history for this message
dareka (battosai00) wrote :
Revision history for this message
Angus77 (andrewmcintosh-yahoo) wrote :

@dareka I remember having this problem. I fixed it by going into System->Preferences->Keyboard->Layouts

I had to select _both_ the keyboard model (Japanese 106-key) _and_ the keyboard layout (Japanese). For some reason, in previous Ubuntus, one was being set correctly but the other wasn't. Although, I have not had this problem with Jaunty or Intrepid (neither on my desktop or my EeePC).

Revision history for this message
dareka (battosai00) wrote :

Thank you Angus77. The problem was already resolved by following your suggestion. I am not sure if this is just a work around or is this the way it is supposed to behave, I hope somebody can judge this and close this bug if possible. Thanks!

Revision history for this message
dareka (battosai00) wrote :

I was told by someone I shouldn't reopen a closed (changing the status from released->new) bug unless I am very sure that the bug was not fixed. Instead, I was told that it might be better for me to create a new bug report. I would like to apologize if I caused some sort of confusion. I would also like to know if there is some kind of wiki out there that I can read regarding the bug handling SOP in Launchpad, especially in the Ubuntu Project. Thanks!

Revision history for this message
xteejx (xteejx) wrote :

This bug report is being closed due to your last comment regarding this being fixed in a later supported version. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in xkeyboard-config (Ubuntu):
status: New → Invalid
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.