August 2023 - Wine-Bugs - list.winehq.org

[Bug 55471] New: nGlide wrapper produces black screen in games using the D3D backend

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55471 Bug ID: 55471 Summary: nGlide wrapper produces black screen in games using the D3D backend Product: Wine Version: 8.4 Hardware: x86-64 URL: https://archive.org/download/Wiz8b/Wiz8NetDemoEB.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 46c8a637525d0f1cf67830295fb460c819b800b6 Distribution: ArchLinux Created attachment 75029 --> https://bugs.winehq.org/attachment.cgi?id=75029 terminal output I'm using nGlide wrapper v2.10 for old games from the Win95/Win98 era that support the 3Dfx Glide renderer. The problem is that most (but not all) of the games just produce a black screen after startup if <Video backend> is set to <Auto> or <Directx> in the nGlide configurator. Vulkan backend is working properly. Some affected games are Descent 3, Die by the Sword, Ultima IX, Wizardry 8, Tachyon The Fringe, Powerslide. The problem is present since Wine 8.4 and regression testing points to commit 46c8a637525d0f1cf67830295fb460c819b800b6 winex11: Separately store the internal pixel format set by WGL_WINE_pixel_format_passthrough. To reproduce the problem in Wizardry 8 demo: 1. download and install the nGlide v2.10 wrapper: https://www.zeus-software.com/downloads/nglide/d-1.html Configuration is done by running nglide_config.exe. Video backend should be either <Auto> or <DirectX>. 2. download and install Wizardry 8 demo. First run 3Dsetup.exe from the game directory. If nGlide v2.10 is installed then you have the option to select 'Glide2x' as the renderer. 3. start the demo with Wiz8.exe. After a short intro the screen remains black. nGlide210_setup.exe (3.2 M) md5sum: cd30d314c3f1470cef1a35300fda1a20 Wiz8NetDemoEB.exe (143 M) md5sum: 728f87e9768102c71017675a1bb06425 Wine 8.14 X.Org X Server 1.21.1.8 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 535.43.08 -- 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.

Aug. 20, 2023

[Bug 55470] i686-w64-mingw32-gcc assumes wrong stack alignment

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55470 --- Comment #2 from Stefan Dösinger <stefan(a)codeweavers.com> --- Building 32 bit libs with x86_64-w64-mingw32-gcc -m32 is not really an option. It breaks in a lot of ways just linking a hello world program. It is apparently not meant to be used in this way. -- 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.

Aug. 20, 2023

