Bug 6168 - Unplugging devices (keyboard, mouse, printer)
Unplugging devices (keyboard, mouse, printer)
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-10-20 20:22 EDT by admin
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-19 10:39:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description admin 1999-10-20 20:22:05 EDT
I am having the following problem;

Keyboard and mouse work fine on boot up, but if I unplug the
keyboard and plug it back it, the keyboard is not
recognized and a hard reboot must occur.  With the mouse I
must exit X and restart for the mouse to become active
again.  A simliar problem occurs with the printer if it is
shut off and turned back on again, it is not recognized.

Seems to be an error re-detecting devices once they have
been unplugged and plugged back in.

On a side note, I think this might be related to the problem
of printer ports not being detected (bug #5540)
Comment 1 Michael K. Johnson 1999-11-19 10:39:59 EST
Some machines simply do not like this.  This isn't a Linux problem;
I've plugged and unplugged keyboards and mice with no problem, though
I do it sparingly because I've been told that it can damage some hardware
if you get unlucky.  Perhaps you got unlucky?  I also turn my printer
on and off and on and off.

This is not related to bug 5540.
Comment 2 Brent R Brian 2000-01-09 13:07:59 EST
I had this problem with "intelligent" devices, once I went back to a simple
mouse and keyboard, no more problems.

I use a switch box on the system and switch to/fro all the time now without

(Gateway2000 Anykey keyboard and AOpen serial mouse).


Note You need to log in before you can comment on or make changes to this bug.