Bugzilla – Bug 433338
No Key repeat possible
Last modified: 2021-03-09 11:59:08 UTC
In YaST2 it is not longer possible to repeat a key. It is only "ONE" Keystroke possible ? Is this a feature ? (German Keyboard)
Could you, please, elaborate how to reproduce the issue?
When I write my name in User "Gönther J. Niederwimmer" ans I have to go to th "ö" the I have hit the back (Curser) butten 21 x again ? When I like to add a repository and have a wrong Url. openSUSE/factory/repo/oss and like delete / change a part from the wrong Url, I have to hit the back Key 16x again to change "F" in factory usw. I hope this helps ;).
Günther, please look at bug #371756. Is this the same problem?
I really don't know what the UI maintainers could possibly do about this. This is a problem in X11 or in the kernel.
IIRC YaST disables keyboard repeat by intention. This has been introduced not long ago (11.0 or 10.x). I forgot the reason. Arvin might still remember.
Hello Stefan, #3 Yes it is the same Bug 371756 :(, I found it and forget it in 11.0, now in 11.1 i will report ;)
See bug #376945.
Uh - INVALID? To clarify: We intentionally disrupt usability for every user because of one installation scenario that can't get this right - a XEN installation? No. I can't believe this.
Surely there is a way to find out if we really are in that exotic scenario that has problems with keyboard autorepeat. If we cripple the keyboard there - too bad, but OK, if there is no other solution, so be it. But we cannot cripple basic functionality (such as keyboard usability) for every user because of that. We went through great lengths to improve usability. We should not simply throw away all that work with something like this.
Günther, I'll need your YaST logs, please.
Created attachment 244270 [details] You need the Yast2 Logs ;)
Once the X server was broken and a workaround was required, see bug #346186.
Source code: if (! UI::TextMode() && SCR::Read (.probe.xen) == true) { y2milestone ("XEN in X detected: running xset"); WFM::Execute (.local.bash, "xset r off; xset m 1"); } Logs: installation/misc.ycp:247 UI::TextMode(): Please check if this is really necessary! [agent-probe] HwProbe.cc(checkPath):371 Unrecognized path '.xen' (and nothing more) I don't think Installation is responsible for non-functional key-repeat.
The only thing I know is that installation handles the DPMS with xset (a new feature in 11.1): DPMS off: /usr/bin/xset dpms 0 0 0; /usr/bin/xset -dpms; /usr/bin/xset s 0 0 DPMS on: /usr/bin/xset dpms 1200 1800 2400; /usr/bin/xset +dpms; /usr/bin/xset s default Is it possible that it might break key-repeating?
It shouldn't, but better verify.
Misc.ycp:192 .sysconfig.keyboard.KBD_RATE: '' Misc.ycp:192 .sysconfig.keyboard.KBD_DELAY: '' Keyboard.ycp:271 rate: delay: numlock:bios capslock:no scrlock:no disclock:no Keyboard.ycp:726 Probed keyboard: <[$["bus":"USB", "bus_hwcfg":"usb", "class_id":264, "dev_name":"/dev/input/event0", "dev_names":["/dev/input/event0"], "dev_num":$["major":13, "minor":64, "range":1, "type":"c"], "device":"Microsoft Wireless Optical Desktop256 2.10", "device_id":196765, "driver":"usbhid", "driver_module":"usbhid", "hotplug":"usb", "keyboard":[$["xkbmodel":"pc104", "xkbrules":"xfree86"]], "modalias":"usb:v045Ep009Dd0041dc00dsc00dp00ic03isc01ip01", "model":"Microsoft Wireless Optical Desktop256 2.10", "old_unique_key":"a+h6.Gxk0sUSKQS5", "parent_unique_key":"k4bc.v+N+B0xY+P6", "resource":$["baud":[$["speed":1500000]]], "rev":"0.41", "sub_class_id":0, "sysfs_bus_id":"1-1:1.0", "sysfs_id":"/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0", "udi":"/org/freedesktop/Hal/devices/usb_device_45e_9d_noserial_if0_logicaldev_input", "unique_key":"ADDn.MQt3KFVjkFB", "vendor":"Microsoft Corp.", "vendor_id":197726]]> Keyboard.ycp:751 Xkblayout: <> Keyboard.ycp:512 Setting keyboard to: <german> ShellCommand.cc(shellcommand):78 could not open file: /usr/share/sax/sysp/maps/Keyboard.map at /usr/sbin/xkbctrl line 116. Keyboard.ycp:391 Parsing file '/tmp/YaST2-03816-AcZQLg/xkbctrl.out' failed Keyboard.ycp:534 x11data=nil Keyboard.ycp:1127 loadkeys command: </bin/loadkeys de-latin1-nodeadkeys.map.gz ; dumpkeys -c iso-8859-15 | loadkeys -u> after packages are installed ... Keyboard.ycp:1057 No probed keyboards. Not unconfiguring any keyboards Keyboard.ycp:1069 Marked keyboard <ADDn.MQt3KFVjkFB> as configured Keyboard.ycp:1074 Marked keyboard <ADDn.MQt3KFVjkFB> as needed Keyboard.ycp:1088 Saved data for keyboard: <german> ... Jiri, is it possible that missing /usr/share/sax/sysp/maps/Keyboard.map file could cause this? How is the "Microsoft Wireless Optical Desktop256 2.10" keyboard supported? Honestly, I don't remember if this is a generic issue in installation (does repeating work with other setup?) but if it isn't generic, it can't be caused by /see comment #18/.
(In reply to comment #20 from Lukas Ocilka) > Jiri, is it possible that missing /usr/share/sax/sysp/maps/Keyboard.map file > could cause this? I'd say it is possible. Missing /usr/share/sax/sysp/maps/Keyboard.map means that setxkbmap is not called at all which means at least some thing is not correctly initialized... well, some thing - the German keyboard should not work at all in X11... Anyway, the file _is_ in beta2 together with /usr/sbin/xkbctrl. The logfile seems to be from beta1. Guenther, please confirm and if it really were beta1, retest with beta2.
It would also help to test it with the default en_US keyboard...
#21 I do start a new fresh installation with a Beta 2 DVD X86_64 and the Problem exist! When I add a nfs Repository it is not possible, a key repeat usw.
Would you be so kind and test the Beta2 with the default en_US language and en_US keyboard? Anyway, it's always nice if you attach YaST logs while testing with different media. Thanks
same result with default en_US language, No key repeat :(. I tested it, in the Network Setup Window. YaST logs: I can't install a fresh Beta 2 on this system! I can only do a upgrade from 11.0 to 11.1 Beta2, there is a Bug in YaST2 Storage, that tell me, to small disk space (splitted path) and I found no way to say GO :(.
Günther, there's no need to proceed the installation, just start the installation program from media. When it shows the Welcome screen, click to the license field and hit Ctrl+Alt+Shift+x - that will open up an xterm (Ctrl+D or `logout` would close it). You can check the key-repeat in that xterm. Anyway, I've tried to switch to de_DE keyboard layout there and repeating worked (in add-ons, for instance). It seems we might need these files from the installation system: * /etc/X11/xorg.conf * /var/log/Xorg.0.log
In the xterm no key repeat is possible.
Created attachment 244513 [details] The Logs from the xterm Test
Not a generic installation issue (the same behavior works well on our testing systems) -> X, keyboard drivers, ... ?
I can reproduce the issue with de_DE on x86_64. de_DE on i386 seems to work fine. I'll test more configurations, but it really doesn't look as YaST issue to me. Stefan, is there any specific info you could use?
I can't tell you who runs "xset r off" during installation. keyboard repeat works fine after installation. I can't help here.
reopening
Günther, it seems we'll have to find out together ;) Please run the installation with Y2DEBUG=1 on commandline when starting the "Installation" image from media and attach the YaST logs. Thanks.
Looks like it is not deterministic :-( My several attempts with y2debug failed to reproduce the issue. Anyway, (In reply to comment #31 from Stefan Dirsch) > I can't tell you who runs "xset r off" during installation. keyboard repeat > works fine after installation. I can't help here. this is problematic. YaST doesn't call "xset r off" and the repeat is missing just in the next dialog after the welcome one. YaST called only setxkbmap between those dialogs, so I thought this one could be guilty...
setxkbmap shouldn't change the state of the autorepeat. If it does I need more details how to reproduce the issue, like current keyboard settting ("setxkbmap -print"/"xset q") and setxkbmap command with all options, which breaks it.
Created attachment 244544 [details] setxkmap -print The command called from YaST was "/usr/bin/setxkbmap -variant nodeadkeys -layout de -model microsoftpro"
Created attachment 244545 [details] xset -q
# setxkbmap -print xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwertz)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+de+inet(microsoftpro)" }; xkb_geometry { include "microsoft(natural)" }; }; # xset q|grep -A3 auto auto repeat: on key click percent: 0 LED mask: 00000000 auto repeat delay: 250 repeat rate: 30 auto repeating keys: 00feffffdffffbbf fadfffffffdfe5ef ffffffffffffffff ffffffffffffffff # /usr/bin/setxkbmap -variant nodeadkeys -layout de -model microsoftpro # xset q|grep -A3 auto auto repeat: on key click percent: 0 LED mask: 00000000 auto repeat delay: 250 repeat rate: 30 auto repeating keys: 00feffffdffffbbf fadfffffffdfe5ef ffffffffffffffff ffffffffffffffff ==> WORKSFORME
(In reply to comment #40 from Stefan Dirsch) > ==> WORKSFORME That's really possible. As I already wrote, for me it doesn't happen every time.
Ok. Since investigation is apparently more or less impossible, I suggest to close it as WORSFORME or WONTFIX.
What about a fallback in installation, e.g., calling `xset r` explicitly?
We already have that in the startup scripts, see bug #346186.
With y2debug failed to reproduce the Problem :(. I have a Problem to log this on a USB Stick :( Now it is OK, the Logs are attached.
Created attachment 244840 [details] The DEBUG YaST Log
By the way, in SLES 11 Beta2 (i386) when I open an xterm at the end of the first stage (just before the reboot), xset -q shows that autorepeat is on but it doesn't work. Calling xset -r fixes that. Command xset -q then shows the very same output but autorepeat works. That doesn't look like a YaST bug and it's hard to make a workaround anywhere :(
Xorg.0.log: (EE) Failed to load module "glx" (module does not exist, 0) (EE) Failed to load module "freetype" (module does not exist, 0) (EE) Failed to load module "record" (module does not exist, 0) (EE) Failed to load module "dri" (module does not exist, 0)
(In reply to comment #17 from Lukas Ocilka) > Source code: > if (! UI::TextMode() && SCR::Read (.probe.xen) == true) { > y2milestone ("XEN in X detected: running xset"); > WFM::Execute (.local.bash, "xset r off; xset m 1"); > } This place currently contains if (not XEN) { Run: `xset r on` } yast2-installation-2.17.20
(In reply to comment #48 from Lukas Ocilka) > Xorg.0.log: > (EE) Failed to load module "glx" (module does not exist, 0) > (EE) Failed to load module "freetype" (module does not exist, 0) > (EE) Failed to load module "record" (module does not exist, 0) > (EE) Failed to load module "dri" (module does not exist, 0) Modules are missing in instsys. Currently we don't need OpenGL support and support for serverside fontrendering during installation. Not talking about record extension for makro recorders at all.