December 2023 - Wine-bugs - list.winehq.org

[Bug 56039] New: winecfg does no longer run after export WINEARCH=win32
by WineHQ Bugzilla 25 Dec '23

25 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56039 Bug ID: 56039 Summary: winecfg does no longer run after export WINEARCH=win32 Product: Wine Version: 9.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- winecfg does not run in 32 bit mode, makes it impossible to choose windows 98 emulation Steps to reproduce: $ rm -rf ~/wine-tmp/ $ mkdir ~/wine-tmp $ export WINEPREFIX=~/wine-tmp $ export WINEARCH=win32 $ winecfg wine: '/home/cedric/wine-tmp' is a 32-bit installation, it cannot support 64-bit applications. Software: $ wine --version wine-9.0-rc2 from this aur package: https://aur.archlinux.org/packages/wine-wow64 $ uname -a Linux cedric 6.6.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 14 Dec 2023 03:45:42 +0000 x86_64 GNU/Linux Running lxde on Xorg Hardware: 0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4) -- 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.

1 11

[Bug 56076] New: Detroit: Become Human crashing upon start
by WineHQ Bugzilla 25 Dec '23

25 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56076 Bug ID: 56076 Summary: Detroit: Become Human crashing upon start Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: edward.daas(a)gmail.com Created attachment 75742 --> https://bugs.winehq.org/attachment.cgi?id=75742 Screen shot of the message displayed The game displays the following message before starting: The graphic card is not officially supported by Detroit: Become Human. The game is likely to crash or fail at launch. When I launch the game anyway, the game crashes instantly. -- 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.

1 1

[Bug 56074] New: Klingon Honor Guard broken mouse input when running full screen.
by WineHQ Bugzilla 25 Dec '23

25 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56074 Bug ID: 56074 Summary: Klingon Honor Guard broken mouse input when running full screen. Product: Wine Version: 9.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fuzzy987321(a)gmail.com Distribution: --- Created attachment 75740 --> https://bugs.winehq.org/attachment.cgi?id=75740 Log when running the game in a clean prefix. When running the game Klingon Honor Guard in full screen mode, the mouse input is broken and unusable. Moving the mouse seems to work for a second, then gets 'stuck': the game ignores all input from both keyboard and mouse for a few seconds, then all inputs from this time seem to come through all at once. Input remains frozen for a few more seconds, after this mouse input goes back to normal for a bit, only to get stuck again a few seconds later. If I don't touch the mouse at all, keyboard input seems to work fine and the game runs as normal. The game doesn't freeze when the input gets stuck - you can see the environment continue to move as normal, you just can't interact with it. If a movement button is held down while the input gets stuck because you move the mouse, the game behaves as if the button continues to be held down while ignoring new inputs. If running the game in windowed and software mode by modifying the [Engine.Engine] section of the Khg.ini file and changing all of the *RenderDevice entries to say SoftDrv.SoftwareRenderDevice and then forcing to game to windowed mode by changing StartupFullscreen to False under the [WinDrv.WindowsClient] section the issue goes away. Even when setting a high custom resolution. Of course the game runs in a window without hardware acceleration then. When using OGlDrv.OpenGLRenderDevice instead, the game seems to always run full screen and only accepts a few predefined 4:3 resolutions such as 1024x768 and 1280x1024. Depending on settings, the input can be made to work, but usually is broken as described above. Setting UseFullscreen to False under the [OGlDrv.OpenGLRenderDevice] section along with setting StartupFullscreen to False under the [WinDrv.WindowsClient] section and specifying a resolution this renderer is compatible with seems to make the input work sometimes, even though the game still runs full screen. The D3DDrv.D3DRenderDevice option seems completely broken rendering the game stretched vertically or squished horizontally in the top left corner of the screen while ignoring all input. The game seems to open 2 different windows in this mode - a full screen one that the game renders in and a second transparent one with only the window decorations visible. Second one responds at least to keyboard input. If alt-tabing to this second one the game quickly refocuses the first, so this isn't at all usable. But this is likely a different issue. There is a free demo of the game available and the issue can be reproduced there. Link to free demo: https://archive.org/details/StarTrekTheNextGenerationKlingonHonorGuard_1020 -- 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.

