http://bugs.winehq.org/show_bug.cgi?id=27779 --- Comment #22 from Kuro <dragon_a.p(a)gmx.net> 2011-07-18 07:38:46 CDT --- (In reply to comment #21)
(In reply to comment #19)
(In reply to comment #18)
No, as I mentioned before I'm seeing this bug in a non-Steam game, Starsiege: Tribes.
This bug is merely associated with the Steam update because it was very closely timed with the Wine update.
Have you actually made sure your problem in Starsiege:Tribes was introduced by the same commit what I posted in comment#10?
I see several contradictions in this bug report so I'd like to summarize what I know about the issue.
1) Non-Steam version of a game is not affected and virtually all of my Steam games exhibit the problem (they're scattered around on my HDD in different wineprefixes).
2) commit ae52a8c2cb0cbca1496e86956a59e5d7160ca5a2 cannot be reverted cleanly (not even on the nearest 1.3.20 version) but after git checkout ae52a8c2cb0cbca1496e86956a59e5d7160ca5a2 I see both mouse pointers git reset --hard HEAD^ I see only the game's own mouse pointer
3) using virtual desktop mode and with unchecked "Automatically capture the mouse in full-screen windows" option the problem doesn't exist.
Fedora 15 + Gnome 3 + X Server 1.10.2
A little question: How can I compile it with "git reset --hard HEAD^"? I'm asking since I don't know much about git and how it works if you change the revision...
Nevermind I found out... But it doesn't help the problem is still present... -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.