March 2021 - Wine-bugs - list.winehq.org

[Bug 49393] New: Gag game crash
by WineHQ Bugzilla 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=49393 Bug ID: 49393 Summary: Gag game crash Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Hello! I'm trying to run 'Gag' game. And it's crashing winmm reading at zero memory address. I've tested few wine versions 5.0.0 .. 5.10 and all have same issue. https://en.wikipedia.org/wiki/GAG_The_Impotent_Mystery If you want trying to run the game, you gonna need start X server with 16-bit display like this: Xephyr :1 -ac -screen 800x600x16 & Crash output: 5.10 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7db6). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7db6 ESP:016cf7c0 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00ca3e08 ECX:016cf760 EDX:000001d0 ESI:00000000 EDI:014afb1c Stack dump: 0x016cf7c0: 009b38b8 639ec090 00000001 00000000 0x016cf7d0: 00ca3e24 00000000 00000000 639d85b5 0x016cf7e0: 00ca3ed4 00000008 000000e8 7ea09ea0 0x016cf7f0: 00000001 016cf810 016cf8cc 016cf820 0x016cf800: 0000001c 7ffc4000 0000003f 00ca0cf0 0x016cf810: 00ca0cf0 016cf830 639efe20 00ca3e08 Backtrace: =>0 0x639d7db6 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8688 EntryPoint+0xffffffff() in winmm (0x00ca3ed4) 2 0x639da5b9 EntryPoint+0xffffffff() in winmm (0x016cf918) 3 0x7ea1bd0c in user32 (+0x9bd0b) (0x016cf918) 4 0x7ea1c35d in user32 (+0x9c35c) (0x016cf968) 5 0x7ea1e5a3 in user32 (+0x9e5a2) (0x016cf9b8) 6 0x7e9db0f2 in user32 (+0x5b0f1) (0x016cfa28) 7 0x7e9dd6c7 in user32 (+0x5d6c6) (0x016cfe48) 8 0x7e9e32df in user32 (+0x632de) (0x016cfea8) 9 0x639d9949 EntryPoint+0xffffffff() in winmm (0x016cff5c) 0x639d7db6 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) 5.0.0 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7b36). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7b36 ESP:0127f700 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:0089e300 ECX:0127f6a0 EDX:0089e678 ESI:00000000 EDI:0105fb0c Stack dump: 0x0127f700: 0089c3c8 639eb090 00000001 00000000 0x0127f710: 0089e31c 00000000 00000000 639d8335 0x0127f720: 0089e3cc 00000008 000000e8 0127f750 0x0127f730: 0000000c 00030038 0127f768 7e925c50 0x0127f740: 7ea78cc0 7ffc4000 0000003f 0089c9f0 0x0127f750: 0089c9f0 0127f770 639eee20 0089e300 Backtrace: =>0 0x639d7b36 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8408 EntryPoint+0xffffffff() in winmm (0x0089e3cc) 2 0x639da339 EntryPoint+0xffffffff() in winmm (0x0127f858) 3 0x7e93863c in user32 (+0xa863b) (0x0127f858) 4 0x7e938cad in user32 (+0xa8cac) (0x0127f8a8) 5 0x7e93b113 in user32 (+0xab112) (0x0127f8f8) 6 0x7e8f635e in user32 (+0x6635d) (0x0127f968) 7 0x7e8f8a7f in user32 (+0x68a7e) (0x0127fe38) 8 0x7e8fedca in user32 (+0x6edc9) (0x0127fe98) 9 0x639d96c9 EntryPoint+0xffffffff() in winmm (0x0127ff4c) 0x639d7b36 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) -- 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.

2 4

[Bug 45882] New: (Overwatch, several source games) Raw Mouse input not working
by wine-bugs＠winehq.org 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=45882 Bug ID: 45882 Summary: (Overwatch, several source games) Raw Mouse input not working Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florian98.rg(a)gmail.com Distribution: --- Playing Overwatch I've noticed that the game still uses mouse pointer speed even though on Windows it uses Raw Mouse input exclusively. I've tried this on any branch of Wine (staging, esync, whatsoever) and the problem still persists. This also happens in Valve games where you can enable Raw Mouse Input, e.g. Team Fortress 2 etc. This does not happen with the native ports of said games that use SDL to get mouse input. I already disabled any mouse acceleration in GNOME whatsoever (using the "Flat" Profile), however the problem persists. Is it possible to rewrite Wine to get Mouse input via SDL2 instead? That would help pave way for Wayland etc. Thanks -- 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.

3 34

[Bug 46534] New: Just Cause 4 crashes on startup
by wine-bugs＠winehq.org 24 Feb '26

24 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=46534 Bug ID: 46534 Summary: Just Cause 4 crashes on startup Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ramy0zahran(a)gmail.com Distribution: --- Created attachment 63387 --> https://bugs.winehq.org/attachment.cgi?id=63387 JC4backtrace Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x0000000141926167). -- 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.

3 19

