Bug 49149
Summary: | mouseconfig no longer allows scroll wheel to work | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | William M. Quarles <walrus> |
Component: | mouseconfig | Assignee: | Brent Fox <bfox> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2006-02-21 18:48:03 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
William M. Quarles
2001-07-15 21:16:31 UTC
I am changing the status on this update from low to normal, as this is now defintitely a bug that should be fixed. As of this update, we are now having the erratic mouse problem in X-Windows while using the new mouseconfig and XConfigurator as well. It is intermittent but happens at least once a day. The mouse shoots up into the top right corner of the screen and resists moving back, and behaves as if buttons on the mouse are being pressed while we are trying to move it back. When we press CTRL-ALT-BACKSPACE to kill X-Windows, and end up back at the txt terminal mode, the mouse function is again restored. startx again, and the mouse continues working until the next attack of erratic behavior. We have confirmed that our problem was caused by a combination of hardware and software problems. However, it is still, in my opinion, a software bug. I obtained another, similar mouse (different harware version, but same brand and model), and tried both mice on a Windoes 98 machine running the latest version of the Microsoft IntelliPoint driver software, available for free download. The scroll wheels on both mice worked perfectly. However, it was noticed that the mouse for our Linux machine would occasionally stop working. This was determined to be caused by a frayed cable, so our mouse must be replaced (or, we can build a new cable, but it's under warranty). When the test mouse that was lent to our group was tried on the Linux machine, no erratic behavior has been observed during normal use for two days. However, it was observed if the mouse was unplugged and then replugged during an X session, and the scroll wheel still failed to work, which was our original complaint. I decided to open up Xconfigurator and try changing our screen resolution. Once I did that, it worked. I changed the resolution back, and it still worked. My theory is that: 1. Our mouse somehow got changed to another type, which might have originally caused our erratic behavior problem. 2. When we tried to change our mouse back using mouseconfig, the configuration files for the X server or Xconfigurator or whereever they are stored for this needed to be reloaded, and mouseconfig does not do that appropriately force these files to be reloaded. Not even a reboot seemed to reload these files, but directly making changes to the video settings using Xconfigurator did. I am not sure what appropriate action must be taken to repair this, but the trouble definitely seems to lie somewhere between Xconfigurator and mouseconf. As a suggestion for an improvement, I think that it should be made possible for a user to at least accidentally unplug their mouse and have the ability to plug it back in and continue to use X-windows without having to kill it first to reobtain control of the mouse. I have just completed a text mode interface for redhat-config-mouse, which means that mouseconfig will be deprecated in the next release of Red Hat Linux. Therefore, I will not be putting any development time towards fixing mouseconfig bugs, so I'm closing this as 'wontfix'. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |