[Bug 30141] New: 1848 (strategy game) becomes unresponsive after the first mouse click
http://bugs.winehq.org/show_bug.cgi?id=30141 Bug #: 30141 Summary: 1848 (strategy game) becomes unresponsive after the first mouse click Product: Wine Version: 1.4 Platform: x86 URL: http://www.gamershell.com/download_17042.shtml OS/Version: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Classification: Unclassified Regression SHA1: 94c0da184e18252ca2df7f9f462e9a4df9c5f2df 1848 is a freeware, historical strategy game taking place during the Hungarian Independence War of 1848/49. The next game from the developer is also affected by this bug (For the Glory!). The problem: a new game can be started from the menus, but as soon as I click with the mouse on the game screen, the game becomes unresponsive: music and animations keep playing but the game no longer responds to mouse or keyboard. Terminal output isn't too informative:
fixme:win:EnumDisplayDevicesW ((null),0,0x32ec20,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x14dc08, flags 0x1, event (nil) stub!
The problem appeared in Wine-1.3.34 and is still present as of wine-1.4-78-g94953f1. 94c0da184e18252ca2df7f9f462e9a4df9c5f2df is the first bad commit commit 94c0da184e18252ca2df7f9f462e9a4df9c5f2df Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Thu Dec 1 07:31:41 2011 +0100 wined3d: Create a PBO in surface_load_location() even if SFLAG_INSYSMEM is already set. In the longer term, sysmem and pbo should be separate resource locations. :040000 040000 0ea129726096c1508557eacfc8272cf884f0c61b 4e1bfdfeccfc95e0b700f75d6841dbb7cc1889da M dlls Other bugs related to this commit: bug #29287, bug #29613. Although the commit can be reverted cleanly on current git, I noticed that - reverting on 1.4 doesn't fix the problem for some reason - reverting on 1.3.37 does fixes the problem Steps to reproduce the problem: 1. install the game as usual. 2. start the game with 1848.exe 3. in the main menu choose <Single Player>, then select the Tutorial Campaign and click on the <Start> button, located in the lower right corner of the screen. 4. close the Events window and left click anywhere on the main game screen (not on the minimap). The game no longer responds to mouse or keyboard input. Fedora 16 Nvidia 250 / driver 290.10 X.Org X Server 1.11.4 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #1 from GyB <gyebro69(a)gmail.com> 2012-05-28 04:46:15 CDT --- Still present in 1.5.5. Now I tested the game with the open source Nouveau driver, and the problem persists with that as well. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #2 from Henri Verbeet <hverbeet(a)gmail.com> 2013-05-20 05:26:30 CDT --- Does this happen in a virtual desktop as well? I'm not sure I can reproduce this. Without virtual desktop I see some window management quirks, but they don't seem related to the commit mentioned here. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #3 from GyB <gyebro69(a)gmail.com> 2013-05-20 06:19:25 CDT --- (In reply to comment #2)
Does this happen in a virtual desktop as well? I'm not sure I can reproduce this. Without virtual desktop I see some window management quirks, but they don't seem related to the commit mentioned here.
The problem is still present in wine-1.5.30-148-gd29f6c4 when using a VD. In full screen mode I can't even get past the main menu as clicking on the <Single player> button has no effect. In virtual desktop mode I can start a new game but as soon as I left-click on the map the game becomes unresponsive. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #4 from Henri Verbeet <hverbeet(a)gmail.com> 2013-05-20 07:18:33 CDT --- (In reply to comment #3)
In full screen mode I can't even get past the main menu as clicking on the <Single player> button has no effect. That sounds sort of like what I'm seeing with kwin. What actually happens for me there is that the game opens a popup window that gets the input focus, but ends up below the main window. Moving the main window (e.g. with alt+click) away makes the popup visible and allows to continue.
With fvwm the main window starts as 320x240, and I get a popup saying something along the lines of the minimum display mode being 1024x768. What happens is that the window is created with size 320x240, but with WS_MAXIMIZE set. We end up setting NET_WM_STATE_FULLSCREEN on the window, but because it's a transient window fvwm doesn't consider it maximizable, and it ends up as 320x240 instead. I suppose that's a fvwm bug, although perhaps setting NET_WM_STATE_FULLSCREEN on a transient window is a bit questionable as well.
In virtual desktop mode I can start a new game but as soon as I left-click on the map the game becomes unresponsive. In virtual desktop it seems to work fine for me. (I tried on different hardware as well.) I'm not quite sure what kind of difference in setup could cause this.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #5 from GyB <gyebro69(a)gmail.com> 2013-05-20 07:41:49 CDT --- I tested this bug under Gnome 3 and XFCE 4.10 with the same result when using a VD. Nvidia binary drivers 319.17, X.Org X Server 1.13.3. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- I can't reproduce this on wine 1.4.1 or 1.7.30, mesa 10.4 with an intel i965. Can someone affected please retest? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- I can confirm this issue, the game runs well in wine 1.3.22 but not in 1.7.30. Tested with and without VD. XFCE 4.10, mesa 10.3. No relevant console output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #8 from super_man(a)post.com --- (In reply to Bruno Jesus from comment #7)
I can confirm this issue, the game runs well in wine 1.3.22 but not in 1.7.30. Tested with and without VD. XFCE 4.10, mesa 10.3. No relevant console output.
Kde, wine 1.9.7-git, wine-staging 1.9.7 still valid issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #9 from joaopa <jeremielapuree(a)yahoo.fr> --- bug still there in current wine with kubuntu 16.10 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 --- Comment #10 from joaopa <jeremielapuree(a)yahoo.fr> --- Still a bug in current wine (3.11)? I tested the demo, but I can not understand the game https://archive.org/details/1848_game -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |82a7f1ebf2979a3c6a4b6ca8fcc | |2679f2278f6e6 Status|NEW |RESOLVED --- Comment #11 from Béla Gyebrószki <gyebro69(a)gmail.com> --- The game works reasonably well in 3.12 when using a virtual desktop, and the game-breaking bug that made the game unresponsive after clicking on the map is gone. Some problems still exist, but I believe those need separate bug reports: * in Wine traditional fullscreen mode the game is unusable, because on the title screen out of the 4 menu options (SinglePlayer, Multiplayer, Options, Exit) only the <Exit> option is selectable. * in virtual desktop mode I noticed that whenever a new popup window is opened, the game custom mouse pointer turns into the default X11 cursor and no selection can be made until I <Alt-Tab> to the desktop then back to the game. This trick with <Alt-Tab> works in vanilla Wine, but not in Wine-Staging for some reason. The commit which fixed the originally reported problem: https://source.winehq.org/git/wine.git/commit/82a7f1ebf2979a3c6a4b6ca8fcc267... Testing was done on Arch Linux using XFCE/XFWM 4.12 as window manager and with Nvidia binary drivers 396.24. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30141 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #12 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.13. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org