Vino VNC connection has wrong keyboard layout

[Stefan König]

After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections use the wrong keyboard layout.
By default I use "DE" keyboard layout.

If I connect from another 18.04.3 machine to said vino on the upgraded 18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys are as well not correct.
I can only fix this by running
 sudo dpkg-reconfigure keyboard-configuration
in a console (pressing Enter all the way through and confirm settings) and rebooting. If I connect to vino VNC after issueing this command and rebooting, the layout is correct until next reboot. Then I have to issue this command again and so on.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vino 3.22.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Dec 6 12:52:22 2019
InstallationDate: Installed on 2017-12-29 (707 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: vino
UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago)

[Stefan König (muelladdi)]

The problem seems to get worse, as in 90% of the cases the above mentioned
  sudo dpkg-reconfigure keyboard-configuration
does not fix the problem anymore. I have to cycle reboots for 10-20 times until I get the correct mapping. Any help is appreciated.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Peter Valdemar Mørch (pmorch)]

I'm using Xubuntu (XFCE) version 18.04 on both ends.

sudo dpkg-reconfigure keyboard-configuration

is configured for a danish keyboard on both ends.

Hitting the 'æ' key in a terminal on the local side produces an 'æ' in the terminal.

Hitting the 'æ' key in a terminal on the remote vnc side produces an ';' in the terminal. The placement of an 'æ' on a danish keyboard is in the same place as ';' on a US keyboard (I think).

[Peter Valdemar Mørch (pmorch)]

Oh, and I just tried x11vnc. It does *not* have this problem. I'm pretty sure this is a vino problem.

[quadra (info06)]

I've the same bug in vino3.22.0-5ubuntu0.1, Linux Mint 19

It makes vino basically unusable for all non-US users.
It's definitely in vino server, not in the vnc client.
Workaround ''sudo dpkg-reconfigure keyboard-configuration'' doesn't work for me
It's a regression, bug was not there e.g. in vino3.8.1-0ubuntu9.4 on ubuntu 16.04