http://bugs.winehq.org/show_bug.cgi?id=22486
Summary: Moving the mouse pointer to top of the screen in Diablo 2: LOD teleports it to the bottom of the screen Product: Wine Version: 1.1.42 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: benshalom@gmail.com
The problem appears in Diablo 2: Lord of Destruction, running on 64-bit ubuntu 10.04 with Nvidia 9500m (driver 195.36.15) in 3d mode (using glide wrapper 0,84c) and 800x600 full-screen resolution.
In the game as well as in the menus, when I move my mouse cursor to the top of the screen it disappears and then re-appears at the screen bottom. This happens with compiz on or off, and regardless of my gnome regular resolution.
Setting the Nvidia option [Option "ModeValidation" "NoXServerModes"] in xorg.conf does not help.
Please let me know if more data is needed.
http://bugs.winehq.org/show_bug.cgi?id=22486
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #1 from Wylda wylda@volny.cz 2010-04-25 12:57:53 ---
Can't confirm this bug report. Works normally here in all the following versions:
* 1.1.42, 1.1.43, 1.1.43-249-g033bb8a
The only issue with the cursor is, that under latest tested git i see both game&KDE cursor, but that's probably because of one of those well know cursor issue.
I also think, that since 1.1.43 there is no need for glide wraper as 3D works again.
http://bugs.winehq.org/show_bug.cgi?id=22486
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2010-04-25 15:01:43 --- OP, are you using vanilla Wine or with some additional patches?
http://bugs.winehq.org/show_bug.cgi?id=22486
--- Comment #3 from Yotam Benshalom benshalom@gmail.com 2010-04-25 15:50:27 --- I use WINE version from ubuntu lucid repositories.
http://bugs.winehq.org/show_bug.cgi?id=22486
--- Comment #4 from Yotam Benshalom benshalom@gmail.com 2010-04-28 21:24:30 --- This problem was solved, for some reason, after upgrading Diablo 2: LOD from version 1.12 to 1.13.
http://bugs.winehq.org/show_bug.cgi?id=22486
Yotam Benshalom benshalom@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from Yotam Benshalom benshalom@gmail.com 2010-04-28 21:26:28 --- Since the problem was resolved with no connection to wine, I think this should be marked as invalid.
http://bugs.winehq.org/show_bug.cgi?id=22486
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-04-28 23:44:18 --- Closing invalid.