1 0

[Bug 54305] New: riched20:editor - test_eventMask() sometimes gets the wrong event mask (0) on Windows 7
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54305 Bug ID: 54305 Summary: riched20:editor - test_eventMask() sometimes gets the wrong event mask (0) on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com riched20:editor - test_eventMask() sometimes gets the wrong event mask (0) on Windows 7: editor.c:6663: Test failed: wrong event mask (0x0) during WM_COMMAND See https://test.winehq.org/data/patterns.html#riched20:editor This looks like a race condition between making the windows visible again and querying the event mask, even though we check that IsWindowVisible() returns true. -- 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.

1 2

[Bug 54497] New: riched20:editor - The window is sometimes visible in test_eventMask() on Windows
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54497 Bug ID: 54497 Summary: riched20:editor - The window is sometimes visible in test_eventMask() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com riched20:editor - The window is sometimes visible in test_eventMask() on Windows: editor.c:6641: Test failed: Window shouldn't be visible. See https://test.winehq.org/data/patterns.html#riched20:editor This failure can happen on any Windows version from Windows 7 to 10 21H1. There are only 5 known instances over the past 6 months which makes it pretty rare: * 2022-10-18 on w10pro64v2004 32-bit * 2022-11-08 on w1064v2009 64-bit * 2022-11-09 on w7u-2qxl (32-bit) * 2022-12-22_20 w10pro64-ar 64-bit * 2023-02-15 on w7u_adm (32-bit) for MR2212 -- 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.

1 2

[Bug 54494] New: riched20:editor - test_EM_FORMATRANGE() fails on Windows in the en_AE + UTF-8 locale
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54494 Bug ID: 54494 Summary: riched20:editor - test_EM_FORMATRANGE() fails on Windows in the en_AE + UTF-8 locale Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com riched20:editor - test_EM_FORMATRANGE() fails on Windows in the en_AE + UTF-8 locale: editor.c:5741: Test failed: Expected < 9, got 10 See https://test.winehq.org/data/patterns.html#riched20:editor The failure is systematic in the en-AE-u8 locale and the invalid / expected values are always the same. Also it never happens in any of the other locales we test, including the hi-u8 one. So it's not a pure UTF-8 issue. Adding traces shows that it is the first iteration of the loop that fails, i.e. the "WINE wine" fmtstring. -- 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.

1 2

[Bug 51509] New: Shadow Warrior 2 Black Screen caused by video (mfplat)
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=51509 Bug ID: 51509 Summary: Shadow Warrior 2 Black Screen caused by video (mfplat) Product: Wine-staging Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi, Shadow Warrior 2 (Gog version) does not work anymore with Wine Staging 6.13. Wine tries to show the videos at the start of the game, but only the sound and the mouse cursor shows up, but the rest of the screen is black. The following error is displayed while that happens: 0100:err:mfplat:mf_decoder_GetOutputStreamInfo Failed to get desired output buffer size Older versions of wine simply skipped the videos and therefore the game was working fine. If you need any other infos, please let me know. Many thx ! -- 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.

1 4

