archive mirror
 help / color / mirror / Atom feed
From: Tim Connors <>
Subject: Re: 2.6 not cat proof
Date: Fri, 28 Nov 2003 15:19:27 +1100	[thread overview]
Message-ID: <> (raw)

bert hubert <> said on Wed, 26 Nov 2003 21:10:52 +0100:
> This bug has been seen here over eight years ago and it is back.. linux
> 2.6.0-test4 is still not cat proof :-)
> I found my cat asleep on the warm laptop, it is winter here, and the
> keyboard was dead. Mouse still works, but I had to reboot before I could use
> the keyboard again. Restarting X, which I could do with the mouse, did not
> help.

Are you sure he didn't press alt-sysreq-r or something? Mine has at
various times, pressed ctrl-alt-backspace, ctrl-alt-delete,
alt-sysrq-b (without s and u first, bastard), and the power button
directly. This is all on a laptop, so sysrq requires you pressing fn

One of the cats have also turned my heater on by the touch sensetive
buttons, in the middle of summer while I was out for the day. The
heater, and the power button now have molly gaurds, but the key
combinations are hard to gaurd against.

Read the fvwm webpage - most of the developers of fvwm have cats, and
have, IIRC, documented various ways around their key typing
habits. IIRC, there is a package that at least detects when a cat is
walking across a keyboard, and forces you to click the mouse in a
window under X. Won't stop the kernel crashing, but will do something.

In all seriousness, on my laptop, (do to this and other reasons, I
have stopped using 2.6 for the time being), when I pressed h and j (or
something like that) at the same time, when I realeased one of the
keys, I got some kernel warning like "invalid keyscan" or
something. Never wrote it down, sorry.

TimC --
When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.

  parent reply	other threads:[~2003-11-28  4:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 20:10 2.6 not cat proof bert hubert
2003-11-26 20:16 ` Nigel Cunningham
2003-11-26 20:38   ` William Lee Irwin III
2003-11-27  7:30   ` Gábor Lénárt
2003-11-27  8:54     ` Måns Rullgård
2003-11-27 11:57       ` Paul Jackson
2003-11-27 16:41         ` Måns Rullgård
2003-11-27 17:37           ` Gene Heskett
2003-11-27 18:21             ` Nigel Cunningham
2003-11-28 10:43               ` Harald Arnesen
2003-11-30 20:09                 ` Bernd Petrovitsch
2003-11-30 21:37                   ` Henrik Persson
2003-12-01  1:46                     ` Stuart Longland
2003-11-26 20:41 ` Mike Dresser
2003-11-26 20:48   ` Edesio Costa e Silva
2003-11-26 23:46     ` Mike Fedyk
2003-11-27  0:50       ` Måns Rullgård
2003-11-27  1:06         ` Mike Fedyk
2003-11-27  8:52       ` Stuart Longland
2003-11-26 20:42 ` Måns Rullgård
2003-11-28  4:19 ` Tim Connors [this message]
2003-11-29 13:36 ` Bill Davidsen
2003-11-29 14:23   ` Gene Heskett
2003-11-29 16:36   ` Markus Hästbacka
2003-11-30 14:29     ` Bill Davidsen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).