June 2021 - Wine-Bugs - list.winehq.org

[Bug 50596] New: Sacred 2 crashes with D3DXCompileShader (d3dx9_36 builtin)
by WineHQ Bugzilla Feb. 5, 2023

Feb. 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=50596 Bug ID: 50596 Summary: Sacred 2 crashes with D3DXCompileShader (d3dx9_36 builtin) Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 69281 --> https://bugs.winehq.org/attachment.cgi?id=69281 +d3dx log Hi, The game crashes at launch with this trace before crash : ------ 0024:trace:d3dx:D3DXCompileShader data "#include \"ui_include.shader\"\n\n\nstruct pixdata {\n\tfloat4 hposition : POSITION;\n\tfloat4 texcoord0 : TEXCOORD0;\n\tfloat4 texcoord1 : TEXCOORD1;\n\tfloat4 texcoord2 : TEXCOORD2;\n\tfloat4 light_dir : TEXCOORD3;\n\tfloat4 color : COLOR;\n};\n\n\nstruct fragout {\n\tfloat4 col "..., length 1410, defines 00000000, include 0031E318, function "mainVS", profile "vs_1_1", flags 0, shader 0031E330, error_msgs 0031E310, constant_table 0031E308. ------ Set d3dx9_36 to native fix the issue. I attach +d3dx log -- 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 45884] New: Just Cause 2 crashed at start
by wine-bugs＠winehq.org Feb. 5, 2023

Feb. 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=45884 Bug ID: 45884 Summary: Just Cause 2 crashed at start Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 62390 --> https://bugs.winehq.org/attachment.cgi?id=62390 Just Cause 2 crashed at start terminal log Hello, Just Cause II crashed at start, you can reproduce this crash at each launch. I joined you the log terminal. Thank you for your help. LGDN. -- 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 7

[Bug 40569] New: application crashes with exception in ddraw_allocate_handle (win98)
by wine-bugs＠winehq.org Feb. 5, 2023

Feb. 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=40569 Bug ID: 40569 Summary: application crashes with exception in ddraw_allocate_handle (win98) Product: Wine Version: 1.9.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 54407 --> https://bugs.winehq.org/attachment.cgi?id=54407 Terminal output (wine 1.9.9) I get a page fault in 32-bit code when starting a game in TOCA Touring Car Championship. This is an old game that requires windows version <= win98. The demo also has the bug. ---begin quote--- ... wine: Unhandled page fault on read access to 0x00000110 at address 0x7e7fcf1d (thread 0028), starting debugger... Unhandled exception: page fault on read access to 0x00000110 in 32-bit code (0x7e7fcf1d). ... Backtrace: =>0 0x7e7fcf1d ddraw_allocate_handle+0x1d(t=0x10c, object=0x15f960, type=DDRAW_HANDLE_MATERIAL) [/home/olivier/Projets/wine-builds/1.9.9_x86/dlls/ddraw/../../../wine-git/dlls/ddraw/main.c:118] in ddraw (0x0033f478) ... ---end quote--- This is with git wine 1.9.9-35-gbd2999d and no 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.

2 16

[Bug 50129] New: Calibre-portable error initializing the bypy frozen importer
by WineHQ Bugzilla Feb. 3, 2023

Feb. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=50129 Bug ID: 50129 Summary: Calibre-portable error initializing the bypy frozen importer Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bilbiliblus(a)gmail.com Distribution: --- When I try to run Calibre-portable.exe y have this message: There was an error initializing the bypy frozen importer: <class 'MemoryError'>: Traceback (most recent call last): File bypy-importer.py, line 250, in <module> File bypy-importer.py, line 195, in __init__ It only happens since Calibre changed to version 5 and on. This very morning I've tried with Calibre 5.3 Thank you -- 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 51313] New: gdi32:driver sometimes fails with a STATUS_GRAPHICS_PRESENT_OCCLUDED error
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=51313 Bug ID: 51313 Summary: gdi32:driver sometimes fails with a STATUS_GRAPHICS_PRESENT_OCCLUDED error Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:driver sometimes gets one or two failures like these: https://test.winehq.org/data/patterns.html#gdi32:driver driver.c:649: Test failed: Got unexpected return code 0xc01e0006. driver.c:689: Test failed: Got unexpected return code 0xc01e0006. 0xc01e0006 is STATUS_GRAPHICS_PRESENT_OCCLUDED. This has happened before but the reason for this error was not identified: https://www.winehq.org/pipermail/wine-devel/2019-July/148494.html I initially suspected a leftover window from a previous test, specifically an Internet Explorer first-run dialog. However the screenshots in the TestBot jobs show that this happens even when there is no such dialog (or at least the dialog is gone by the time the tests complete). The failures always happen on the same two lines despite the occlusion status being checked in other places. Also both failures happen right after minimizing the windows. So it seems likely there is a race condition, either in the test or in the underlying API (if so it spans Windows 10 1607 to 2009). -- 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

