Bug 87634 - XSetInputFocus errors spewed all over VC1
XSetInputFocus errors spewed all over VC1
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-31 09:24 EST by Chris Ricker
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-10-21 21:30:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2003-03-31 09:24:57 EST
I just did a fresh install of RHL 9 gold from CD onto a system with a Matrox G400

During the install, the error message

failed on XSetInputFocus()

spewed constantly across VC1

The install seemed to work fine otherwise, though
Comment 1 Michael Fulbright 2003-03-31 16:24:28 EST
By spewed you mean they come out continuously at a particular rate, or only once
during the install?
Comment 2 Chris Ricker 2003-03-31 16:34:15 EST
Continuously... The screen wound up looking like

failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on XSetInputFocus()failed on XSetInputFocus()failed on
XSetInputFocus()failed on
<snip>

as they kept appearing....
Comment 3 Chris Ricker 2003-03-31 16:35:30 EST
Hmm, this system has a serial mouse (Kensington Thinking Mouse -- not made any
more, but still the best mouse in existance ;-). serial instead of ps/2 is the
only unusual hardware feature of the system that I can think of....
Comment 4 Michael Fulbright 2003-04-02 15:21:50 EST
Could you switch to VC2 (cntl-alt-f2) and type

less /tmp/XF86Config.test

and look through it for anything related to Input devices or mice and let me
know what its configured to use?

You should see something like:

Section "InputDevice"
   Identifier  "Mouse0"
   .
   .
   .
   .
EndSection

If you could give me the stanza in your file that would help.
Comment 5 Michael Fulbright 2003-04-22 12:31:35 EDT
Closing due to inactivity. If you have new information to add please reopen the
issue report.
Comment 6 Chris Ricker 2003-04-25 09:05:49 EDT
It's

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "Microsoft"
        Option      "Device" "/dev/ttyS0"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection
 
Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
        Identifier  "DevInputMice"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "no"
EndSection

both before and after I configure it to use the Kensington mouse
Comment 7 Michael Fulbright 2003-05-13 14:42:16 EDT
Mike could you try testing with a serial mouse to see if this problem still occurs?
Comment 8 Tripp Lilley 2003-09-10 20:24:55 EDT
We're having the same problem here with a twitchy sysadmin who clicks too fast.
Basically, the problem has shown up when he clicks in a text field and ends up
sliding the mouse out of the text field (which reveals the little "copy" drag
icon) and letting go, instead of a clean click in the field.

We haven't been able to exactly reproduce the bug (and that's a good thing,
since we're trying to get our install working), but maybe this feedback will help.
Comment 9 Jeremy Katz 2003-10-21 21:30:23 EDT
This shouldn't happen anymore in Fedora test releases.

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