Bug 75728
Summary: | ps2 mouse button problem with XTestFakeButtonEvent() | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Robert J. Brown <rj> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-11 19:08:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert J. Brown
2002-10-11 16:18:26 UTC
ehm if you say this is an X bug, why do you file it against the kernel ? I filed against the kernel because I could not find xfree86 as a choice to file it against, and bugzilla forced me to choose something. Also, it seemed to some of us that since it looked ps2 specific, that it might be in the kernel ps2 driver. Sorry. :-( I just tried rh8.0 with an old logitech serial mouse, and the problem manifested itself, to my great suprise, so I guess it is not ps2 specific after all. :-\ It turns out that what we will really be needing is for it to work with a USB mouse ultimately. Now that I see the problem with a serial as well as ps2 mouse, I suspect that the USB mouse will show it too. I cannot run a USB mouse test until MOnday. I will keep you informed. Red Hat Linux 7.0, 7.1, 7.2, and 7.3 come with both XFree86 4.x, and with all of the XFree86 3.3.6 servers, so if you decide to use an older release, there is no need to go back as far as 6.2, since 3.3.6 is supported in all 7.x releases as well - unless of course you have a particular fancy to the 6.2 release. Since this problem is likely to affect an extremely small number of users, and since it hasn't at all been reported in all the time XFree86 4.x has been released, it is not an issue which I can assign any priority to, and is thus unlikely to ever be looked into by us. This is ultimately an issue that should be reported directly to XFree86.org, due to the reasons cited above. You can report this problem, by emailing xfree86, and also the xpert mailing list. The best way to get resolve from upstream, is to try and stimulate interest from them in solving the problem. I'm closing this as WONTFIX for now, however, if you encounter a bug fix patch in the wild, or from XFree86.org, feel free to attach the patch to this report and reopen. Thanks. |