[Bug 31899] New: No keyboard input in La-Mulana remake
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=31899 Bug #: 31899 Summary: No keyboard input in La-Mulana remake Product: Wine Version: 1.5.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: twwinwood(a)gmail.com Classification: Unclassified Created attachment 41993 --> http://bugs.winehq.org/attachment.cgi?id=41993 Output of "env WINEDEBUG=-all,+keyboard,+key,+dinput,+message wine LaMulanaWin.exe" Per the AppDB entry for version 1.1.1.1, the game works as far as the menu screen but cannot be played due to the lack of response to keyboard input. -- 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.

3 26

[Bug 35907] New: Caps Lock state gets confused with multiple processes/threads
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=35907 Bug ID: 35907 Summary: Caps Lock state gets confused with multiple processes/threads Product: Wine Version: 1.7.15 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: ken(a)codeweavers.com Open two instances of Notepad in the same prefix: wine notepad & wine notepad & With one Notepad window active, turn Caps Lock on. Switch to the other Notepad window. Type some text. Notice it's not capitalized, although it should be. Turn Caps Lock off. Type some text. Notice that it is capitalized, although it shouldn't be. Switch back to the first Notepad window. Type some text. Notice that it is capitalized, although it shouldn't be. -- 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.

3 15

[Bug 45385] New: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected.
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=45385 Bug ID: 45385 Summary: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected. Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- I noticed that the state of the keys sometimes sticks in pressed state. This happens when cycling windows with some shortcut key combination. For example if cycling with Alt+Tab, on pressing Alt, the program gets WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling windows, the program does not get WM_KEYUP because the window is not focused and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state. When cycling back to the program window, the window get focused only after releasing Alt key, so it does not get this event as well. If cycling windows with another shortcut key combination (for example Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick. In the same time, GetAsyncKeyState returns the proper state of the keys. Note1: The problem is obviously in the wineserver code, because it handles the key state tables for the different threads. Note2: The effect happens only sometimes. It seems the code for proper processing is already there, but some racing conditions have place. Note3: There is some probability that the effect is in result of my application code, but it never happens on real Windows, so I considered it a bug. Note4: I tried to workaround this problem by reading the whole table by GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE message of the main window. This workaround actually works, but is too ugly IMO. The same trick on WM_ACTIVATEAPP does not work. -- 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.

3 4

[Bug 26269] New: BioShock 2: Loss of keyboard input on loading screen
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=26269 Summary: BioShock 2: Loss of keyboard input on loading screen Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: mgavl69(a)juno.com Created an attachment (id=33488) --> (http://bugs.winehq.org/attachment.cgi?id=33488) trace +keyboard On the inital 'New Game' loading screen you cannot use the space bar to continue. Keyboard and mouse input is recognised correctly when adjusting settings in the menus. Wine version 1.3.14-git Xserver v1.10.0 -- 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.

3 33

[Bug 37966] New: xrandr12 regression for nvidia users across a range of applications (too many to list)
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=37966 Bug ID: 37966 Summary: xrandr12 regression for nvidia users across a range of applications (too many to list) Product: Wine Version: 1.7.35 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Dead Space 3: "Your Graphics Card does not meet Dead SpaceTM 3 minimum requirements." Call of Juaraz: "Failed to initialize rendering device. Check if your graphic card supports DirectX 9.0c" Overlord: Unhandled exception Overlord II Unhandled exception ...surely many more but you get the idea. Reverting commit 8e9e4a657f29ff018c6296ced1f115ca8731e5e6 (introduced in 1.7.35) makes all these problems go away. Furthermore, this commit introduces all the warnings reported in bug 34348. I have never seen these warnings produced on my Nvidia-based laptop prior to 1.7.35, and I now get them even when not running a 3D application (eg. cmd.exe). Nvidia GTX660M nvidia 346.35 driver $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.9*+ 39.9 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) Let me know if there's anything else you need. -- 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.

3 16

[Bug 26898] New: wine does not show save game screenshots
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=26898 Summary: wine does not show save game screenshots Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: vaniaz(a)msn.com Screenshots are saved in dds format. When saving game, I get the following in console fixme:d3d_surface:surface_convert_format Cannot find a conversion function from format WINED3DFMT_B8G8R8A8_UNORM to WINED3DFMT_DXT1. Saved screenshot is completely black. -- 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.

3 35

[Bug 23166] New: X-Blade's launcher does not display background, button images and cannot be closed.
by wine-bugs＠winehq.org 23 Feb '26

23 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=23166 Summary: X-Blade's launcher does not display background, button images and cannot be closed. Product: Wine Version: 1.2-rc3 Platform: x86 URL: http://games.on.net/file/25712/X-Blades_Demo OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrew.millington(a)gmail.com The launcher does not display *the background instead it displays gray background *the images for the buttons instead it displays generic Window's buttons plus you cannot close the launcher eg "Exit" or "Run Game". Both appear to be in a launcher.dat file body.bmp (background) /img/*.png (button images) Installing Internet Explorer 6 allows the images to displayed and you can close the launcher -- 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.

3 25