Bug 1322952

Summary: SysRq sequences prone to accidental typing
Product: [Fedora] Fedora Reporter: buzire.rhn
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-31 18:33:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description buzire.rhn 2016-03-31 18:31:00 UTC
Description of problem:
On some physical keyboards (Lenovo), the SysRq is very close to AltGr, which is often mapped as Level3 modifier, used for accents in regular typing. It's very easy to trigger a magic SysRq sequence when slightly missing the Level3 button while typing (with bad consequences).
This forces users to either:
- never use accents
- disable SysRq magic sequences

It's bad news for people who like to debug their systems.

Workaround, but only for X, which makes the system ignore SysRq when AltGr (mod5) is pressed:

$ xmodmap -
remove mod5 = Sys_Req
$

Filed as kernel, because a generic workaround (useful for TTY in addition to X) would be nice (remove AltGr from the magic combo?).

Version-Release number of selected component (if applicable):
4.4.6-200.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
0. Use a keyboard like found like Lenovo x230
1. Re-enable SysRq magic keys
2. Start X session
3. Press AltGr + PrtSc with one finger
4. Try to type the C accent

Actual results:
Restart

Expected results:
No letter is emitted, or the accented letter is emitted as if SysRq wasn't pressed

Additional info:

Comment 1 Josh Boyer 2016-03-31 18:33:35 UTC
Sorry, we're not going to do anything with this bug.