[Bug 55862] New: [aarch64-musl] ws2_32.dll failed to initialize // could not load kernel32.dll
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55862 Bug ID: 55862 Summary: [aarch64-musl] ws2_32.dll failed to initialize // could not load kernel32.dll Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: winehq.org(a)life.at Distribution: --- On Alpine Linux (= musl) with either, **WINE 8.19** and current **master**, I get the same errors. It's configured like this, only lacking the mentioned dependencies: % ../configure --disable-tests --with-mingw --enable-archs=i386,aarch64 configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported. configure: libcapi20 development files not found, ISDN won't be supported. configure: libnetapi not found, Samba NetAPI won't be supported. Confirming the environment: % ./wine --version wine-8.19 % uname -m aarch64 % ldd `which ls` /lib/ld-musl-aarch64.so.1 (0xffffa0732000) Confirming libraries: % find ./ -name ws2_32.dll -o -name kernel32.dll ./dlls/kernel32/aarch64-windows/kernel32.dll ./dlls/kernel32/i386-windows/kernel32.dll ./dlls/ws2_32/aarch64-windows/ws2_32.dll ./dlls/ws2_32/i386-windows/ws2_32.dll % file dlls/kernel32/*/kernel32.dll dlls/kernel32/aarch64-windows/kernel32.dll: PE32+ executable (DLL) (GUI) Aarch64, for MS Windows, 14 sections dlls/kernel32/i386-windows/kernel32.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows, 15 sections % file dlls/ws2_32/*/ws2_32.dll dlls/ws2_32/aarch64-windows/ws2_32.dll: PE32+ executable (DLL) (GUI) Aarch64, for MS Windows, 14 sections dlls/ws2_32/i386-windows/ws2_32.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows, 15 sections The errors (same result with other exe's, like `msiexec` or `winecfg`): % rm -Rf ~/.winevanilla ; WINEPREFIX=~/.winevanilla ./wine programs/powershell/aarch64-windows/powershell.exe wine: created the configuration directory '/home/g/.winevanilla' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:err:module:loader_init "ws2_32.dll" failed to initialize, aborting 002c:err:module:loader_init Initializing dlls for L"C:\\windows\\system32\\wineboot.exe" failed, status c0000142 wine: could not load kernel32.dll, status c0000135 % rm -Rf ~/.winevanilla ; WINEPREFIX=~/.winevanilla ./wine programs/powershell/i386-windows/powershell.exe wine: created the configuration directory '/home/g/.winevanilla' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:err:module:loader_init "ws2_32.dll" failed to initialize, aborting 002c:err:module:loader_init Initializing dlls for L"C:\\windows\\system32\\wineboot.exe" failed, status c0000142 0024:err:environ:init_peb starting L"Z:\\home\\g\\Downloads\\wine\\build\\programs\\powershell\\i386-windows\\powershell.exe" in experimental wow64 mode 0024:err:module:init_wow64 could not load L"C:\\windows\\system32\\wow64.dll", status c0000135 _(Issue originally created on [Hangover](https://github.com/AndreRH/hangover/issues/141))_ -- 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.

1 7

[Bug 56029] New: After focusing the window behaves as if the left mouse button is pressed and hold.
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56029 Bug ID: 56029 Summary: After focusing the window behaves as if the left mouse button is pressed and hold. Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- Maybe this regression is already reported, but it is so strange, that I was not able to find it in the reports. The effect is that if the uses switches to WINE application by Alt-Tab for example, it behaves as if the left mouse button was pressed and hold. For example, if there is a text editor, a mouse selection starts and moving the mouse you select text as if the left mouse button is pressed. In order to stop this behavior, you need to click with some of the mouse buttons on the window (regardless of what button). In addition, sometimes after activating the window, the focus moves to the main menu as if the Alt key was pressed. These both appears on random intervals somehow related to what you do in the window. The most reproducible procedure is the following: 1. Open two "notepad" instances with text files big enough to fills the whole window. 2. Switch to the **other** notepad window by Alt-Tab, click somewhere in the text. 2.1 If the text caret moves successfully, goto 2. 2.2 If text caret simply disappears from the initial position but not appeared where you clicked, go to 3 3. Switch to the other window by Alt-Tab, move the mouse, without pressing buttons, the text is selected after the mouse cursor. This behavior stops when you press the left mouse button once on the text. Another way is to press Alt key in order to enter the main menu and then again to return to the text. -- 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.

1 3

[Bug 56071] New: Technomage Black screen No graphics or movies shown
by WineHQ Bugzilla 24 Dec '23

24 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56071 Bug ID: 56071 Summary: Technomage Black screen No graphics or movies shown Product: Wine Version: 9.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2011.ac(a)gmail.com Distribution: --- Black screen when running. Can hear movies but no graphics shown. Used to work in older wine versions (1.7 era) Demo here https://www.gamepressure.com/download.asp?ID=615 -- 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.

1 5