http://bugs.winehq.org/show_bug.cgi?id=20362
Summary: Diablo II: X11 mouse pointer shows over fullscreen window Product: Wine Version: 1.1.31 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P4 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: thijs.vandenboogaard@gmail.com
When Diablo II is started and the mouse pointer is left alone, it stays somewhere in the upper right of the fullscreen window. While playing it gets pretty annoying. A temporary solution is to move the mouse pointer to the very right of the screen when starting. Has probably something to do with D2D.
Running Wine 1.1.31 on Ubuntu Karmic X86_64. Intel Core 2 Quad Q6600 @ 3200MHz, Nvidia Geforce GTX 260 (propretiary drivers 185.18.36).
http://bugs.winehq.org/show_bug.cgi?id=20362
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |trivial
http://bugs.winehq.org/show_bug.cgi?id=20362
James epsilon72@cox.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |epsilon72@cox.net
--- Comment #1 from James epsilon72@cox.net 2009-12-07 14:46:46 --- I am getting this problem as well, with d2d mode (not d3d) and wine versions 1.1.12 and 1.1.33 on Gentoo amd64. I have to keep moving the mouse repeatedly to the right as the game is starting up to fix it.
http://bugs.winehq.org/show_bug.cgi?id=20362
TehThyz thijs.vandenboogaard@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-ddraw Version|1.1.31 |1.1.33
http://bugs.winehq.org/show_bug.cgi?id=20362
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.33 |1.1.31
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2009-12-07 22:11:39 --- Don't change original reported Wine vesion
http://bugs.winehq.org/show_bug.cgi?id=20362
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2009-12-07 22:12:05 --- Confirming per comment 1
http://bugs.winehq.org/show_bug.cgi?id=20362
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-ddraw |-unknown
http://bugs.winehq.org/show_bug.cgi?id=20362
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #4 from Wylda wylda@volny.cz 2010-01-02 04:19:50 ---
I can't confirm this bug report. Works perfectly here, i.e. no such problems found in single player and multiplayer (battlenet) when leaving mouse cursor in different places on the screen during startup.
Tested on: * wine-1.1.12, 1.1.31, 1.1.32, 1.1.35, 1.1.35-364-g9dc584d * Diablo v1.12 * nVidia 8600GT, driver v190.53 * color depth 16 and 24bits * Debian Lenny 32bit
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #5 from Sven septim.dt@gmail.com 2010-01-02 05:21:59 --- Could be a bug in a window manager like compiz.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-01-03 06:33:45 --- Original reporter, are you using Compiz or any other desktop effects?
http://bugs.winehq.org/show_bug.cgi?id=20362
Arno Schuring aelschuring@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aelschuring@hotmail.com
--- Comment #7 from Arno Schuring aelschuring@hotmail.com 2010-01-08 17:39:02 --- I'm not the original reporter, but I'm experiencing this same issue as well (and have been for some time - I'm fairly certain that I've seen this years ago): - when the game switches to full-screen mode, it displays its intro in 640x480 and the Xserver mouse cursor is still visible on top of it (but can't be moved). If the original X cursor location was outside of the top-left 640x480 pixels, it is moved to the bottom or right edge of the screen, so it is unnoticable during the intro. - then the game switches resolution again to 800x600 (nobody plays in 640x480 nowadays), the X cursor becomes painfully visible because it's now in plain sight, even when it was hidden during the intro. - What's weird is that the X mouse cursor does not follow the in-game mouse cursor; it always stays in the same place, and always on top of the game screen, even when the in-game cursor is hidden (e.g. during loading screens). - Like comment#1 says, if you move the mouse to the bottom right exactly when the game switches from 640x480 to 800x600 (after the second intro movie), you can keep the mouse cursor out of sight during play. Otherwise, you're stuck with an immovable caret or pointer somewhere on the screen.
I'm running GNOME (metacity) without compositing. Wine version is 1.1.32 on Xorg 1.5 and using the X.org radeon driver. I also run other games on this system (Starcraft, FootballManager2008), but no other game has this issue.
@Wylda: if you're using the NVidia binary drivers, you're probably using DiabloII in 3D mode. Could you run D2VidTst.exe, switch to 2D (directdraw) mode and test again?
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #8 from Wylda wylda@volny.cz 2010-01-08 18:21:16 --- (In reply to comment #7)
@Wylda: if you're using the NVidia binary drivers, you're probably using DiabloII in 3D mode. Could you run D2VidTst.exe, switch to 2D (directdraw) mode and test again?
No i play in 2D. Because of bug 17503 you cant play 3D now. I did a retest just now. I am using screen resolution 1920x1200. I did four tests and everytime i left mouse cursor in different screen corner, but in my case, cursor disappears during movie playback. I still can't confirm this bug report.
Tested on: * wine-1.1.36 * Diablo v1.12 * nVidia 8600GT, driver v190.53 * color depth 16 and 24bits * Debian Lenny 32bit * X.org 1:7.3+20 (same like 1.3 ???)
http://bugs.winehq.org/show_bug.cgi?id=20362
Henri Kemppainen du@guu.fi changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |du@guu.fi
--- Comment #9 from Henri Kemppainen du@guu.fi 2010-02-17 13:58:29 --- A "me too" here.
Running Gentoo, I once updated a large number of packages, including Nvidia's display drivers and numerous Xorg components (I believe it was a major upgrade which brought config-free Xorg among other changes). Ever since I've experienced an unwanted X11 mouse cursor in fullscreen applications such as Stepmania (native Linux build), Prboom (native Linux build), and Diablo II (wine). In Prboom, the ghost cursor would only appear after switching to another TTY and back, but otherwise the problem remains identical.
I switched to Debian Squeeze and the problem persists (although I've only tested Diablo II under Wine). I can also reproduce the problem on another machine w/ATI display card, running Ubuntu 9.10.
Googling turns up similar problem reports with native Linux applications. Wine bug #21524 might be related.
http://bugs.winehq.org/show_bug.cgi?id=20362
Fred fred@alternation.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fred@alternation.fr
--- Comment #10 from Fred fred@alternation.fr 2010-03-23 05:55:28 --- Hi, I've met a kind of similar bug, but not with Diablo II, as I'm not playing it. It is with the games "The Heat of War" and "Call of Duty 2", but with the last one, it was not there with Wine 1.1.28.
The X11 mouse pointer shows over fullscreen window in a bunch of applications, most of them being games (but not only it seems with Wine bug #21524)!
It's important to say that problem NEVER EVER shows in windowed mode, but ONLY in fullscreen and that it is not there in Windows (whatever version)!
So the bug affects Wine:
Version 1.1.41 (with the game "Call of Duty 2" on OpenSuse 11.2 x86_64 + KDE4).
I've seen it first in Wine:
Version 1.1.36 (with the game "The Heat of War" on Fedora 12 x86_64 + Gnome).
It doesn't affects Wine:
Version 1.1.28 (with the game "Call of Duty 2" on OpenSuse 11.2 x86_64 + KDE4)
Two workarounds:
- Or quickly moving the cursor as the game is launched (tricky to achieve & look stupid =;)
- Or using a WM (Fluxbox for exemple doesn't have that problem) other than Gnome or KDE, as it looked related to in both cases.
Then, I've found by the Ubuntu forums that the problem is even bigger:
- http://ubuntuforums.org/showthread.php?t=988573
- http://ubuntuforums.org/showthread.php?t=925046
and that there is also something similar in Quake Live: http://bugs.winehq.org/show_bug.cgi?id=17746 (that one being closed invalid, where it doesn't really seems to be the case).
Do you guys having the problem all use x86_64 Linux? I will give a try of one of this game on a i686 box, just to see if it's not x86_64 related and keep you informed...
http://bugs.winehq.org/show_bug.cgi?id=20362
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #11 from Vitaliy Margolen vitaliy@kievinfo.com 2010-03-23 08:56:26 --- *** Bug 22126 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #12 from Henri Kemppainen du@guu.fi 2010-03-23 09:22:28 --- (In reply to comment #10)
- Or using a WM (Fluxbox for exemple doesn't have that problem) other than
Gnome or KDE, as it looked related to in both cases.
On all my installations I've had this problem on, it happens with Fluxbox too. Normally I don't use any WM at all.
Do you guys having the problem all use x86_64 Linux? I will give a try of one of this game on a i686 box, just to see if it's not x86_64 related and keep you informed...
The problem is there on both x86_64 and i686.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #13 from Fred fred@alternation.fr 2010-03-23 09:44:56 ---
The problem is there on both x86_64 and i686.
Strange, because I've just tested Call of Duty 2 on a i686 box and there's NO "ghost mouse pointer" so it looks like that, in my case, it's something affecting ONLY x86_64 systems, with Gnome or KDE4, but NOT Fluxbox!
That would explains the fact that the user from comment #4 & #8 doesn't see the bug, as he uses Debian Lenny 32bit
Then, the bug should be hidden in some x86_64 libraries that Gnome & KDE4 have in common, but that Fluxbox doesn't use...
Perhaps in the 3D Desktop effects parts (even if you don't activate them), as Fluxbox is not supposed to be accelerated, if I'm right?
On all my installations I've had this problem on, it happens with Fluxbox too. Normally I don't use any WM at all.
mmh, that put then my idea to the ground =:(
The only thing I can add is that it's not hardware related, as I've seen it on Intel GM45 and Nvidia Geforce 7600GT...
http://bugs.winehq.org/show_bug.cgi?id=20362
Randy cinco_flare@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cinco_flare@hotmail.com
--- Comment #14 from Randy cinco_flare@hotmail.com 2010-04-25 16:47:30 --- Now that bug 17503 is fixed, I have recently been using the Direct 3D setting in video test and I am having the same issue. The x11 cursor spears in one spot and doesn't move. Sometimes I can get the pointer to go off the screen but it's difficult. I tested using Direct Draw and it's the same. I was using a Glide wrapper before the Direct 3D problem was fixed and I was also experiencing this problem but not to the same extent. Using the wrapper, if I left the mouse in the lower right corner of my screen before even starting the game then (most times) it would not appear in the game. Every once in a while it would show up but in that case I would just restart the game and try again and it would work. In all three video modes though, if you leave the pointer near the top left the the screen before starting the game, it shows up at the top left corner.
Using - Kubuntu Karmic - Wine 1.1.43 - Nvidia GeForce GTX 260 - Desktop Resolution 1280x1024 - compositing turned off I have another program called Play Online Viewer and it has it's own cursor too. If I run it in full screen mode then my x11 cursor doesn't appear as it does in diablo. So I wonder what's the difference.
http://bugs.winehq.org/show_bug.cgi?id=20362
DL taedium_vitae@eml.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |taedium_vitae@eml.cc
--- Comment #15 from DL taedium_vitae@eml.cc 2010-05-14 21:08:45 --- I can confirm that this bug also occurs with Fable : The Lost Chapters with wine-1.1.44. Also, as Fred said, that COD2 ran properly with older wine versions such as wine-1.1.34, but has the mouse bug with 1.1.44. I'll try and get around to running a regression test for COD2.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #16 from DL taedium_vitae@eml.cc 2010-05-15 00:29:11 --- OK, this bug does not occur for me when virtual desktop mode is enabled, so that can be considered a workaround.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #17 from DL taedium_vitae@eml.cc 2010-05-15 05:49:02 --- Okay, I did a couple of regression tests but I have been getting a different result each time. Perhaps I typed the wrong git bisect bad/good in both cases, but I don't think so. I'll try and get around to doing it one more time tomorrow.
I am pretty sure that the regression is somewhere in the 1.1.40/41 versions, though.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #18 from DL taedium_vitae@eml.cc 2010-05-15 09:58:04 --- Okay, this time the regression test got to a string of cursor related patches, but the game crashed when trying to launch COD2 with this message:
X Error of failed request: BadCursor (invalid Cursor parameter) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Resource id in failed request: 0xe00083 Serial number of failed request: 148 Current serial number in output stream: 166
It wouldn't let me bisect further: There are only 'skip'ped commits left to test. The first bad commit could be any of: 3044d734b1cd84746cc57ace8b79a156ea9391b1 776527f38f2ff89f354e49aa8df795440677376a cd28e2be7c79644e02babb509247a453e0153390 eed9c63ac7650293523da5c8d067c74258568ba8 We cannot bisect more!
So I assume these patches are the cause of the issue.
http://bugs.winehq.org/show_bug.cgi?id=20362
Claudio sick_soul@yahoo.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sick_soul@yahoo.it
--- Comment #19 from Claudio sick_soul@yahoo.it 2010-05-17 12:10:47 --- I have this same issue:
the X11 pointer shows over the game window.
wine 1.1.44, linux 2.6.27.45 on x86, nvidia card, X.Org X Server 1.6.3. I use fluxbox as my window manager.
The X11 pointer follows around every action, and is quite annoying.
To work around this problem I ALT+click the window, move it on the side, then change to a higher resolution (which "minimizes" the Diablo II window), and change back to the playing resolution, and click the Diablo II icon.
http://bugs.winehq.org/show_bug.cgi?id=20362
Manuel Soukup linuxuser-sky@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxuser-sky@gmx.de
--- Comment #20 from Manuel Soukup linuxuser-sky@gmx.de 2010-05-24 11:59:51 --- Hi
I can confirm this bug with wine 1.1.44 and Sidux 64 bit
the X11 pointer shows over the game window.
wine 1.1.44, Linux think 2.6.34-0.slh.4-sidux-amd64 on x86_64, ati card, X.Org X Server 1.7.7. I use openbox as window manager.
The X11 pointer follows around every action.
My work around is to start the game in a virtual desktop with 800x600 and change the game res to the same size then i change my res with xrandr to is and i can play without annoying bug.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #21 from Henri Kemppainen du@guu.fi 2010-05-25 13:32:35 --- These might or might not be relevant, but I'm linking to a few forum threads here so I won't need to google them again when I want to track and see if there's helpful information. There's at least one more thread (possibly on another forum) I would've liked to find -- on it they mentioned how the unwanted cursor appears after switching VTs (this is a big problem for me; I run games on another X server, and would like to switch to the primary desktop every once in a while without triggering the bug).
On the second page of the first thread, they point out a curious fix: add some delay before the call to hide the mouse cursor. I've noticed that the mode-switching delay (when a game switches resolution or I switch VT) goes hand-in-hand with this bug, and that eliminating some mode switches can reduce the frequency of triggering this bug.
http://ubuntuforums.org/showthread.php?t=925046 http://ubuntuforums.org/showthread.php?t=980592 http://ubuntuforums.org/showthread.php?t=1058375 http://ubuntuforums.org/showthread.php?t=916046 http://ubuntuforums.org/showthread.php?t=1279001 http://ubuntuforums.org/showthread.php?t=1199354 http://ubuntuforums.org/showthread.php?t=1096036 http://ubuntuforums.org/showthread.php?t=988573 http://ubuntuforums.org/showthread.php?t=936670 http://ubuntuforums.org/showthread.php?t=789416
Sadly there's no common denominator in the information gathered. For some, disabling compiz seems to help. For some, this problem seems to occur with intel drivers only. For some, it's a gnome issue, and for some it's something else. Sigh.
http://bugs.winehq.org/show_bug.cgi?id=20362
Major András majorandras@freemail.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |majorandras@freemail.hu
http://bugs.winehq.org/show_bug.cgi?id=20362
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #22 from Xavier Vachon xvachon@gmail.com 2010-07-19 18:41:04 --- In current git (1.2), I do not experience these behaviours with the mouse pointer in Diablo 2.
Gentoo Linux X64 KDE 4.4.5 nvidia-drivers 256.35
Can someone else test and confirm?
http://bugs.winehq.org/show_bug.cgi?id=20362
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |0bhamid0@gmail.com
--- Comment #23 from Dmitry Timoshkov dmitry@codeweavers.com 2010-08-27 02:11:42 --- *** Bug 24163 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #24 from Alexandre Julliard julliard@winehq.org 2010-10-13 10:14:35 CDT --- Probably fixed by 536fc57091a80135ac1d6a3fceda3e7a87389897. Please confirm.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #25 from GyB gyebro69@gmail.com 2010-10-13 11:05:20 CDT --- I don't have Diablo II, but bug #22126 was marked as a duplicate of this bugreport. In Aztaka the issue is still not fixed, using wine-1.3.4-314-g5019592. A white arrow pointer is always on the screen and tries to follow the game's native mouse pointer, but it is confined into a small rectangle area in the center of the screen.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #26 from Randy cinco_flare@hotmail.com 2010-11-03 15:30:48 CDT --- Still present in wine 1.3.6
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #27 from GyB gyebro69@gmail.com 2011-07-10 12:07:15 CDT --- The desktop mouse pointer is still visible during gameplay in Aztaka, using Wine-1.3.24. The only change I see with versions >1.3.18 is that the pointer is now completely stuck in the middle of the screen (doesn't try to follow the game's native pointer).
Fedora 15 Gnome 3 + Mutter as WM Xserver 1.10.2
http://bugs.winehq.org/show_bug.cgi?id=20362
Alexey Loukianov mooroon2@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mooroon2@mail.ru
--- Comment #28 from Alexey Loukianov mooroon2@mail.ru 2011-09-23 18:20:49 CDT --- Correct me if I'm wrong but this bug is about Diablo II and not about Aztaka. I can't reproduce it with 1.3.28 (and, actually, never been able to reproduce it since around 1.2 release). What's about the exact instructions to reproduce it? I suspect that it might had been fixed long ago.
http://bugs.winehq.org/show_bug.cgi?id=20362
Mike Mestnik cheako+winehq@mikemestnik.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cheako+winehq@mikemestnik.n | |et
--- Comment #29 from Mike Mestnik cheako+winehq@mikemestnik.net 2012-04-16 19:17:15 CDT --- Mouse Jumps All Over... from the appdb. Relevant information copied here.
by Jason Marty on Friday March 30th 2012, 23:49 Running an up-to-date version of Arch Linux with the latest wine. It seems this might be an issue with some other library/package, because even the version of Wine that use to work fine for me with this game no longer works.
by Mike Mestnik on Sunday April 15th 2012, 1:53 I get the same issue running 1.4 and I just upgraded to 1.5.2. However for me mouse clicks are erratic, choosing the currently active location.
by Mike Mestnik on Monday April 16th 2012, 15:15 This is Ubuntu precise, x86-32.
X.Org X Server 1.11.3 Release Date: 2011-12-16 Build Date: 21 March 2012 06:09:11AM xorg-server 2:1.11.4-0ubuntu7 (For technical support please see www.ubuntu.com/support) X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 11.0 X.Org XInput driver : 16.0 X.Org Server Extension : 6.0
Using xrandr didn't help. However I did discover that including the menus the in-game menu is also un-effected, thus only when the game board has focus is there an issue. This presents an easy platform to test things as one can activate/deactivate the bug with vary few other changes. I'll see what else I can glean.
I've just recompiled wine from *git and applied the 3 patches for Diablo III and the changes from the wine/ppa and AFAICT these are working.
I'd be happy to test other patches.
* git log commit c8495104a9552095037cb15f54ed5939669cf83c Author: root Date: Sun Apr 15 10:58:38 2012 -0500
Mike mestnik migrate to debian src.
commit 0ccd06158b9916543d3a983ad7c19aba4c5a7525 Author: root Date: Sun Apr 15 10:57:49 2012 -0500
Mike mestnik debian patches 2.
commit 2e3aaf2ae5c2d971ab03e80fae4d0199f1b8903c Author: root Date: Sun Apr 15 10:57:04 2012 -0500
Mike mestnik debian patches.
commit a014a68b8b381703043846e6bf81ddc15ae3c973 Author: root Date: Sun Apr 15 10:54:06 2012 -0500
Mike mestnik D3 patches.
commit c6a673291da6e9ee956910f35efcde0a8d8437ea Author: Alexandre Julliard Date: Fri Apr 13 20:15:32 2012 +0200
Release 1.5.2.
by Mike Mestnik on Monday April 16th 2012, 19:08 I have some more information, remember reading I said the 'ghosted' positions formed a rectangle? Well check this out:
Of the 4 locations x(1):y(1) to x(4):y(4) x(1)=x x(2)=x*2 x(3)=x x(4)=x*2
y(1)=y y(2)=y y(3)=y*2 y(4)=y*2
When the mouse is in the upper left corner the 4 locations are vary close together and when the mouse is near the center the 3 other ghost locations are near the bottom and right of the screen. As indicated x(1):y(1) seams to track the 'original'/intended mouse location vary well.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #30 from Alexey Loukianov mooroon2@mail.ru 2012-04-17 01:33:49 CDT --- Mike, I'm afraid but the info you post is a bit... em... a mess. What are the patches you apply to your Wine tree and why do you do it? What about "stock vanilla" Wine without any patches, does it work or not? If not - had you tried to compile it with XInput2 turned off (in case it had been turned on before, an vise verso) and check if that helps? Does this happen always, including when Wine is configured to be run in "Virtual Desktop" mode, or when the game itself is configured to be run in windows?
The behavior you observe might be related to a bug #29871. Try to recompile your Wine with the commit cb3b723 reversed and check if that helps. In case you've got the input messed in all Wine versions, even in those which had been working perfectly before - most likely it is not a Wine fault, but rather a bug in one of the system components, like Xserver, libxi or Xorg input drivers. Try to rollback relevant Xorg packages to a state they were at, say, year or two ago and check if that would fix the issue.
In any case, the bug you are trying describe in your comment is by no means not a one this bugreport is about. Please, do the checks I had described in previous sentences and if the problem persists - fire up another bugreport with a detailed description about "what, where and why", attache relevant debug logs, e.t.c. There's no point in hi-jacking non-related bugreport, it won't be welcome.
http://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #31 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.18 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=20362
BastyJuice Bastyjuice@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Bastyjuice@aol.com
--- Comment #32 from BastyJuice Bastyjuice@aol.com --- Yes it is
https://bugs.winehq.org/show_bug.cgi?id=20362
--- Comment #33 from Béla Gyebrószki gyebro69@gmail.com --- I don't own Diablo II, but the problem is still present in the game Aztaka with Wine 1.7.40. Aztaka has a demo (~900 MB download): http://www.gamershell.com/download_45600.shtml
I have similar problem in the indie game 'Foresight' where the X11 mouse pointer is always visible on the screen and it's moving along with the game's own mouse pointer.
Fedora 21 XOrg 1.16.3 XFCE 4.10
https://bugs.winehq.org/show_bug.cgi?id=20362
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #34 from super_man@post.com --- This cant be tested with diablo 2 demo, it has other issues that prevents using it. Palette could not be found or something like that.
https://bugs.winehq.org/show_bug.cgi?id=20362
BastyJuice Bastyjuice@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|Bastyjuice@aol.com |
https://bugs.winehq.org/show_bug.cgi?id=20362
Chebanenko Igor chebanenkoigor93@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chebanenkoigor93@gmail.com
--- Comment #35 from Chebanenko Igor chebanenkoigor93@gmail.com --- Please,test your game in Wine 6.9
https://bugs.winehq.org/show_bug.cgi?id=20362
Jeff D. Hanson jhansonxi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jhansonxi@gmail.com
--- Comment #36 from Jeff D. Hanson jhansonxi@gmail.com --- Not able to reproduce on Xubuntu 20.04.3 x86_64 with Wine v7 and Diablo II v1.07 or Diablo II LoD v1.14d. GeForce GTX 750 Ti using Nvidia 470.57.02 driver. Game video modes (DirectDraw, Direct3D, 3dfx Glide) selected using D2VidTst.exe and verified in the registry (educated guess based on value changes). Cursor changed to game version at launch (with stationary cursor) and whenever game had focus or cursor moved into game screen boundary (multiple monitors).
-
wine-bugs＠winehq.org -
WineHQ Bugzilla