Quoting Colin Watson ([EMAIL PROTECTED]): > I strongly agree, and to be honest I have real trouble seeing > Christian's argument here (well, at least not post-lenny). Putting a > fatal signal on a surprising key that people might quite reasonably > expect from the engraving to have completely different semantics is not > compatibility worth preserving.
I finally had a closer look here and I can propose the attached patch to console-data so that PrtScr does nothing. This is untested stuff. Just wild guess as I'm often doing with console-data...
--- keymaps/i386/include/linux-keys-bare.inc 2007-05-08 19:00:08.519961000 +0200 +++ keymaps/i386/include/linux-keys-bare.inc.new 2008-11-29 15:59:47.792370754 +0100 @@ -148,7 +148,7 @@ # The three system keys # keycode 84 = Last_Console # Alt+SysRq/PrintScrn -keycode 99 = Control_backslash # SysRq/PrintScrn +keycode 99 = VoidSymbol # SysRq/PrintScrn plain keycode 70 = Scroll_Lock shift keycode 70 = Show_Memory
signature.asc
Description: Digital signature
