AltGr does trigger Alt key when using en-us-intl layout

22 views
Skip to first unread message

5hp...@gmail.com

unread,
Feb 25, 2020, 2:48:01 PM2/25/20
to rdesktop User Discussion/Support
Hi!

I have to connect to a Windows 2012R2 server. I use the following command line to do that:
    rdesktop \
             -k en-us-intl \
             -x 0x80 \
             -r sound:local \
             -N \
             -a 16 \
             -g 1920x1080+0+0 \
             -K \
             windowserver.domain.com

However, when pressing AltGr+y/p/q I would like to get ü/ö/ä but instead the combination Alt+y/p/q is triggered.
It triggers the same event when using the Alt key directly.
I also tried with the normal en-us layout, but it has the same effect. Removing the -K option also does not change the behaviour.
I read a few things about AltGr beeing a weird key and often not behaving correctly on Windows, but there was always no clear solution...

On the client I use en-US-altgr-intl layout already, and the keyboard is an actual US layout:
$ setxkbmap -query rules: evdev model: pc105 layout: us variant: altgr-intl options: ctrl:nocaps

and I also tested with a second keyboard, but it did not change.

Is there something I can change or test on the client to make it work?
I do not have admin rights on the Windows machine.

Thanks in advance!

Best regards
Sebastian

5hp...@gmail.com

unread,
Feb 26, 2020, 9:42:58 AM2/26/20
to rdesktop User Discussion/Support
Today I tested on another PC, with another version, another keyboard and another operating system and even another window manager - so basically everything is different.
However, it works on that machine.
Interestingly enough, I can see that Windows shows me that I'm using ENG-INTL keyboard layout in the taskbar.
This was not the case when I connected from my workstation.

On the machine I'm right now, I had to download the en-us-intl layout from github, as the version installed there is pretty old (1.8.3 from CentOS - not sure why the intl layout is not in there?).
There are slightly different keyboard settings though:
$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     us
variant:    altgr-intl
options:    terminate:ctrl_alt_bksp

I'll further test if the version or my options in the xkbmap are the culprit.
Nevertheless, if someone has a clue what could be wrong, please give me a hint ;)

best regards
Sebastian
Reply all
Reply to author
Forward
0 new messages