setxkbmap set incorrect layer for swedish and alt-intl keyboards
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
x11-xkb-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
For my work and for real life I write a lot in English, Italian and Portuguese so on all my system desktop (Lubuntu 13.04), netbook and notebook (Lubuntu 13.10), I set my keyboard to US alternative international.
What I expect pressing the key " ' " followed by " c " from the keyboard is the special char " ç " (ALT code 135) but on 13.10 it
read it as a " ć ", when on 13.04 is working as expected.
I tried to configure it with the new keyboard layout Handler applet and with the old-but-good Lxkeymap but Lubuntu simply seems to ignore the existence of that character. The rest of the keyboard is working fine. This char is really important for Portuguese so it's a big issue. I tried with a standard Ubuntu 13.04/13.10 live, same behavior.
Another user on Lubuntu mailing list reported the same issue wih swedish keyboard:
2013/11/2 Nio Wiklund <@>:
I can confirm this behaviour also with Swedish keyboard
Examples
Acute accent + c prints ç in 12.04.3 but ć in 13.10
Acute accent + e prints é in 12.04.3 and 13.10
When I log in from a Lubuntu 13.10 client via ssh to a Xubuntu 12.04.3
ssh server, I get the 13.10 behaviour, so it seems connected to the
keyboard setting rather than interpreting the ascii code.
-------
Note that entering a TTY the keyboard do not change at all. It's stuck on US keyboard.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: x11-xkb-utils 7.7~1ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Sat Nov 2 08:24:59 2013
InstallationDate: Installed on 2013-10-30 (3 days ago)
InstallationMedia:
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
Status changed to 'Confirmed' because the bug affects multiple users.