Red Hat Bugzilla – Bug 501092
Displayed cursor doesn't properly move off the top of second screen
Last modified: 2018-04-11 04:02:19 EDT
Created attachment 344245 [details]
Description of problem:
I have two screens. One is 1280x1024, and one is 1024x768. They're arranged like this:
If I move my mouse cursor up into the "empty space" above the smaller monitor, the cursor will reach the top edge of the monitor and stop. If I'm dragging a window up into the "empty space", the cursor will stop moving once it reaches the top of the smaller screen, but the window will keep moving up as though nothing strange is happening.
After about 40 pixels of my cursor appearing stuck while I move it up into the "empty space", the cursor will start to disappear from the bottom up. For example, only the top half of the cursor will be showing on the top edge of the monitor. Moving my mouse farther up will cause less of the cursor to be visible, and moving my mouse down causes more of the cursor to be visible.
In all of this, screenshots, dragging windows around, and moving the cursor left to the larger screen show that the "actual" cursor position is moving around correctly, but the cursor is not being properly drawn at that position.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Have a second monitor with "empty space" above it.
2.Move cursor up into empty space
Cursor stops for ~40 pixels, then disappears from the bottom up.
Cursor should act like it's moving behind the plastic casing of my monitor: not stop and not show just the top half of my cursor on the top edge of the screen.
This is on a Radeon 9000, if that's significant. I'll attach /var/log/Xorg.0.log; there's no xorg.conf. This bug is on a fully-updated F11 Preview installation.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This only happens with KMS enabled, which makes me wonder if I reported this against the wrong package.
Still happening with:
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Unless someone else shows up to test, this report can be closed. I no longer have this video card and so cannot test it.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.