December 2020 - Wine-Bugs - list.winehq.org

[Bug 47657] New: Character in The Sims 1 Make-A-Celebrity looks completely white
by wine-bugs＠winehq.org May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=47657 Bug ID: 47657 Summary: Character in The Sims 1 Make-A-Celebrity looks completely white Product: Wine Version: 4.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Created attachment 65100 --> https://bugs.winehq.org/attachment.cgi?id=65100 +ddraw,+d3d,+d3d_shader It's very close to https://bugs.winehq.org/show_bug.cgi?id=46948 but it only seems to happen to this particular add-on tool. Actual game still renders just fine so it's a regression. To run this tool, you need to have an installation of the actual game. Attaching +ddraw,+d3d,+d3d_shader 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.

2 6

[Bug 47716] New: cat planet fails to start with llvmpipe drivers
by wine-bugs＠winehq.org May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=47716 Bug ID: 47716 Summary: cat planet fails to start with llvmpipe drivers Product: Wine Version: 4.15 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- Cat Planet fails to start. It brings up a dialog saying "Unexpected error occured [sic] when running the game." It seems that it triggers a floating point exception in the mesa software drivers. -- 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 9

[Bug 48633] New: CSS HTML Validator 2020 - toolbar does not display properly
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=48633 Bug ID: 48633 Summary: CSS HTML Validator 2020 - toolbar does not display properly Product: Wine Version: 5.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: support(a)htmlvalidator.com Distribution: --- Created attachment 66485 --> https://bugs.winehq.org/attachment.cgi?id=66485 Shows incorrect display of Toolbar (look at row containing "New List" and more) The Batch Wizard tool in CSS HTML Validator 2020 does not display the Toolbar properly. To reproduce: 1. Download trial version at https://www.htmlvalidator.com/private/css-html-validator-wine-bug-x64-setup… 2. Install and run program. 3. Go to the Batch Wizard (F2). 4. By default, the toolbar is hidden in Wine because it does not display properly. To force the display of the toolbar, choose Options->Force Toolbar. 5. The toolbar icons and spacing will not display properly. The toolbar buttons appear to be fully justified, but they should be left justified. 6. The toolbar should look more like it does on Windows (see attachment). -- 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 48650] New: Support other keyboard layout than "standard" one (dvorak, bepo…)
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=48650 Bug ID: 48650 Summary: Support other keyboard layout than "standard" one (dvorak, bepo…) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: aeris+winehq(a)imirhil.fr Distribution: --- Created attachment 66509 --> https://bugs.winehq.org/attachment.cgi?id=66509 bepo patch Currently running wine with a "not standard" keyboard like bépo or dvorak leads to some key not recognized. On bépo, key like "«" ("2" caps on an azerty) not completely working. On Guild Wars 2, "«" works correctly on chat input but can't be bind to a function on ingame key mapping menu, or "é" ("z" on an azerty) works standalone but not with alt modifier (but ctrl or shift modifiers work). I try to modify directly https://github.com/wine-mirror/wine/blob/c698682b3286d72cc7c4c4624b4d14b03d… to add bépo support but I don't understand `key_scan` or `key_vkey` values. Achieve to get almost fully working bépo keyboard ("«" and "é" act correctly again but some modifiers don't work) with removal of all mapping in this file but a custom bépo one (made without real understanding of what I do :P). -- 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 48736] New: shlwapi: Implement SHLockSharedEx function
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=48736 Bug ID: 48736 Summary: shlwapi: Implement SHLockSharedEx function Product: Wine Version: 5.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shlwapi Assignee: wine-bugs(a)winehq.org Reporter: katayama.hirofumi.mz(a)gmail.com Distribution: --- Created attachment 66625 --> https://bugs.winehq.org/attachment.cgi?id=66625 The patch There is no implementation of SHLWAPI!SHLockSharedEx function. This patch will add 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.

1 3

