[Bug 1200594] New: Certain applications do not honor keyboard layout settings
http://bugzilla.opensuse.org/show_bug.cgi?id=1200594 Bug ID: 1200594 Summary: Certain applications do not honor keyboard layout settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Usability Assignee: screening-team-bugs@suse.de Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since recently, last "zypper dup"?, konsole and lokalize do not honor the layout setting of the keyboard. For Dutch it needs to be US international with dead keys, which is the current setting, but entering, after each other, keys " and e does not produce �, but a simple e. However when entering the same sequence in firefox it does produce an �. I tried also the layout "US international alternative", but with the same result. I can't do any proper translations. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200594 http://bugzilla.opensuse.org/show_bug.cgi?id=1200594#c1 --- Comment #1 from Freek de Kruijf <freek@opensuse.org> --- Also in snapshot 20220614 the same problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200594 http://bugzilla.opensuse.org/show_bug.cgi?id=1200594#c2 --- Comment #2 from Freek de Kruijf <freek@opensuse.org> --- I noticed the following error messages using "journalctl -b -u systemd-udevd.service: jun 23 12:23:35 eiktum systemd[1]: Starting Rule-based Manager for Device Events and Files... jun 23 12:23:35 eiktum systemd[1]: Started Rule-based Manager for Device Events and Files. jun 23 12:23:48 eiktum systemd[1]: Stopping Rule-based Manager for Device Events and Files... jun 23 12:23:48 eiktum systemd[1]: systemd-udevd.service: Deactivated successfully. jun 23 12:23:48 eiktum systemd[1]: Stopped Rule-based Manager for Device Events and Files. jun 23 12:23:48 eiktum systemd[1]: systemd-udevd.service: Consumed 1.552s CPU time. jun 23 12:23:50 eiktum systemd[1]: Starting Rule-based Manager for Device Events and Files... jun 23 12:23:50 eiktum systemd-udevd[589]: Configuration file /etc/udev/rules.d/40-libsane.rules is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 12:23:50 eiktum systemd-udevd[589]: /etc/udev/rules.d/40-libsane.rules:41 Unknown group 'scanner', ignoring jun 23 12:23:50 eiktum systemd-udevd[589]: /etc/udev/rules.d/40-libsane.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring jun 23 12:23:50 eiktum systemd-udevd[589]: /etc/udev/rules.d/40-libsane.rules:26: The line takes no effect any more, dropping jun 23 12:23:51 eiktum systemd-udevd[589]: Configuration file /etc/udev/rules.d/S99-2000S1.rules is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 12:23:51 eiktum systemd-udevd[589]: /etc/udev/rules.d/S99-2000S1.rules:41 Unknown group 'scanner', ignoring jun 23 12:23:51 eiktum systemd-udevd[589]: /etc/udev/rules.d/S99-2000S1.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring jun 23 12:23:51 eiktum systemd-udevd[589]: /etc/udev/rules.d/S99-2000S1.rules:26: The line takes no effect any more, dropping jun 23 12:23:51 eiktum systemd[1]: Started Rule-based Manager for Device Events and Files. jun 23 12:23:51 eiktum mtp-probe[745]: checking bus 7, device 3: "/sys/devices/pci0000:00/0000:00:13.0/usb7/7-5" jun 23 12:23:51 eiktum mtp-probe[745]: bus: 7, device: 3 was not an MTP device jun 23 12:23:51 eiktum mtp-probe[737]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:13.0/usb7/7-4" jun 23 12:23:51 eiktum mtp-probe[737]: bus: 7, device: 2 was not an MTP device jun 23 12:23:51 eiktum mtp-probe[751]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb5/5-2" jun 23 12:23:51 eiktum mtp-probe[751]: bus: 5, device: 2 was not an MTP device jun 23 12:23:51 eiktum mtp-probe[789]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:16.2/usb3/3-1" jun 23 12:23:51 eiktum mtp-probe[789]: bus: 3, device: 2 was not an MTP device jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument jun 23 12:23:51 eiktum systemd-udevd[708]: event5: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument jun 23 12:23:52 eiktum systemd-udevd[707]: Using default interface naming scheme 'v250'. jun 23 12:23:52 eiktum systemd-udevd[701]: Using default interface naming scheme 'v250'. lines 35-74/74 (END) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com