You are not logged in.
Pages: 1
Hi guys,
I don't usually post problems, but I've been struggling with this for weeks, and I've tried everything I can.
I originally wanted to make a custom keyboard layout, which worked for a while, but then it suddenly stopped working. I got rid of all my custom settings, trying to get a normal US keyboard layout back, but it seems to be stuck on UK.
All my settings say US, even the GNOME settings show that it's set to US and the visual keyboard is US, but when I actually type, everything appears assuming a UK layout.
If I run setxkbmap from Terminal, the keyboard layout changes...but only until I switch away from Terminal. Switching to Chrome and then back to Terminal reverts the layout back to UK.
>gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'us')]>localectl status
System Locale: LANG=en_GB.UTF-8
VC Keymap: us
X11 Layout: us
X11 Model: pc105+inet
X11 Options: terminate:ctrl_alt_bksp>cat /etc/vconsole.conf
KEYMAP=us>cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# instruct systemd-localed to update it.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "us"
Option "XkbModel" "pc105+inet"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection>cat /etc/locale.gen | grep -v \#
en_GB.UTF-8 UTF-8>cat /etc/locale.conf
LANG=en_GB.UTF-8The system locale is set to en_GB, but this really shouldn't have any impact on the keyboard layout.
Does anyone have any idea what I could try?
Thanks!
Last edited by somody (2018-11-28 14:24:09)
Offline
Maybe we can narrow down where things go wrong.
Boot to multi-user.target , login to console .
what keymap is used ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Running gnome on wayland?
loginctl session-statusOffline
Maybe we can narrow down where things go wrong.
Boot to multi-user.target , login to console .
what keymap is used ?
Good idea! At that console, the keyboard layout is US. If I'm in GNOME and I use Ctrl+Alt+F2 and log in there, it's also US.
Offline
Running gnome on wayland?
loginctl session-status
>loginctl session-status
2 - somody (1000)
Since: Tue 2018-11-27 20:46:13 CET; 37s ago
Leader: 864 (gdm-session-wor)
Seat: seat0; vc2
TTY: tty2
Service: gdm-password; type x11; class user
State: active
Unit: session-2.scope
├─ 864 gdm-session-worker [pam/gdm-password]
├─ 879 /usr/bin/gnome-keyring-daemon --daemonize --login
├─ 885 /usr/lib/gdm-x-session --run-script /usr/bin/gnome-session
├─ 887 /usr/lib/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none ->
├─ 904 /usr/lib/gnome-session-binary
├─ 967 /usr/bin/gnome-shell
├─1093 /usr/lib/gsd-power
├─1094 /usr/lib/gsd-print-notifications
├─1096 /usr/lib/gsd-rfkill
├─1097 /usr/lib/gsd-screensaver-proxy
├─1098 /usr/lib/gsd-sharing
├─1099 /usr/lib/gsd-sound
├─1100 /usr/lib/gsd-xsettings
├─1103 /usr/lib/gsd-wacom
├─1107 /usr/lib/gsd-smartcard
├─1117 /usr/lib/gsd-a11y-settings
├─1120 /usr/lib/gsd-clipboard
├─1122 /usr/lib/gsd-color
├─1128 /usr/lib/gsd-datetime
├─1131 /usr/lib/gsd-housekeeping
├─1135 /usr/lib/gsd-keyboard
├─1137 /usr/lib/gsd-media-keys
├─1138 /usr/lib/gsd-mouse
├─1165 /usr/lib/gsd-printer
├─1188 /usr/lib/tracker-miner-fs
├─1191 /usr/lib/gsd-disk-utility-notify
├─1194 /usr/bin/gnome-software --gapplication-service
├─1200 /usr/lib/tracker-miner-apps
├─1202 /usr/lib/evolution-data-server/evolution-alarm-notify
├─1312 fcitx
├─1317 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --config-file /usr/share/fcitx>
├─1321 /usr/bin/fcitx-dbus-watcher unix:abstract=/tmp/dbus-xHUI39SiuJ,guid=be1db6ba520e5c7a89b7f4315bfd9f0>
...
...Offline
Nope, X11.
Random guess: fcitx?
Offline
Nope, X11.
Random guess: fcitx?
I do not think so because it is a different scope.
Having a very cursory glance over the source code of the
gsd-keyboardutility that is listed in the
loginctl session-status i see that it does take some assumptions about what keyboard layout is used. Does your problem persist in different desktop environments?
OK, you state, that it is fine in other environments than GNOME, for example the VT. So this could make a stronger case for GNOME specific behaviour? Try a different DE?
Last edited by randomguy (2018-11-28 02:09:20)
Offline
Nope, X11.
Random guess: fcitx?
Wow, I just removed everything related to it (libgooglepinyin fcitx-googlepinyin fcitx-gtk2 fcitx-gtk3 fcitx-qt4 fcitx-configtool fcitx-qt5 fcitx) and rebooted and it's working perfectly now.
Thanks a lot for the help! I'm embarrassed it was so simple...
Offline
Cool.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Fwwi, I'm not sure why you'd need fcitx in Germany, but you can probably fcitx-configure the problem away and keep using it.
Offline
Pages: 1