From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Regression 2.6.35-rc1?] Sysrq works too well (no need of alt)
Date: Sat, 19 Jun 2010 23:16:32 +0200 [thread overview]
Message-ID: <201006192316.32360.rjw@sisk.pl> (raw)
In-Reply-To: <4C0E0E51.8050709@tudelft.nl>
On Tuesday, June 08, 2010, Éric Piel wrote:
> Hello,
> I haven't investigated much yet, but I have the feeling that since
> 2.6.35-rc1 my "Print Screen/SysRq" key works only as SysRq: if I press
> it (normally assigned to take screenshot in gnome), nothing happens (no
> input event received in userspace) and no key on the keyboard works
> afterwards, until I press Alt. Actually the keys work, but behave as if
> the sysrq key was kept pressed (can be seen in dmesg, or by pressing "b").
>
> Looking at the log, a potential culprit is commit
> 97f5f0cd8cd0a05449cbb77d1e6f02e026875802 (Input: implement SysRq as a
> separate input handler). Probably the logic of "have to press all the
> keys at the same time" changed to "have to press the keys one after each
> other". So pressing alt and later on pressing PrintScreen leads to a SysRq.
>
> Does anybody else see this behaviour? Any suggestion on how to solve
> this bug? I'll try reverting the commit and report if it fixes the
> problem (the git revert fails so I've got to fix the conflict manually).
Is this still a problem with 2.6.35-rc3?
Rafael
next prev parent reply other threads:[~2010-06-19 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 9:33 [Regression 2.6.35-rc1?] Sysrq works too well (no need of alt) Éric Piel
2010-06-08 22:55 ` Éric Piel
2010-06-09 0:37 ` Dmitry Torokhov
2010-06-09 8:30 ` Dmitry Torokhov
2010-06-09 11:32 ` Éric Piel
2010-06-19 21:16 ` Rafael J. Wysocki [this message]
2010-06-19 23:15 ` Éric Piel
2010-06-29 7:07 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201006192316.32360.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=E.A.B.Piel@tudelft.nl \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).