[Bug 51040] New: msi:package fails on Windows 10 if privileges not high enough
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=51040 Bug ID: 51040 Summary: msi:package fails on Windows 10 if privileges not high enough Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The following failures only happen if the test is run on a recent enough Windows (i.e. Windows 10) in a user account with too few privileges. package.c:5079: Test failed: Expected "keydata", got "" package.c:5084: Test failed: Expected "field2", got "" package.c:5089: Test failed: Expected "keydata,field2", got "" package.c:5096: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\FileName1", got "" package.c:5107: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\", got "" package.c:5113: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\", got "" package.c:5123: Test failed: Expected "C:\Users\winetest\AppData\Local\", got "" package.c:5136: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\FileName2.dll", got "" package.c:5147: Test failed: Expected "C:\Users\winetest\AppData\Local\Temp\FileName4.dll", got "" package.c:5651: Test failed: Expected , got winetest In particular one can notice this bug on the TestBot's w1064_adm VM. Note however that these tests seem to be run and succeed on wvistaadm and w7u_adm. See: https://test.winehq.org/data/tests/msi:package.html -- 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 47508] New: FL Studio: Pressing backspace while editing the name of something closes edit name window prematurely
by wine-bugs＠winehq.org Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=47508 Bug ID: 47508 Summary: FL Studio: Pressing backspace while editing the name of something closes edit name window prematurely Product: Wine Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ajduck(a)outlook.com Distribution: --- Created attachment 64895 --> https://bugs.winehq.org/attachment.cgi?id=64895 A channel highlighted in the channel rack Since Wine 4.9, pressing backspace to remove text while editing the name of something closes the window and sets the name as whatever was in the box usually with one character removed. Before 4.9 pressing backspace only removed a character without closing the window which is correct behaviour. Steps to reproduce: 1. Open FL Studio. 2. Press F6 to open the channel rack. If nothing appears or a window disappeared, press F6 again. 3. There are probably already a few "channels" in the project file (possibly the demo project opened up). See the image attached. You need to hold shift and click on the highlighted bit, which is a channel. (Alternatively right click and select "Rename, color and icon..."). You can pick any channel for this. 4. The edit name window will appear. Type anything, then press backspace to try and remove a character. What is expected: It should remove a character without closing the window, as text editing usually goes. What actually happens: It closes the edit name window. Sometimes pressing backspace again after the edit name window has closed (especially when doing this on the mixer) goes on to close the playlist (the window with a big grid) which is not normal behaviour (doesn't happen before 4.9 either). Pressing backspace usually only changes the snap settings (the little drop down menu at the top panel of the main FL Studio window which has a magnet by it). -- 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 25

[Bug 49443] New: Anno 1800: Super slow & bad performance
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=49443 Bug ID: 49443 Summary: Anno 1800: Super slow & bad performance Product: Wine Version: 5.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: holzminister(a)t-online.de Distribution: --- Created attachment 67544 --> https://bugs.winehq.org/attachment.cgi?id=67544 terminal out WineD3D Hi, I tried to run Anno 1800 but unfortunately it runs pretty terrible slow on my end. The game itself seems to work fine. But when loading into a game it takes me about 30 minutes on my machine (The loading screen seems unresponsive for most of the time, animation plays like once every 5 minutes or so). When loaded into a game I get like <10 FPS (DXVK & WineD3D) and you can visible see the assets and texures being loaded when scrolling through the map (DXVK, with WineD3D it is the same, but there are a lot of graphical glitches in addition). The terminal output attached is with WineD3D. If you require more information please let me know and I will try to provide it. my pc Archlinux Ryzen 2700x 32gb ram AMD Vega 56 (Mesa 20.1.1) game and os on ssd Kind Regards. -- 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 43235] New: FreeBSD crash on Dungeons & Dragons Online because of secur32
by wine-bugs＠winehq.org Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=43235 Bug ID: 43235 Summary: FreeBSD crash on Dungeons & Dragons Online because of secur32 Product: Wine Version: 2.10 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 58542 --> https://bugs.winehq.org/attachment.cgi?id=58542 Output trying to run the Dungeons & Dragons Online launcher I updated today to staging 2.10 and I wanted to try out D&DO. It was working in staging 2.7 before I upgrade to 2.10 I attached the output. Maybe it's a built mistake from the maintainer, maybe it's Wine, I don't know since I'm using the pre-built package from repositories. -- 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 20

[Bug 49202] New: Never exited critical section in freetype.c
by WineHQ Bugzilla Feb. 2, 2023

Feb. 2, 2023

https://bugs.winehq.org/show_bug.cgi?id=49202 Bug ID: 49202 Summary: Never exited critical section in freetype.c Product: Wine Version: 5.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal54(a)gmail.com Distribution: --- if expression `(!enum_face_charsets(family, face, &enum_charsets, proc, lparam, NULL))` is true, then only return is executed without exiting critical session https://github.com/wine-mirror/wine/blob/6d801377055911d914226a3c6af8d8637a… ``` if (!enum_face_charsets(family, face, &enum_charsets, proc, lparam, psub ? psub->from.name : NULL)) return FALSE; } } } else { LIST_FOR_EACH_ENTRY( family, &font_list, Family, entry ) { face_list = get_face_list_from_family(family); face = LIST_ENTRY(list_head(face_list), Face, entry); if (!enum_face_charsets(family, face, &enum_charsets, proc, lparam, NULL)) return FALSE; ``` -- 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