[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#34079: marked as done (Problems with IMPS2 mouse protocol)

Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <45E33155.30402@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: gpm 1.14, June 1998
	 Xfree86 3.3.2
	 Perhaps others that use IMPS2

Debian 2.1
Microsoft IntelliMouse on PS/2 port
Kernel 2.2.2

Problems:
Once a program uses the IMPS2,IntelliMouse, protocol, no other programs
can communicate with the mouse correctly unless they use the IMPS2
protocol too.

Examples:
Running gpm with IMPS2 -- works ok.
Then run Xfree86 -- mouse skips around and clicks everywhere,even after
GPM is killed, must select IMPS2 to fix the error, or reboot and not
start GPM.

or
Running Xfree86 with IMPS2 then gpm wont work with standard PS/2 until
system 		is restarted.

Also, svgalib does not support the IMPS2 protocol so all programs that
use the svgalib for mouse input malfunction after gpm or Xfree86 is run.

Hope this helps
Marius Grigoriu

--- End Message ---
--- Begin Message --- 
Closing this bug since I didn't get any reply from the submitter (or
repliers) after my ping a month ago. If anybody ever reproduces this
problem, feel free to reopen.

Brice

--- End Message ---
Reply to: