Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 142534 - gpm locks the keyboard if no mouse is present
gpm locks the keyboard if no mouse is present
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gpm (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Eido Inoue
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-12-10 09:40 EST by Stefan Kutzke
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-10 11:22:39 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 Stefan Kutzke 2004-12-10 09:40:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040803 Firefox/0.8

Description of problem:
The keyboard doesn't work after booting a machine into  runlevel 3
with gpm service configured an running and no mouse is connected.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configuring mouse wtih redhat-config-mouse or by hand.
2. Disconnect the mouse.
3. Reboot the machine.

Actual Results:  The keyboard doesn't work.

Expected Results:  The keyboard should work regardless if a mouse is
connected or not.

Additional info:

It's not really a problem. I do a chkconfig gpm off and throw the
mouse away :-)
Comment 1 Eido Inoue 2004-12-10 11:22:39 EST
Couldn't reproduce using your steps; may be hw specific. Some
systems-- especially those using PS/2 mice-- are less forgiving about
unplugging/plugging in mice without power cycling (rebooting may not
be enough).
Comment 2 Stefan Kutzke 2004-12-13 11:16:38 EST
You are right, it's hw specific. Power cycling the server machine
solves the problem.

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