Comment 20 for bug 303601

Revision history for this message
Michael Jones (jonesmz) wrote : Re: [Bug 303601] Re: REISUB is broken

On my laptop, disabling the keyboard shortcuts associated with the SysReq
key didn't do it. I also had to modify

Some Linux distributions come with the magic sysrq disabled as a security
measure, considered by some to be misguided. You'll see in */etc/sysctl.conf
*

kernel.sysrq = 0

 Change this to

kernel.sysrq = 1

 and run

sysctl -p

 You should always check for this on a new Linux system before running into
a freeze that makes you wish magic sysrq was working.

from

http://en.wikipedia.org/wiki/Magic_SysRq_key

and THEN it worked.

Is this disabled in Ubuntu intentionally?

On Fri, Jun 26, 2009 at 6:22 PM, motty <email address hidden> wrote:

> I worked around it by System->Preferences->Keyboard shortcuts - disable
> anything that was attached to the PrintScrn key. (on a laptop with PrintScrn
> & SysRq on the same key).
> This is still very disturbing, because SysRq should have not depended on
> any application-level settings.
> Besides, the more gentle ops, like SysRq-H (help), don't show anything
> within X.
> Hope for it to work at the next freeze...
>
> --
> REISUB is broken
> https://bugs.launchpad.net/bugs/303601
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> Now, I'm not sure if this is in all installs of Intrepid or just some of
> them, but somehow the magic SysRq keys stopped working on several installs
> of Intrepd Ibex. I don't know what causes it, but it becomes very apparent
> thanks to Compiz Fusion somehow locking up the entire operating system.
>
> A test of REISUB on this system when it is working shows none of it works
> (In fact, I got flooded by gnome-screenshot, indicating pretty clearly the
> magic keys are somehow disabled.)
>
> I need bug confirmation, which means that if this problem has shown up in
> other systems, it's likely a bug and not some problem I caused.
>