Bug 349501
Summary: | xset m 1 1 does not change the acceleration/threshold of the mouse pointer. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Ian Hands <iphands> |
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-25 07:46:10 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
Ian Hands
2007-10-23 20:46:03 UTC
I have tried this on a clean Update 9 install. The command "xset m 1 1" still does not change the mouse's behavior. Hi, Ian, I am slightly confused about the status of your support. Given that this is RHEL bug, I would expect you to file an issue through the IssueTracker. I will certainly not close this bug if you don't have support (and this is actually CentOS or educational license of RHEL), but you would get much better treatment if going through official ways. The official blurb follows: For official Red Hat Enterprise Linux support, please log into the Red Hat support website at http://www.redhat.com/support and file a support ticket, or alternatively contact Red Hat Global Support Services at 1-888-RED-HAT1 to speak directly with a support associate and escalate an issue. I have found a workaround that suits me... (Launching "X -a 1 :0" works as "xset m 1 1" does for me.) I do still believe that xset is not functioning properly. That being said I understand that I am a newcomer here but why should my "support" matter at all here (unless RHEL3 U9 is no longer supported by RedHat, or I am making a silly mistake (but I guess you would have pointed that mistake out already(?)). Shouldn't a bug be fixed asap either way? Wouldn't this only benefit RedHat to find (and smash) a bug before the customer? It does not really make a difference to me (I've found a reasonable alternative route). I am not trying to sound over critical here (forgive me if I did). I am just concerned about the "you would get much better treatment" part, and what it means to RHEL customers/community. Please disregard if I have made quick, wrong, and bad assumptions (I am admittedly new to this bug-tracker/community and while I work for a large company that works closely with Redhat I have never used "IssueTracker" or any other official channels of communication with RH). I do appreciate the heads up though. Thanks. -Ian p.s. Please reassign/resolve at your discretion. (The (possible) bug is not hindering me personally anymore.) Ian, no you are certainly not too much critical, but the situation is not simple we would like it to be. First of all, our resources are not unlimited, and we have currently 670 open bugs just for X related packages. That's a lot of work so we have to prioritize and some bugs get more preference than others. So, customers who pay for support get better treatment than those who don't (that certainly doesn't mean that Fedora/CentOS/unsupported RHEL bugs won't get any attention, just not that everybody would drop anything they have in hands to fix it; and of course, you are right, if the bugs hits you, it will most probably hit our clients as well). The other result of need to prioritize is that different distributions get different level of attention -- RHEL3 is now in the level that only security bugs and bugs which would severely disrupt operations of our clients get fixed. I hate to say it, but your bug doesn't fall into either category. Closing as per your last comment as WONTFIX. sorry, some typos "the situation is not as simple as we would like it to be", and some missing commas. |