[Thinlinc-technical] Cannot switch keyboard layout

Pierre Ossman ossman at cendio.se
Thu Jan 21 11:21:14 CET 2016

On Wed, 20 Jan 2016 17:47:00 +0100
Torsten Kasch <tk at CeBiTec.Uni-Bielefeld.DE> wrote:

> On 20.01.2016 16:40, Pierre Ossman wrote:
> [...]
> > I'm afraid this is how VNC works (and therefore ThinLinc) at the
> > moment. Other systems generally send physical key identifiers, but
> > VNC sends the symbol instead. That means that in other systems the
> > layout on the server (or in the virtualised guest) is what matters.
> > But with VNC the layout of the client is what's relevant.
> I was afraid you would say that... :-(

Note that this is only how it works now. It could be changed in the
future if we want to. We have a bugzilla entry for this:


But switching trades some problems for other ones, so it's still up for
debate which model should be used. At the moment it's not something
we're working on.

> Just curious: What's the use of having a
> $TLPREFIX/libexec/tl-default-keyboard which seems to only call
> setxkbmap(1) if it isn't possible to actually set the layout from
> within a VNC session?

There are some problems with the current approach, but most of those can
be solved if the client and server have the same layout configured.

If you're not hitting those problems then this setting doesn't matter.

Pierre Ossman           Software Development
Cendio AB		https://cendio.com
Teknikringen 8		https://twitter.com/ThinLinc
583 30 Linköping	https://facebook.com/ThinLinc
Phone: +46-13-214600	https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

More information about the Thinlinc-technical mailing list