http://bugs.winehq.org/show_bug.cgi?id=32212
Bug #: 32212 Summary: Mouse cursor not released from Blizzard based games Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: kantlivelong@gmail.com Classification: Unclassified
ALT+Tabbing and workspace switching doesn't work properly while playing Diablo 3, StarCraft 2, or World Of Warcraft. The game can be minimized/moved but the cursor still shows as the games cursor and not X11. I am able to type in other apps but clicking results in sending the click event to the game instead.
http://bugs.winehq.org/show_bug.cgi?id=32212
kantlivelong kantlivelong@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.5.17
http://bugs.winehq.org/show_bug.cgi?id=32212
jacobsen.douglas@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacobsen.douglas@gmail.com
--- Comment #1 from jacobsen.douglas@gmail.com 2012-11-14 10:14:44 CST --- I have the same issue. Only with SC2 (wine 1.5.14) because D3 was wine 1.5.10. If I tried to play D3 in anything above 1.5.10 I got a message that my video card was too crappy and it wouldn't let me play.
But otherwise it's exactly the same as kantlivelong. I only tried workspace switching, but my mouse doesn't work outside of the game. I can however use the keyboard (alt+tab selects applications outside of the game, and I can use keyboard shortcuts to control windows).
This also didn't use to happen for me, but I couldn't tell you which wine versions I was using (maybe 1.5.11?).
Ubuntu 12.10 x86_64
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #2 from jacobsen.douglas@gmail.com 2012-11-14 19:41:09 CST --- As an update, I tested with 1.5.13 and I don't have the problem then.
http://bugs.winehq.org/show_bug.cgi?id=32212
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr 2012-11-14 21:51:13 CST --- Please, perform a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=32212
kantlivelong kantlivelong@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet@gmail.com, | |kantlivelong@gmail.com
--- Comment #4 from kantlivelong kantlivelong@gmail.com 2012-11-15 19:55:29 CST --- Regression Test Results:
73d68c5a31b972a24dab39b036a5d3197edb3565 is the first bad commit commit 73d68c5a31b972a24dab39b036a5d3197edb3565 Author: Henri Verbeet hverbeet@codeweavers.com Date: Fri Sep 28 01:06:53 2012 +0200
winex11: Handle a NULL cursor clipping rect the same as a fullscreen rect.
We want to avoid ungrabbing the clipping window if "fullscreen clipping" is enabled.
:040000 040000 3dec98daefa3c7fb1ca29f0d5525e0d92975e151 959ad7b92a3c85f3e38ce75b618b1b263e0d9d46 M dlls
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #5 from kantlivelong kantlivelong@gmail.com 2012-11-15 20:40:47 CST --- Reversing commit 73d68c5a31b972a24dab39b036a5d3197edb3565 on the latest git fixes the problem.
http://bugs.winehq.org/show_bug.cgi?id=32212
kantlivelong kantlivelong@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |winex11.drv
http://bugs.winehq.org/show_bug.cgi?id=32212
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |73d68c5a31b972a24dab39b036a | |5d3197edb3565
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #6 from Henri Verbeet hverbeet@gmail.com 2012-11-16 04:45:57 CST --- This works fine here in at least SC2. Are you using a clean prefix? What window manager are you using?
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #7 from kantlivelong kantlivelong@gmail.com 2012-11-16 11:12:25 CST --- I retested this on another fresh prefix for both SC2 & D3 (did not have time for WoW)
-Two separate machines. -wine-1.5.17 with and without the commit. -Ubuntu 12.04 x86_64 -Cinnamon 1.6.7 -Machine 1 & 2 using nvidia drivers
I can reconfirm that the issue happens with the commit
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #8 from Henri Verbeet hverbeet@gmail.com 2012-11-25 15:34:58 CST --- Actually, this sounds a bit like some variant of bug 23745, or something similar. Does this also happen with a different wm like e.g. fvwm?
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #9 from kantlivelong kantlivelong@gmail.com 2012-11-25 16:26:05 CST --- (In reply to comment #8)
Actually, this sounds a bit like some variant of bug 23745, or something similar. Does this also happen with a different wm like e.g. fvwm?
The only other WM I have tried is Unity and reverting this patch resolved the issue as well.
The game does not crash or freeze like 23745 but simply holds onto the cursor focus and captures the events. I can use keyboard shortcuts to work my way through the WM but cannot use the mouse.
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2012-11-26 05:01:01 CST --- (In reply to comment #9)
The only other WM I have tried is Unity and reverting this patch resolved the issue as well.
Unity isn't much better.
The game does not crash or freeze like 23745 but simply holds onto the cursor focus and captures the events. I can use keyboard shortcuts to work my way through the WM but cannot use the mouse.
I suppose you should create a "+tid,+x11drv,+event,+mouse,+win" log. The impression I have is that the window never receives the FocusOut event though, so the clip window never gets reset, and the only reason it worked before is because the clip window never got set properly either.
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #11 from kantlivelong kantlivelong@gmail.com 2012-11-26 10:31:04 CST --- Created attachment 42626 --> http://bugs.winehq.org/attachment.cgi?id=42626 Reverted commit
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #12 from kantlivelong kantlivelong@gmail.com 2012-11-26 10:33:19 CST --- Created attachment 42627 --> http://bugs.winehq.org/attachment.cgi?id=42627 With Commit
I switched to work space(WS) 2 with the game in 1 and it worked. Moved the game to WS2 and switched to WS1 and no issues again. The 3rd time i switched between work spaces the issue occurred and kept on occurring.
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #13 from Henri Verbeet hverbeet@gmail.com 2012-11-26 10:42:49 CST --- (In reply to comment #10)
I suppose you should create a "+tid,+x11drv,+event,+mouse,+win" log. The
Actually that's supposed to be +cursor instead of +mouse.
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #14 from kantlivelong kantlivelong@gmail.com 2012-11-26 11:03:56 CST --- Reverted: http://paste.ubuntu.com/1389405/ 1.) Switch to WS2 = GOOD 2.) Move to WS2 and switch to WS1 = BAD 3.) Move to WS1 and switch to WS2 = GOOD 4.) Switch to WS1 and switch to WS2 = GOOD 5.) Move to WS2 and switch to WS1 = BAD
With Commit: http://paste.ubuntu.com/1389408/ 1.) Switch to WS2 = GOOD 2.) Move to WS2 and switch to WS1 = GOOD 3.) Move to WS1 and switch to WS2 = GOOD 4.) Switch to WS1 and switch to WS2 = GOOD 5.) Move to WS2 and switch to WS1 = GOOD
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #15 from joaopa jeremielapuree@yahoo.fr 2013-04-13 01:21:45 CDT --- still a bug in current wine?
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #16 from kantlivelong kantlivelong@gmail.com 2013-04-22 18:54:45 CDT --- (In reply to comment #15)
still a bug in current wine?
Sorry for the delay.
I'll test this by the weekend.
http://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #17 from kantlivelong kantlivelong@gmail.com 2013-04-29 18:21:57 CDT --- UPDATE:
I am still seeing the issue on 1.5.29.
https://bugs.winehq.org/show_bug.cgi?id=32212
--- Comment #18 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=32212
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #19 from Ken Sharp imwellcushtymelike@gmail.com --- Abandoned
https://bugs.winehq.org/show_bug.cgi?id=32212
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #20 from Bruno Jesus 00cpxxx@gmail.com --- Closing abandoned bugs.
-
wine-bugs＠winehq.org