On 31/12/13 10:42, Martin (KDE) wrote:
Am 23.12.2013 18:05, schrieb Roderick Johnstone:
Hi
I'm trying to establish an F20 x2go kde session with the correct
keyboard type and mapping for my clients' keyboards (pc105/gb, and mac).
What I get when I log in is always a us keyboard map for a pc105 keyboard.
I've tried starting the x2go session with a simple xterm, and found that
I can get the correct keyboard mapping as set by the x2go windows
client. (I had to touch a file /usr/share/X11/xkb/keymap.dir to get this
to work though.)
Since the keyboard map is correct in the Xterm session but wrong in the
kde session it looks like x2go is setting the keyboard/map ok but that
kde is somehow overriding what is being set by x2go. (I've tried with
Keyboard daemon both checked and unchecked in System Settings ->
Startup and Shutdown -> Service manager. I'm running with kscreen2
unchecked as that causes other problems with resizing the session window).
Does kde try to set the keyboard type and layout on login?
If so, how can I stop it doing that and accept whatever was set before
startkde was run?
Hi there
I have simmilar Problems. After logging in with x2go I always have us
keyboard. Different from my direct login I have the IBus keyboard icon
im ny system tray. this only shows us keyboard as available. After
adding german keyboard to this list my x2go client settings are used as
well. To add german keyboard I had to activate "customized active input
method" on the "input method" tab first. May be you have to add all your
needed keyboard layout to this list and after this your remote selection
is used.
I am not realy sure what this IBus thing is all about and why I have to
configure it with x2go but not with local login.
regards
Martin
Thanks
Roderick Johnstone
Martin
Thanks for your post. I just got to finding that IBus is implicated too,
just a few minutes ago (at least when I started typing this)!
For me it was a little more complicated though...
First I found that a console session in KDE was giving me a US keyboard
layout too.
I do a kickstart install and had a, what turns out to be, legacy command
in there:
keyboard uk
This worked in the F20 beta but fails to work in the released version.
When I checked the Anaconda/kickstart docs it seems that the kickstart
'keyboard' command was enhanced for F18.
I then looked at my F18 installer written anaconda-ks.cfg file I found
that it had:
# Keyboard layouts
# old format: keyboard uk
# new format:
keyboard --vckeymap=uk --xlayouts='gb'
so I changed my F20 kickstart file to have:
keyboard --vckeymap=uk --xlayouts='gb'
With a new install I then found that the console session had the correct
gb keyboard mapping.
Now on to x2go...
By setting keyboard layout and keyboard model alternately to (gb,
pc105/gb) and then (fr, pc105/fr) I found that the requested keyboard
layout was set but only on the first login via x2go. I found I could
reset the keyboard if I removed the ~/.config directory. Later I found
that all that was needed was to remove the ~/.config/dconf directory.
Console sessions were always right now, no matter what.
As you found out too, in the x2go session the IBus keyboard icon was
displayed in the system tray. I then found that by removing all the
ibus* packages the keyboard layout was set correctly in the x2go session
every time.
Like you, I'm not too sure what IBus is doing but it seems to remember
the first keyboard layout used in the x2go sessions and thereafter
always use that for x2go sessions, but not console sessions.
I hope that this all remains stable for me now. My experience with the
x2go keyboard layout setting is that just as I think I've got it
working, it stops working!
Roderick
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
