Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Apr 2009 21:38:42 -0400
From:      debardeleben@aol.com
To:        freebsd-current@freebsd.org
Subject:   Re: KDE and input events.
Message-ID:  <8CB8538B792B51B-388-26F6@webmail-dd11.sysops.aol.com>
In-Reply-To: <8CB8530B963508E-D10-12E5@WEBMAIL-MA11.sysops.aol.com>
References:  <8CB8530B963508E-D10-12E5@WEBMAIL-MA11.sysops.aol.com>

next in thread | previous in thread | raw e-mail | index | archive | help

 I updated to r190788, and reset the internal state of
my mouse using windows and it works now. I do not
know if recent changes fixed it or if the mouse just
needed a reset. In any case it looks as though current -CURRENT
works with my mouse.

-Charles


 


 

-----Original Message-----
From: debardeleben@aol.com
To: freebsd-current@freebsd.org
Sent: Mon, 6 Apr 2009 5:41 pm
Subject: Re: KDE and input events.










Are you running -CURRENT? I have found that my bluetooth
logitech mx-revolution mouse is broken yet again. I am seeing
stuff like you are seeing, where the buttons are just whacky.
usually the left button is permanently pushed, but at the moment
I am getting no motion events out of it. All of my recent issues
started when I updated to a version that included r190741 but
I have not yet proven this to be the source. For now I am using the
mouse pad on my dinovo keyboard, which seams to work.

Anyone know what the change to hid processing is for? so far
every time it is changed, my mouse stops working? until someone
restores some old code that is usually described as unneeded or
a work around for some other bug. Is there maybe a bug in the
Logitech HID implementation?

-Charles
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"



 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8CB8538B792B51B-388-26F6>