Created attachment 17824 [details]
Cursor area after exiting quake3 based games
I have everything from git (mesa, drm, xserver, xf86-video-ati, etc)
This happens when I exit tremulous or enemy territory (both quake3 based games).
An area around the cursor stays painted on the screen, in addition to the moving cursor.
With "Desktop Effects" enabled the area is black, while it's transparent (only the cursor is showed) if I disable them, but in both cases the cursor is present.
Note that in the screenshot you can't see the cursor in the middle of the black area, but I can :)
I reported a similar (or the same?) problem to Peter Hutterer on the fdo mailing list. Don't know if he already looked into this.
Since I only have one quake3-based game on my system (and this is Q3 arena) I only experienced it there.
You maybe wanna add Peter to CC.
if you know his email address, can you add him? :)
Sure, I added him.
It seems this bug is gone after upgrading to xorg-server 1.5.0
I'll reopen it if I notice again.
You've got it wrong.
xorg-server-1.5.0 was not packaged from the git master branch. All the new input stuff like XI2 and MPX is not in xorg-server-1.5.0. That's the reason why you don't see the bug anymore.
I finally got to download ET, but I can't really run it. It seems to choose monitor sync ranges that my monitor cannot do.
In addition to that, when I ctrl+c the game, the server waits forever in drmGetLock (about 30% of the time I kill it).
So no progress here, until I can actually run anything and reproduce the bug.
Use ioquake3 plus the quake3 demo gamedata.
Fetch ioquake3 from icculus and the gamedata here:
Created attachment 20708 [details] [review]
This patch fixes the issue. Can you please confirm this?
Pushed the fix since it worked for me and I was rebasing it around my trees anyway.
Author: Peter Hutterer <firstname.lastname@example.org>
Date: Mon Dec 1 16:57:06 2008 +1000
xfree86: don't render SW cursors for devices attached to VCP (#16805)
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.