If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

After the update to 10.10 on Gentoo (also in 10.11), the mouse cursor in the secondary screen on my dual head system (separate desktops, no xinerama) becomes garbled in certain situations:
- In wine programs
- Renoise
- All programs which use their own cursor instead of the system one

The mouse cursor is fine on the primary screen. Ati-drivers up to and including 10.8 were fine, too. (I had to skip 10.9 because of the hideous vt switching bug).

Because there doesn't seem to be any programs capable of taking screenshots with mouse cursors visible, I had to do a dumb-blonde-style screenshot with my digital camera, please see here: http://steam.punk.dy.fi/ati-10.10.png
It's an Enigma simulator running with wine. The white garbled square should be the normal Windows-style cursor.

Are you sure this issue is related to ATI drivers? There was a major xorg server update from 1.8 to 1.9. It could introduce this problem. I do also have dual screen configuration on dualheaded video card. You mentioned cursor garbles in certain situations, but I always get corrupted mouse cursor on second screen. There are number of problems related to separate X screens in xorg server so I thought it could be the one of them.

Comment

Damn! You are right!!! It was xorg-server-1.9.x which was the 'bad guy' here; it didn't occur to me to test this, although I upgraded them both at the same time... Now I downgraded to xorg-server-1.8.2 while still using ati-drivers-10.11 (quite easy on Gentoo), and the mouse cursor corruption is gone .Thanks for pointing that out!

While testing I noticed that on xorg-server-1.9, if I used the default xorg cursor instead of my usual custom cursor, the cursor was corrupted all the time on the secondary screen.

Now, if I could just figure out where should I report THIS bug so it gets noticed...