[Bug 52579] MSI USB Firmware Update Tool 2.16.70 : Empty Audio IC dropdown on MSI MEG Z590 GODLIKE motherboard

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52579 Linards <linards.liepins(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins(a)gmail.com -- 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.

Aug. 20, 2023

[Bug 55470] i686-w64-mingw32-gcc assumes wrong stack alignment

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55470 --- Comment #1 from Stefan Dösinger <stefan(a)codeweavers.com> --- I have filed https://github.com/mingw-w64/mingw-w64/issues/30 , but I don't know if this is the correct place to report mingw-w64 bugs. https://www.mingw-w64.org/ points to this github repo, but it says "(Unofficial) Mirror of mingw-w64-code". -- 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.

Aug. 20, 2023

[Bug 52579] MSI USB Firmware Update Tool 2.16.70 : Empty Audio IC dropdown on MSI MEG Z590 GODLIKE motherboard

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52579 --- Comment #3 from Linards <linards.liepins(a)gmail.com> --- Issue still present with Update tool version 2.16.86. -- 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.

Aug. 20, 2023

[Bug 55470] New: i686-w64-mingw32-gcc assumes wrong stack alignment

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55470 Bug ID: 55470 Summary: i686-w64-mingw32-gcc assumes wrong stack alignment Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)codeweavers.com Distribution: --- Created attachment 75028 --> https://bugs.winehq.org/attachment.cgi?id=75028 Example C code to show the issue This is probably not a Wine bug, but something we may want to document and take care of one way or another: i686-w64-mingw32-gcc quietly assumes 16 byte stack alignment, which is wrong for Win32. To see the effect compile and disassemble the attached test.c with i686-w64-mingw32-gcc test.c -c -O2 i686-w64-mingw32-objdump -d test.o The outcome: 0: 81 ec ac 01 00 00 sub $0x1ac,%esp 6: 8d 44 24 10 lea 0x10(%esp),%eax a: 89 04 24 mov %eax,(%esp) d: e8 00 00 00 00 call 12 <_func+0x12> 12: 81 c4 ac 01 00 00 add $0x1ac,%esp 18: c3 ret However, x86_64-w64-mingw32-gcc -m32 properly aligns the stack before placing the aligned structure: x86_64-w64-mingw32-gcc test.c -c -O2 -m32 i686-w64-mingw32-objdump -d test.o 0: 55 push %ebp 1: 89 e5 mov %esp,%ebp 3: 83 e4 f0 and $0xfffffff0,%esp 6: 81 ec a0 01 00 00 sub $0x1a0,%esp c: 8d 44 24 10 lea 0x10(%esp),%eax 10: 89 04 24 mov %eax,(%esp) 13: e8 00 00 00 00 call 18 <_func+0x18> 18: c9 leave 19: c3 ret To my knowledge Wine does not use SSE instructions on purpose, so we should be mostly fine. msvcrt, wined3d or dsound (especially when compiled to use SSE to make Rosetta 2 happy) may be affected. The test.c file is attached. What can we do about it? 1) Ignore it 2) pass -mincoming-stack-boundary=2 to mingw for 32 bit targets 3) Use 64 bit target mingw with -m32 I'll file a bug for mingw too, linking this bug as reference. -- 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.

Aug. 20, 2023

[Bug 55333] ws2_32:sock - test_connect_events() sometimes fails in Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55333 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |01afb21bf2b3a9c6b03847b03a1 | |ac4a572ed49a3 CC| |fgouget(a)codeweavers.com Keywords| |regression --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- A bisect shows that this started with the commit below: commit 01afb21bf2b3a9c6b03847b03a1ac4a572ed49a3 Author: Zebediah Figura <zfigura(a)codeweavers.com> AuthorDate: Sat Jul 22 01:44:06 2023 -0500 ws2_32: Move the event reset in WSAEnumNetworkEvents() to the server. So that it is done atomically with retrieving events. Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=52474 -- 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.

Aug. 20, 2023

[Bug 34004] Broken Sword: The Angel of Death demo needs native d3dx9_36 or d3dcompiler_43

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=34004 --- Comment #22 from temp82(a)luukku.com --- (In reply to temp82 from comment #21) > wine-8.12 > no change. still all black. the same 8.14 -- 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.

Aug. 20, 2023

[Bug 55469] New: GL_OUT_OF_MEMORY crash

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55469 Bug ID: 55469 Summary: GL_OUT_OF_MEMORY crash Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Starting with Wine 8.14, after playing just a second co-op game, I receive a "GL_OUT_OF_MEMORY" error, followed by several instances of "Cannot allocate memory", followed by the typical "RtlpWaitForCriticalSection" crash I have also experienced in previous versions if I play too many matches. Not sure if the two are related, but with previous versions (up to 8.13), I was able to play a couple matches and then restart the application as a sort of workaround. -- 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.

Aug. 20, 2023

[Bug 55457] Robot Battle 1.4 crashes on startup after commit 08dc691d

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55457 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |2846111765350def595de6e9d54 | |bc33d250e808b Resolution|--- |FIXED --- Comment #5 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- (In reply to James Beddek from comment #4) > This should probably have been closed for the 8.14 release, no? What's the > policy around that, should I have included a 'Fixes' tag in the commit? This bug has to be marked resolved FIXED still. This doesn't happen automatically. Since you filed this bug, you have the ability to do this yourself. I'll mark it as such now. Thanks for your bug and patch! -- 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.

Aug. 20, 2023