Red Hat Bugzilla – Bug 815627
There is no mouse cursor in the Diablo III beta game
Last modified: 2012-04-26 13:46:50 EDT
Description of problem: It's possible to install and run the Diablo III beta game with Wine (with the patches listed below). But there is no mouse cursor during the game, although the game responds to the mouse moving and clicking. The issue shows regardless of the DE and wine versions (the problem exists in the "bare" X session too). At the same time, in other GNU / Linix distros everything is OK (that's why I wrote bug-report here). http://bugs.winehq.org/attachment.cgi?id=39500 http://bugs.winehq.org/attachment.cgi?id=39494 http://bugs.winehq.org/attachment.cgi?id=39565 ___________________________________ Version-Release number of selected component (if applicable): wine-1.5.1-1.fc16.i686 wine-1.5.2-1.fc16.i686 kde*-4.8.2-1.fc16.i686 xorg-x11-server*-1.11.4-2.fc16.i686 ___________________________________ How reproducible: always ___________________________________ Steps to Reproduce: 1. Following these instructions: http://appdb.winehq.org/objectManager.php?sClass=version&iId=25588 http://appdb.winehq.org/objectManager.php?sClass=version&iId=25588&iTestingId=70944 2. Run the game. 3. The is no mouse cursor. ___________________________________ Actual results: There is no mouse cursor in the game. The game is not playable. ___________________________________ Expected results: The game works fine. The mouse is usable during game. ___________________________________ Additional info:
Please try this update which is in pending state for f16: https://admin.fedoraproject.org/updates/wine-1.5.2-2.fc16
I've updated Wine up to 1.5.2-2. There are no changes regarding the visibility of the mouse cursor in the game. Sad...
In general, the culprit turned out to be q4wine. Winecfg was giving the errors until I've configured it with q4wine. Then I've installed vcrun200{5|8} & winhttp with winetricks. As a result I was able to run Diablo III beta, but without a mouse. I had removed the ~/.wine prefix and tried to run winecfg again, but this has resulted in an error again. So I've just copied the prefix (which had already contained vcrun200{5|8} & winhttp) from another computer (with Ubuntu installed). After these actions Wine stopped giving an error, and Diablo III beta has been launched well (with the mouse cursor). In other words, now the bug is that Wine can not independently create a working prefix, which allows to install anything (e.g. with winetricks). This bug should be closed. Continuation is here https://bugzilla.redhat.com/show_bug.cgi?id=816623