[Bug 1060767] [NEW] Ctrl-PrintScrn and Alt-SysRq are killing the processes in console

[kenorb]

Public bug reported:

Affected keys (on key release time):
- Ctrl+PrintScrn
- Alt+SysRq
- Win+PrintScrn
- and similar like Alt-SysRq + 1-4,7-9,0 (which are ignored by kernel, even these are documented in kernel sysrq.txt)
Exceptions: Alt+SysRq+5,6 (because these are only digits which are handled by kernel)

Steps to reproduce:

1. Change to the text console (Ctrl-Alt-F1).
2. Log in.
3. Run: sleep 100 (or any other command like: cat, head, etc.)
4. Press Ctrl-PrintScrn or Alt-SysRq  (and release the key).
5. Process get killed by: ^\Quit (core dumped)

What I expect is to change my log level  of kernel messages by Alt-SysRq + 0-9 as documented at http://kernel.org/doc/Documentation/sysrq.txt
Or use any other shortcuts using PrintScrn key.

Normally the only keys which should be killing the processes are: Ctrl+4
and Ctrl+\ but not the other.

Originally I've reported it here:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12478
But this doesn't happens on other distributions.
So I was advised to report key mapping issue to my software distribution community.

** Affects: binutils (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: coreutils (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: coreutils (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

- Affected keys (no release time):
+ Affected keys (on key release time):
  - Ctrl+PrintScrn
  - Alt+SysRq
  - Win+PrintScrn
  - and similar like Alt-SysRq + 1-4,7-9,0 (which are ignored by kernel, even these are documented in kernel sysrq.txt)
  Exceptions: Alt+SysRq+5,6 (because these are only digits which are handled by kernel)
  
  Steps to reproduce:
  
  1. Change to the text console (Ctrl-Alt-F1).
  2. Log in.
  3. Run: sleep 100 (or any other command like: cat, head, etc.)
  4. Press Ctrl-PrintScrn or Alt-SysRq  (and release the key).
  5. Process get killed by: ^\Quit (core dumped)
  
  What I expect is to change my log level  of kernel messages by Alt-SysRq + 0-9 as documented at http://kernel.org/doc/Documentation/sysrq.txt
  Or use any other shortcuts using PrintScrn key.
  
  Normally the only keys which should be killing the processes are: Ctrl+4
  and Ctrl+\ but not the other.
  
  Originally I've reported it here:
  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12478
  But this doesn't happens on other distributions.
  So I was advised to report key mapping issue to my software distribution community.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1060767

Title:
  Ctrl-PrintScrn and Alt-SysRq are killing the processes in console

Status in “binutils” package in Ubuntu:
  New
Status in “coreutils” package in Ubuntu:
  New

Bug description:
  Affected keys (on key release time):
  - Ctrl+PrintScrn
  - Alt+SysRq
  - Win+PrintScrn
  - and similar like Alt-SysRq + 1-4,7-9,0 (which are ignored by kernel, even these are documented in kernel sysrq.txt)
  Exceptions: Alt+SysRq+5,6 (because these are only digits which are handled by kernel)

  Steps to reproduce:

  1. Change to the text console (Ctrl-Alt-F1).
  2. Log in.
  3. Run: sleep 100 (or any other command like: cat, head, etc.)
  4. Press Ctrl-PrintScrn or Alt-SysRq  (and release the key).
  5. Process get killed by: ^\Quit (core dumped)

  What I expect is to change my log level  of kernel messages by Alt-SysRq + 0-9 as documented at http://kernel.org/doc/Documentation/sysrq.txt
  Or use any other shortcuts using PrintScrn key.

  Normally the only keys which should be killing the processes are:
  Ctrl+4 and Ctrl+\ but not the other.

  Originally I've reported it here:
  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12478
  But this doesn't happens on other distributions.
  So I was advised to report key mapping issue to my software distribution community.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1060767/+subscriptions