On Fri, 27.09.13 11:43, Arthur Taylor (a...@ified.ca) wrote: > > This is an old thread from February. Sorry I can't reply to the original > email. > > Apparently I failed to notice this question. My bad. > > >> Hello systemd developers > >> > >> TL;DR: On a VT which X is running, messing with KDSKBMODE on > >> underneath X at best has no affect and at worst breaks keyboard input > >> badly. In the short term, systemd should stop calling this ioctl > >> because it has no benefit and makes no sense. > > > > It sounds to me we indeed want to set K_UNICODE only if K_OFF (or > > something else like it) is currently not set. > > > > However, before we change this, there's one thing that makes me wonder: > > what does X11 do on shutdown? Does it put the kbd back to K_UNICODE? Or > > back to K_XLATE? > > > > Lennart > > > Provided the behaviour hasn't been changed in the last six months, > Xorg remembers the VT KBMODE on start, set it to whatever it needs > (sometimes more than once :-/ ) and restores it to the value it was on > start upon exit. > > (Of course if X crashes hard it isn't restored, and that is why > SysRq+R was invented.) > >
This has been in place for a while, commited in February, does this leave anything open? http://cgit.freedesktop.org/systemd/systemd/commit/?id=a25d4d0e3ccf0e9bf0b37e5791275fd6ca5eb4ae Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