[Bug 48749] New: Spider: Game fails at completion
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=48749 Bug ID: 48749 Summary: Spider: Game fails at completion Product: Wine Version: 5.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: james.tabor(a)reactos.org Distribution: --- Created attachment 66652 --> https://bugs.winehq.org/attachment.cgi?id=66652 Spider from ReactOS Playing game it locks up at completion. -- 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 49074] New: Nintendulator 0.980 - AVI capture fails due to error in AVIStreamWrite
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=49074 Bug ID: 49074 Summary: Nintendulator 0.980 - AVI capture fails due to error in AVIStreamWrite Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: avifil32 Assignee: wine-bugs(a)winehq.org Reporter: quietust(a)gmail.com Distribution: Ubuntu In Nintendulator 0.980 (a Nintendo Entertainment System emulator), attempting to record to an AVI file fails with AVIERR_UNSUPPORTED from AddAudio::AVIStreamWrite when running in Wine Staging 5.7 on Ubuntu 16.04.6 LTS. The same thing happens in Wine-Devel 5.7. Given that I am the author of this application, I've been able to track down exactly what's going wrong. On Windows, the AVIStreamWrite function treats the "lStart" parameter differently depending on the stream type - for a Video stream it expects it to be a frame number (increasing by 1 each time), but for an Audio stream it expects it to be a *sample* number (increasing by "lSamples" each time). In Wine, however, Audio streams expect "lStart" to increase by 1 each time, just like Video streams. I've built two test versions of my application: one that only works on Windows, and one that only works in Wine. They can be downloaded from the following URL: https://www.qmtpro.com/~nes/misc/nintendulator_winebug.zip (sha1 4eca2a261db3fdaa03cbc92cbee307c56ffffac2) See https://github.com/quietust/nintendulator/blob/fc91a2abcbe3ad37a1a6e52f12d8… for relevant source code - these test versions have lines 273-280 commented out and have "WineHack" hardcoded (to "false" for the Windows version and "true" for the Wine version) for the check on line 287. Steps to reproduce: 1. Download and extract the archive linked above 2. Run "nintendulator_windows.exe stars.nes" in Wine 3. Open the "Misc" menu and select "Start AVI Capture" 4. Enter a filename and press Save 5. Set the Compressor to "Full Frames (Uncompressed)" and press OK 6. Press F2 to start emulation and observe that it fails. 7. Repeat steps 2-6 with "nintendulator_wine.exe" and observe that it now works correctly. 8. Repeat steps 2-7 on Windows and observe that the results are the other way around. -- 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 49186] New: DXBC compiler generates incorrect spir-v code
by WineHQ Bugzilla May 27, 2021

May 27, 2021

https://bugs.winehq.org/show_bug.cgi?id=49186 Bug ID: 49186 Summary: DXBC compiler generates incorrect spir-v code Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: alex.fishman(a)gmail.com Distribution: --- Created attachment 67204 --> https://bugs.winehq.org/attachment.cgi?id=67204 dxbc tessellaton control shader I'm having issues with tessellation shaders. Seems that the generated spir-v code is incorrect. After converting the spir-v to GLSL (spirv-dis) and validating it (glslangValidator) there are errors in the the following section: #version 450 layout(vertices = 5) out; out float gl_ClipDistance[5]; layout(location = 0) out vec2 o0[5]; layout(location = 1) out vec4 o1[5]; vec4 opc[4]; vec4 v1[5]; void control0() { v1[1u] = vec4(gl_ClipDistance[0u]); v1[2u] = vec4(gl_ClipDistance[1u]); v1[3u] = vec4(gl_ClipDistance[2u]); v1[4u] = vec4(gl_ClipDistance[3u]); v1[5u] = vec4(gl_ClipDistance[4u]); vec4 r0; r0.x = intBitsToFloat(gl_InvocationID); o0[gl_InvocationID] = gl_in[floatBitsToInt(r0.x)].gl_Position.xy; o1[gl_InvocationID] = v1[floatBitsToInt(r0.x)]; } ... glslangValidator outputs the following error: ERROR: 0:4: 'gl_ClipDistance' : identifiers starting with "gl_" are reserved ERROR: 1 compilation errors. No code generated. Sample DXBC binary is attached -- 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 6

[Bug 49301] New: pthread_exit hangs on unwind through call_thread_exit_func on arm64
by WineHQ Bugzilla May 26, 2021

May 26, 2021

https://bugs.winehq.org/show_bug.cgi?id=49301 Bug ID: 49301 Summary: pthread_exit hangs on unwind through call_thread_exit_func on arm64 Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)codeweavers.com Distribution: --- Created attachment 67309 --> https://bugs.winehq.org/attachment.cgi?id=67309 Workaround My arm64 Wine build spins in services.exe after starting up anything. The backtrace points into pthread_exit() - see attached file backtrace.txt. I placed pthread_exit calls throughout the thread creation / shutdown code and it works up to the point where signal_exit_thread() calls call_thread_exit_func(). After call_thread_exit_func() passes control to the C function exit_thread() pthread_exit() will hang. I previously had this problem only in a gcc wine build (with 8fb8cc03 reverted), but recently, presumably after an update to clang-10, the problem also happens when building Wine with clang. The attached backtrace is from a build with clang 10. Calling exit_thread() directly from signal_exit_thread() without going through call_thread_exit_func works around the problem. See attached file noasm.diff -- 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 49378] New: kernel32.WriteFile with multi byte characters reports incorrect number of written bytes
by WineHQ Bugzilla May 26, 2021

May 26, 2021

https://bugs.winehq.org/show_bug.cgi?id=49378 Bug ID: 49378 Summary: kernel32.WriteFile with multi byte characters reports incorrect number of written bytes Product: Wine Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: suokkos(a)gmail.com Distribution: --- Created attachment 67438 --> https://bugs.winehq.org/attachment.cgi?id=67438 Wine test case to trigger the bug Writing utf-8 multibyte characters to stdout using stdio led to uncovering this bug. Attached test case is a simple way to trigger the underlying issue. Minimal steps leading to issue: 1. Set console output to CP_UTF8 2. Use WriteFile with multibyte characters Expect outcome: WriteFile reports number of bytes written. Actual outcome: WriteFile reports number of characters written. Other observations while writing test case: I first run same test case using kernelbase.WriteFile. Base version seems to behavior differently because my test case passed. I only then noticed the important detail that there is multiple WriteFile entry points. -- 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