http://bugs.winehq.org/show_bug.cgi?id=17267
Summary: World of Warcraft 3.0.8a: No input in main game area Product: Wine Version: 1.1.14 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: betadog@gmx.net
Created an attachment (id=19260) --> (http://bugs.winehq.org/attachment.cgi?id=19260) console output of wine while bug occurs
Keyboard and mouse input doesn't work concerning interaction with the ingame world (for things like chatting and moving around).
Everything apart from that works, though - all the UI elements respond just fine. Keyboard input in text windows (like when adding a friend to the friendlist) works, too. Also ingame objects (NPCs, other players etc) light up when hovered over, which could mean that the WoW client doesn't recognize mouse clicks or keyboard key presses in the (3D-accelerated?)gameing area.
Other things I've tried: -fiddling arround with winecfg (tried all the window configuration settings; set Windows Version to Vista and 2000) -Ubuntu-supplied wine version 1.0.1 (1.1.14 is from the WineHQ repo) -different version of the nvidia driver: 177.28 (ubuntu provided) -mousepad, different mouse -windowed mode or starting with wine explorer.exe /desktop=1024x786 -starting WoW from a desktop link (not from console)
My System: Acer Aspire 7530G Laptop Ubuntu 8.10 - Kernel 2.6.27-11-generic Nvidia 9400M - driver version: 180 3GB Ram
http://bugs.winehq.org/show_bug.cgi?id=17267
Adys adys.wh+winehqdotorg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh+winehqdotorg@gmail.c | |om
--- Comment #1 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-05 10:45:12 --- I'm not sure what you mean by this. Out of curiousity: do you run a second monitor? If so, do you run Xinerama or Dual View?
Xinerama is known to "detach" mouse input once in a while, freaky bug -- but nothing to do with keyboard input.
180.22 driver with clean wine-1.1.14 wineprefix should work just fine. Install it from the official nvidia website if anything.
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #2 from Philipp N. betadog@gmx.net 2009-02-05 11:47:48 --- (In reply to comment #1)
I'm not sure what you mean by this. Out of curiousity: do you run a second monitor? If so, do you run Xinerama or Dual View?
Xinerama is known to "detach" mouse input once in a while, freaky bug -- but nothing to do with keyboard input.
180.22 driver with clean wine-1.1.14 wineprefix should work just fine. Install it from the official nvidia website if anything.
To clarify: Usually, you move your character in 3rd person with the WSAD keys or the mouse, or interact with the game world by clicking on non-player-characters and other game objects with the mouse. Also the camera is controlled by simultaneously holding a mouse button and moving the mouse (doesn't work.). Pressing keys or mouse buttons seemingly isn't registered by the game in that part of the screen - but on UI elements, such as the in-game menu or the inventory, mouse clicks and keyboard keys are working just fine. I'll attach an explanatory screenshot if needed.
No second monitor attached - just the build-in LCD screen. No Xinerama running, no Dual View configured.
It might be worth noting that the build-in graphic card is of the Hybrid SLI variant - which means that there are actually two integrated graphic cards. The one in use is specified by BusID in xorg.conf.. If there is more info needed I'ld be glad to provide.
For now, I'll try the 180.22 driver and report back.
I tried with a clean prefix, actually I tried just after purging wine, manually rm'ing ~/.wine and reinstalling 1.1.14 from WineHQ's repository.
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #3 from Philipp N. betadog@gmx.net 2009-02-05 12:14:51 --- (In reply to comment #1)
I'm not sure what you mean by this. Out of curiousity: do you run a second monitor? If so, do you run Xinerama or Dual View?
Xinerama is known to "detach" mouse input once in a while, freaky bug -- but nothing to do with keyboard input.
180.22 driver with clean wine-1.1.14 wineprefix should work just fine. Install it from the official nvidia website if anything.
Same problem with nvidia driver 180.22 and clean prefix.
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #4 from Adys adys.wh+winehqdotorg@gmail.com 2009-02-05 12:18:29 --- I'm not able to reproduce this, and have never heard of this. Has this bug always occured for you? If not - can you run a regression test? http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #5 from Philipp N. betadog@gmx.net 2009-02-05 12:43:07 --- (In reply to comment #4)
I'm not able to reproduce this, and have never heard of this. Has this bug always occured for you? If not - can you run a regression test? http://wiki.winehq.org/RegressionTesting
This is the first time I've tried running World of Warcraft (or wine for that matter) on this laptop. I can only compare it with a previously owned laptop where everything worked fine. I'm not able to try with previous versions of WoW as I can't connect (get into the game world) with previous versions without resorting to legally grey area methods. I'll do the regression testing when I've got more time on my hands - for now, I can only attest that the same bug occurs on wine 1.0.1.
I agree that this seems to be a pretty uncommon bug. Google turns up nothing comparable.
The only uncommon hardware in my laptop I can think of is the aforementioned Hybrid SLI graphics card(s).
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #6 from Austin English austinenglish@gmail.com 2009-08-05 10:24:58 --- Is this still an issue in current (1.1.26 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17267
Philipp N. betadog@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WORKSFORME
--- Comment #7 from Philipp N. betadog@gmx.net 2009-08-05 11:08:06 --- Bug dissapeared. Can't reproduce it anymore.
http://bugs.winehq.org/show_bug.cgi?id=17267
--- Comment #8 from Philipp N. betadog@gmx.net 2009-08-05 11:10:45 --- As I didn't play any World of Warcraft since the aforementioned patch, I can't tell when the bug dissapeard - seems like something along the way to 3.2.0 made it go away.
Thanks to everyone concerned. :)
http://bugs.winehq.org/show_bug.cgi?id=17267
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |FIXED
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-05 22:58:39 --- Fixed then.
http://bugs.winehq.org/show_bug.cgi?id=17267
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Alexandre Julliard julliard@winehq.org 2009-08-07 12:39:53 --- Closing bugs fixed in 1.1.27.