overhaul keyboard handling

[uli42]

(09:47:09) uli42: Ionic: the main problem from my point of view is that x2goclient passes null/null as keyboard. nxagent cannot handle that properly. I implemented a fix yesterday but it turned out not to help. The code is broken somehow and nees an overhaul.
(09:47:13) Ionic: but we don't actually apply that in nxagent
(09:47:29) Ionic: yeah, because nxagent doesn't actually do that
(09:47:34) Ionic: x2goserver does it
(09:48:01) Ionic: essentially, nxagent merely queries the remote (client-side) keyboard settings and writes it into the keyboard file in the session directory
(09:48:27) Ionic: from there, x2goserver takes over and if the keyboard type is set to auto, it uses setxkbmap to apply the dumped config
(09:48:38) uli42: We should define how keyboard is gonna behave:
(09:48:38) uli42: 1. if user passes kbtype= use that
(09:48:38) uli42: 1a) if the value is null/null or query user want autoconf
(09:48:38) uli42: 2. if user did not pass anything try autoconf
(09:48:38) uli42: 3. if 1 and 2 produce no results try global config file
(09:48:38) uli42: 4. else use builtin default
(09:49:04) Ionic: yes yes, but nxagent never behaved in that way
(09:49:17) Ionic: we should extend it to do that by itself and NOT depend upon x2goserver to do it, I guess
(09:49:25) Ionic: so open a bug report for this so we can track it
(09:49:41) uli42: Ionic: thsi is something that really should be done inside nxagent. a) because everyone needs that functinality b) it simplyfies things
(09:49:57) Ionic: but now that I understand what is actually happening, my bet is even stronger on variant="," breaking things
(09:50:25) uli42: tell me more!
(09:50:27) Ionic: uli42: I agree, that's why I asked for a bug report to track this, but it's not a high-priority problem