Skip to content

Citrix virtual desktop: AltGr+keys do not display (properly) #1266

@PeterASchneider

Description

@PeterASchneider

I am using mintty with msys2 and cygwin on Windows 10 22H2.

Around the time of upgrading to Win 10 22H2, characters only reachable through an AltGr combination stopped working properly: {[]}\, which are dearly needed for programming. The keys work in all other programs, including a cygwin console. I checked with cygwin/mintty 3.0.0 as well as msys2/mintty 3.7.1.

I can type the characters using the Ctrl+Alt modifiers after enabling "Ctrl-LeftAlt is AltGr" in the options. I can also paste them from the clipboard, potentially from the same terminal (they display just fine).

I am accessing the computer in question through two indirections: I access a virtual client through citrix from which I initiate a remote desktop session to the actual work machine.

Pressing the keys in mintty with a bash, preceded by Ctrl-V, produces the following output:

  • {: Displays nothing but erases the line input and jumps to column 1
  • [: Displays ^[
  • ]: Displays ^]
  • }: Displays ^[[1;7p
  • \: Displays ^\

The Windows events arriving in mintty when I press AltGr, continue to hold it while I press \, and then release both, are

<000518> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:1 fUp:0
<000519> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:0
<000520> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:1 fUp:0
<000521> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:0
<000522> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:1 fUp:0
<000523> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:0
<000524> 00000000002410B4 P WM_KEYDOWN nVirtKey:VK_OEM_4 cRepeat:1 ScanCode:0C fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<000525> 00000000002410B4 P WM_KEYUP nVirtKey:VK_OEM_4 cRepeat:1 ScanCode:0C fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<000526> 00000000002410B4 P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1
<000527> 00000000002410B4 P WM_KEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:1 fUp:1

On my home computer, also Win10 22H2, where I don't have the issue, the sequence is slightly different: The key-down pairs for AltGr come in the order VK_CONTROL->VKMENU, while they come in the order VK_MENU->VK_CONTROL on the remote machine with the problem.

<000001> 0000000000B90CC8 P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<000002> 0000000000B90CC8 P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0
<000003> 0000000000B90CC8 P WM_KEYDOWN nVirtKey:VK_OEM_4 cRepeat:1 ScanCode:0C fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<000004> 0000000000B90CC8 P WM_KEYUP nVirtKey:VK_OEM_4 cRepeat:1 ScanCode:0C fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<000005> 0000000000B90CC8 P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<000006> 0000000000B90CC8 P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions