Bug 98495

Summary: grp:switch no longer works as a toggle
Product: xkeyboard-config Reporter: pogonyshev
Component: GeneralAssignee: xkb
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium CC: billic
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: workaround for altgr toggle from ru layout

Description pogonyshev 2016-10-29 21:07:20 UTC
I have two keyboard layouts: English and Russian. Among others I use the following command to configure keyboard:

    setxkbmap -option grp:switch

This made keyboard in English layout temporarily issue Russian characters as long as AltGr (right Alt) was pressed, and likewise temporarily issue English characters in Russian layout as long as AltGr is pressed. Main usecase was to type certain characters from English layout that are not present in Russian one, e.g. / or '.

Since recently, however, grp:switch doesn't work as it used to. In Russian layout it doesn't make any difference if AltGr is pressed or not, largely defeating the main purpose I used it for. I.e. in Russian layout AltGr+. used to type / (as it is the character on that key in English layout), now it types the dot, as if AltGr is not pressed.

Note that in English layout AltGr still works as before, so it's not like it completely doesn't work.

$ setxkbmap -version
setxkbmap 1.3.1
Comment 1 billic 2016-11-25 09:40:54 UTC
Created attachment 128187 [details] [review]
workaround for altgr toggle from ru layout
Comment 2 billic 2016-11-25 09:41:40 UTC
Have same layout (us.ru) and recently have troubles with switching back from russian layout. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704209 there is a workaround for epo layout in bugtracker.

Russian patch can be created like same.
Comment 3 Mihail Konev 2016-12-11 01:42:50 UTC
Fixed as of bf0263d2f8e7e0ff0135c47f9b7213931345fa94

*** This bug has been marked as a duplicate of bug 97057 ***

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.