http://qa.mandrakesoft.com/show_bug.cgi?id=2810
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2003-03-06 17:06 -------
I hadn't tried that yet but yes, changing the mouse to whatever type it can be
(including auto)
and rebooting (or closing/reopening X) actually forces it to be GlidePoint.
Sorry for the uninteresting disturbance, but thanx... gotta have to make some noise at
belkin's :)
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
I'm actually using a belkin 2 ports PS/2 KVM so I can "control" two machines with one
console (Keyboard, mouse and screen)
The KVM doc gives it to be fully compatible with Linux (all distros)
When I set the mouse to standard mouse, I am able to switch from one machine to
another
without any problem.
If the mouse is set to PS/2 with wheel, switching back to ML9.1 makes the cursor out
of
control, as well as the buttons.
(The other machine is a win2K server (yes ARGH ! LOL) and recognizes the wheel without
any prob)
If you have some time left.... ;)
