|
Bugzilla – Full Text Bug Listing |
| Summary: | Local keyboard language sometimes not enabled after startup and Gnome login | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Terje J. Hanssen <terjejhanssen> |
| Component: | Basesystem | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bwiedemann, chcao, crrodriguez, dimstar, fcrozat, forgotten_65GhXku982, forgotten_ZZuOragHZ_, jengelh, mcatanzaro, systemd-maintainers, terjejhanssen, zaitor |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Gnome menu shows No
Gnome menu displays "correctly" Norwegian keyboard layout, even that the keyboard actually works using wrong English layout |
||
Created attachment 600816 [details]
Gnome menu displays "correctly" Norwegian keyboard layout, even that the keyboard actually works using wrong English layout
Hei Terje
Next reboot -> try alt+f1 -> TTY terminal:
Is the keyboardlayout correct there?
Or do you have a english keyboard?
I suspect we have some kind of race here
embla:~ # journalctl -b | grep systemd-vconsole-setup
sep. 25 19:12:40 embla systemd-vconsole-setup[168]: /usr/bin/loadkeys failed with error code 1.
sep. 25 19:12:40 embla systemd-vconsole-setup[168]: cannot open file no-latin1
embla:~ # systemctl status systemd-vconsole-setup.service
systemd-vconsole-setup.service - Setup Virtual Console
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
Active: active (exited) since to. 2014-09-25 19:12:40 CEST; 42min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Main PID: 168 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-vconsole-setup.service
sep. 25 19:12:40 embla systemd-vconsole-setup[168]: cannot open file no-latin1
I suspect the issue here is not GNOME.
Hei Bjørn, Just to clarify; Do you mean when I recognize English layout keyboard even though the Gnome applet tells Norwegian keyboard, I should switch to console mode using Ctrl-Alt-F1, login there and test the keyboard layout setting? If so, I have to wait until next time I recognize this happends. Yes and no - I want you to do the ctrl+alt+f1 after any reboot - you don't even have to log in - just press æøå in the "username" and you will see if you have norwegian or english keyboard. on a current upgraded install from 13.1 to factory + gnome:next i see a "permanent" fail with regards to keyboard layout, permanent fix for me as of now was to add vconsole.keymap=no-latin1 to bootline Note that when I say permanent, i mean in tty - keyboardlayout works just fine in gnome even without the "fix" I tested now after reboot and got correctly Norwegian characters æøå ÆØÅ, and this is mostly also the case on my other machines. This is on Factory upgraded from 13.1 or Tumbleweed lsb_release -a LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch Distributor ID: openSUSE project Description: openSUSE 20140918 (Harlequin) (x86_64) Release: 20140918 Codename: Harlequin I'm going to do a new 13.2 beta1 installation on this workstation, but will test also on another machines, especially when keyboard layouts conflict. On two machines after a new installation to 13.2 Beta1 and next upgrade to Factory: 1) In console tty mode (Ctrl+Alt+F1) Permanent wrong English keyboard layout (should be Norwegian as installed) 2) In Gnome gui mode Norwegian keyboard layout, mostly, but as reported initially, it happends sometimes to English keyboard layout, even that Gnome applet menu shows Norwegian. I also discovered after the new installation/upgrade that "Show keyboard layout" on at Gnome keyboard applet menu failed (gkbd-keyoard-display). After I added the package libgnomekbd, this function now works again. Hi Terje, thanks for the info Could you verify if you have the same error as me about vconsole in journald logs? Here is the output I get:
# journalctl -b | grep systemd-vconsole-setup
Sep 30 15:34:58 linux-6pfs systemd-vconsole-setup[135]: cannot open file no-latin1
# systemctl status systemd-vconsole-setup.service
systemd-vconsole-setup.service - Setup Virtual Console
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
Active: active (exited) since Tue 2014-09-30 15:34:58 CEST; 8min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Main PID: 135 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-vconsole-setup.service
Sep 30 15:34:58 linux-6pfs systemd-vconsole-setup[135]: cannot open file no-latin1
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I also tried to put vconsole.keymap=no-latin1 on the boot line (if I made it right?), but did still get English characters in console tty mode. Here is another output from the /var/log/journal/xxxd/*
# strings * | grep vconsole
SYSLOG_IDENTIFIER=systemd-vconsole-setup
_SYSTEMD_UNIT=systemd-vconsole-setup.service
MESSAGE=/etc/vconsole.conf available
MESSAGE=Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.2-1.gdcee397-desktop root=UUID=1b37dae9-501e-47fc-940e-5f5149200657 resume=/dev/disk/by-uuid/975c3c3e-1227-4950-8ee0-f35c02c58526 splash=silent quiet showopts vconsole.keymap=no-latin1
MESSAGE=Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.2-1.gdcee397-desktop root=UUID=1b37dae9-501e-47fc-940e-5f5149200657 resume=/dev/disk/by-uuid/975c3c3e-1227-4950-8ee0-f35c02c58526 splash=silent quiet showopts vconsole.keymap=no-latin1
Frederic: You are kind of the resident systemd guru: Do you have an idea whats going on here? @ Terje: thats odd that it did not work as it does here. When you are in tty - could you try doing a systemctl restart systemd-vconsole-setup.service and see if you get norwegian keyboardlayout then. And are you sure it's english and not dvorak? aka are your keys qwerty on the top line? (In reply to Bjørn Lie from comment #9) > Frederic: You are kind of the resident systemd guru: Do you have an idea > whats going on here? console settings and GNOME settings are orthogonal. check those settings using localectl output. Based on that, you'll know exactly what are the defaults for console and for X11. I was thinking about systemd-vconsole-setup[135]: cannot open file no-latin1 even when it's there. (In reply to Bjørn Lie from comment #9) > @ Terje: thats odd that it did not work as it does here. > > When you are in tty - could you try doing a > > systemctl restart systemd-vconsole-setup.service > > and see if you get norwegian keyboardlayout then. > Yes, that command works for root, fail with no access for normal user. > And are you sure it's english and not dvorak? > > aka are your keys qwerty on the top line? My keyboad is querty on the top-line (below the function row). Looks like a standard 102 key IBM keyboard (Model M) with Norwegian layout. http://en.wikipedia.org/wiki/File:102-key_Model_M.jpg Lastly I also found the needed "|" (pipe) on the English layout (mode) as "*" (star) on the Norwegian key to the left of the Return key. (In reply to Bjørn Lie from comment #11) > I was thinking about > > systemd-vconsole-setup[135]: cannot open file no-latin1 > > even when it's there. This is related to dracut (reported as bnc#897972, sorry a SLES12 bug not publicly visible) and a fix is being worked on. (In reply to Terje J. Hanssen from comment #12) > (In reply to Bjørn Lie from comment #9) > > > @ Terje: thats odd that it did not work as it does here. > > > > When you are in tty - could you try doing a > > > > systemctl restart systemd-vconsole-setup.service > > > > and see if you get norwegian keyboardlayout then. > > > > Yes, that command works for root, fail with no access for normal user. This is normal, loadkeys (used by systemd-vconsole-setup.service) is only possible for root. (In reply to Frederic Crozat from comment #13) please use lsinitrd /boot/initrd | grep no-latin1 to check if the font is really in the initrd in the correct path (guess: it should be below usr/share/kbd/consolefonts/) (In reply to Dr. Werner Fink from comment #14) > (In reply to Frederic Crozat from comment #13) > > please use > > lsinitrd /boot/initrd | grep no-latin1 > > to check if the font is really in the initrd in the correct path (guess: it > should be below usr/share/kbd/consolefonts/) It is here, but this is an upgraded system + I might have been fixing it up when I first noticed the issue.. -rw-r--r-- 1 root root 4933 Sep 17 22:16 usr/share/kbd/keymaps/i386/qwerty/no-latin1.map (In reply to Bjørn Lie from comment #15) > (In reply to Dr. Werner Fink from comment #14) > > (In reply to Frederic Crozat from comment #13) > > # lsinitrd /boot/initrd | grep no-latin1 cat: write error: Broken pipe -rw-r--r-- 1 root root 1714 Sep 17 22:16 usr/share/kbd/keymaps/i386/qwerty/no-latin1.doc # ls -1 /usr/share/kbd/keymaps/i386/qwerty/no* /usr/share/kbd/keymaps/i386/qwerty/no-latin1.doc /usr/share/kbd/keymaps/i386/qwerty/no-latin1.map.gz /usr/share/kbd/keymaps/i386/qwerty/no.map.gz Btw: What is wrong with UTF-8? Does this not work with Norwegian keyboard? Please configure the stuff with YaST2, that is Norwegian keyboard and Norwegian language together a second language US English and avoid GNOME. Then run mkinitrd to see which font is then enabled in the initrd. To update and sum up a little bit, I have now also installed fresh new 13.2 Beta1 on three different workstations and laptop, and next upgraded them to Factory. As always previously, I select Norwegian as primary language and added English (US) as secondary language, Gnome as default desktop and added the KDE software pattern, all during the initial installation. For Factory this cause "permanently" wrong English keyboard layout at Console login (ctrl+alt+f1) and correct Norwegian kb layout at Gnome desktop session gui and also for su to root in Gnome terminals. To add confusing, a seldom time it happends randomly to be Norwegian characters at Console login or English in Gnome, the latter also while the Gnome Kb applet shows it should be Norwegian. The Norwegian keyboard layout has worked and works flawlessly for both Console and Gnome sessions on 13.1/Tumbleweed on the same hardware. As I still have both 13.1/Tw and 13.2 in dual-boot on the same machines, I have now compared the content of configuration files as follows (here with stripped away most comments). As seen below, there is one differense between the two /etc/sysconfig/keyoard files (13.1) KEYTABLE="no-latin1.map.gz" (13.2) KEYTABLE="" Empty is the default (us). I added "no-latin1.map.gz" also to the 13.2 file using the YaST2 /etc/sysconfig editor, rebooted but with no change. Still English kb at Console login. Isn't it really not reconfigured, yet? /etc/sysconfig/keyboard (13.1) # Keyboard settings for the text console # # Keyboard mapping # (/usr/share/kbd/keymaps/) # e.g. KEYTABLE="de-latin1-nodeadkeys", "us" or empty for US settings # KEYTABLE="no-latin1.map.gz" KBD_DELAY="" KBD_RATE="" KBD_NUMLOCK="bios" KBD_SCRLOCK="no" KBD_CAPSLOCK="no" KBD_DISABLE_CAPS_LOCK="no" KBD_TTY="" COMPOSETABLE="clear latin1.add" YAST_KEYBOARD="norwegian,pc104" /etc/sysconfig/keyboard (13.2) # Keyboard settings for the text console # # Keyboard mapping # (/usr/share/kbd/keymaps/) # e.g. KEYTABLE="de-latin1-nodeadkeys", "us" or empty for US settings # KEYTABLE="" KBD_DELAY="" KBD_RATE="" KBD_NUMLOCK="bios" KBD_SCRLOCK="no" KBD_CAPSLOCK="no" KBD_DISABLE_CAPS_LOCK="no" KBD_TTY="" COMPOSETABLE="clear latin1.add" # The YaST-internal identifier of the attached keyboard. # YAST_KEYBOARD="norwegian,pc104" /etc/sysconfig/console (13.1 & 13.2) CONSOLE_FONT="lat1-16.psfu" CONSOLE_UNICODEMAP="" CONSOLE_SCREENMAP="none" CONSOLE_MAGIC="(B" CONSOLE_ENCODING="UTF-8" /etc/sysconfig/language (13.1 & 13.2) INPUT_METHOD="" RC_LANG="nb_NO.UTF-8" RC_LC_ALL="" RC_LC_MESSAGES="" RC_LC_CTYPE="" RC_LC_COLLATE="" RC_LC_TIME="" RC_LC_NUMERIC="" RC_LC_MONETARY="" RC_LC_PAPER="" ROOT_USES_LANG="ctype" AUTO_DETECT_UTF8="no" INSTALLED_LANGUAGES="en_GB,nb_NO" as a workaround, you could try to call localectl to see what it thinks and maybe even update settings. I'll do that, but I need the exact command how to do it ;) I can add that when I upgraded one machine from 13.1 to Factory using 'zypper dup', the console kb layout was kept correct. It looks to be related to new Factory installations. Hi having the same problem. But A workaround is to go into yast2 -> hardware -> System Keyboard Layout -> Danish then update system. Then back to Norwegian and it then works. mortenb@mortenblap:~> locale LANG=nb_NO.UTF-8 LC_CTYPE="nb_NO.UTF-8" LC_NUMERIC="nb_NO.UTF-8" LC_TIME="nb_NO.UTF-8" LC_COLLATE="nb_NO.UTF-8" LC_MONETARY="nb_NO.UTF-8" LC_MESSAGES="nb_NO.UTF-8" LC_PAPER="nb_NO.UTF-8" LC_NAME="nb_NO.UTF-8" LC_ADDRESS="nb_NO.UTF-8" LC_TELEPHONE="nb_NO.UTF-8" LC_MEASUREMENT="nb_NO.UTF-8" LC_IDENTIFICATION="nb_NO.UTF-8" LC_ALL= mortenb@mortenblap:~> æøå language/keyboard/locale probably got corrupted during update. but this is now working fine for me. Now quite a few months later, and the "situation" is a lot better. Still I have some issues, but at least Norwegian keyboard layout is applied, even if again borked. Moving bug to Base:System / systemd-maintainers cause I really do not see this a gnome bug. Granted I'm not sure if this is really a systemd bug, it might as well be hidden some where else in the base packages, but at least since systemd 219 I have lost the "representations" of nordic letters in TTY, and let me state that the original bug was "fixed", so something changed around 2.19 Systemd-maintainers: Please let me know what debug info you need (In comment to Bjørn Lie from comment #22) > Bjørn, just to inform you that it's a long time since I saw this issue, and I had almost forgotten this bug. At least it happends so seldom that it doesn't bother me longer, and I don't remember when it disappeared. I update my system regulary, and currently I'm running the latest openSUSE 13.2 (3.16.7-7-desktop) and Gnome 3.14.3 on my machines. By the way, I tested your journalctl and systemctl commands again in console mode, and the last part of the output was: systemd-vconsole-setup: mapscrn: cannot open map file _trivial_ Just for your information. (In reply to Bjørn Lie from comment #22) I'd like to know wyh do you think this is a systemd bug? For no better reason than bug returning at the same time as we went to systemd 219. Now systemd might very well be just the messenger, but I have this in my logs now embla:~ # journalctl -b | grep systemd-vconsole Apr 14 14:41:19 embla systemd-vconsole-setup[141]: /usr/bin/loadkeys failed with error code 1. Apr 14 14:41:19 embla systemd-vconsole-setup[141]: cannot open file no-latin1 Apr 14 14:41:20 embla unknown[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 14 14:41:20 embla kernel: audit: type=1130 audit(1429015280.350:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Apr 14 14:41:25 embla systemd-vconsole-setup[415]: /usr/bin/loadkeys failed with error code 1. and the fun embla:~ # lsinitrd /boot/initrd | grep no-latin1 -rw-r--r-- 1 root root 1714 Apr 10 10:11 usr/share/kbd/keymaps/i386/qwerty/no-latin1.doc Returned to my initrid. I'm pretty positive that GNOME has got nothing to do with whats in the initrid I can add that doing rm /usr/share/kbd/keymaps/i386/qwerty/no.map.gz /usr/share/kbd/keymaps/i386/qwerty/old.no.map.gz and running mkinitrd fixes the issue yet again (In reply to Bjørn Lie from comment #25) > For no better reason than bug returning at the same time as we went to > systemd 219 I doubt that this one is usable for 13.1 ... also adding the submitters of 219 to carbon copy (In reply to Bjørn Lie from comment #26) > I can add that doing > > rm /usr/share/kbd/keymaps/i386/qwerty/no.map.gz /usr/share/kbd/keymaps/i386/qwerty/old.no.map.gz > > and running mkinitrd fixes the issue yet again sounds more like an mkinitrd problem ... or systemd 219 is missing yet an other patch from Base:System:Legacy/systemd which is systemd-210 which is kbd-model-map.patch and/or the file /usr/share/kbd/keymaps/i386/qwerty/no.map.gz should not be used which could be a problem of the package kbd and/or mkinitrd. AFAICS from Base:System/systemd as well as from openSUSE:Factory/systemd the patch kbd-model-map.patch *is* included. Therefore this is not a bug of systemd even if the systemd tools report the error. Hi Stanislav, would you please help to have a look at this issue? I'm not sure whether it is right to assign it to you, please feel free to reassign, thank you. The vconsole/kbd issue is exactly the same as the bug 932981, just the map is different. But it is present as well. I suspect that it is a race problem of dracut (bug 904214), but I have no proof yet, and no input from dracut developers. I see no problem in kbd itself. The problem in GNOME is different, and it has nothing to do with kbd. I will leave this bug for the solution of the GNOME problem reported initially and reassigning it to the GNOME team. Please follow bug 932981 for the problem of the console. This problem surely looks as a race, and it can be reproduced only on some machines, and only sometimes. Maybe my issue is related. I run latest updated 42.2 I have been using Plasma 5 until a few days ago and decided to test gnome after reading a positive report. Gnome seems OK, but I am annoyed with the keyboard behavior after login. After login to gnome, gnome classic and SLE Classic I have always US-keyboard, but correct SE-keyboard after login Plasma, Plasma 5 and IceWM. The "funny" thing is that I can resolve the issue by starting Yast2-keyboard and canceling it without doing anything. This behavior is 100%. I log out and in to gnome and can get same result every time. Console 1-5(=tty1-5) have correct SE-keyboard all the time. This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |
Created attachment 600815 [details] Gnome menu shows No User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Running current openSUSE Tumbleweed and Gnome 3.12.2, installed with Norwegian as primary language and English as secundary language. The "No" is always shown correctly on the Gnome top-right bar after startup and login, but sometimes the keyboard actually works with English layout instead, even that also the Gnome keyboard layout tells Norwegian in these cases. Two screenshots are attached here from the Gnome menu. Tried also some forum suggested commands to query the keyboard layout as follows: terje@linux-ntag:~> setxkbmap -query | grep layout layout: no,us terje@linux-ntag:~> setxkbmap -query rules: evdev model: pc104 layout: no,us variant: , terje@linux-ntag:~> (xset -q|grep LED| awk '{ print $10 }') 00001002 terje@linux-ntag:~> xset -q | grep -A 0 'LED' | cut -c59-67 00001002 terje@linux-ntag:~> setxkbmap -print | grep xkb_symbols xkb_symbols { include "pc+no+us:2+inet(evdev)+terminate(ctrl_alt_bksp)" }; terje@linux-ntag:~> setxkbmap -v | awk -F "+" '/symbols/ {print $2}' no A workaround that fix this is to just select English and next Norwegian again on the Gnome top menu, and then the keyboard works correctly with Norwegian layout. Reproducible: Sometimes Steps to Reproduce: 1. Restart (hot or cold) and login to Gnome 2. 3. Actual Results: As described above Expected Results: The keyboard should actually work with displayed Norwegian layaout.