This sounds like a regression from the new X11 keyboard input mechanism (it now uses the "evdev" driver instead of the "kbd" driver). But I have no idea if it's X11's, Qt's or kdelibs's fault.
What appears to be happening is that something is enabling the nodeadkeys option somewhere.
This sounds like a regression from the new X11 keyboard input mechanism (it now uses the "evdev" driver instead of the "kbd" driver). But I have no idea if it's X11's, Qt's or kdelibs's fault.
What appears to be happening is that something is enabling the nodeadkeys option somewhere.