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

[Bug 48824] New: build error - xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48824 Bug ID: 48824 Summary: build error - xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant Product: Wine-staging Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Building on Debian Buster, I ran into the following error with 5.4-staging using my regular build scripts. ccache gcc -m64 -c -o xact_dll.o /mnt/gaming/applications/wine/git/dlls/xactengine3_6/../xaudio2_7/xact_dll.c -I. \ -I/mnt/gaming/applications/wine/git/dlls/xactengine3_6 \ -I/mnt/gaming/applications/wine/git/dlls/xactengine3_6/../xaudio2_7 -I../../include \ -I/mnt/gaming/applications/wine/git/include -D__WINESRC__ -DXACT3_VER=0x0306 -D_REENTRANT -fPIC \ -Wall -pipe -fcf-protection=none -fno-stack-protector -fno-strict-aliasing \ -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wno-packed-not-aligned \ -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla \ -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -g -O0 /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c: In function ‘unwrap_notificationdesc’: /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GLOBALVARIABLECHANGED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1193:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GUICONNECTED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1194:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GUIDISCONNECTED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1198:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_CUEPREPARED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1199:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_CUEPLAY: ^~~~ ... Build of shared WoW64 failed. I don't have time to investigate right now, but I was able to build fine if I avoided the xactengine-initial patch set. $ ./patchinstall.sh DESTDIR=../../git --all -W xactengine-initial -- 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 16

[Bug 47365] New: jittering caused by mouse input in vkquake
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=47365 Bug ID: 47365 Summary: jittering caused by mouse input in vkquake Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com Distribution: --- Created attachment 64704 --> https://bugs.winehq.org/attachment.cgi?id=64704 wine log In vkquake, enable vsync (and set an fps limit well above refresh rate via "host_maxfps" command if your using a refreshrate of greater than 60Hz, as the game caps to 72fps by default), start a new game and pan the camera via the keyboard's arrow keys. It should be absolutely smooth. Now, pan the camera by moving the mouse instead -> there is jitter. After alt + Tab to the desktop and back into the game, this jitter usually is gone. Still, it shouldn't occur in the first place, as it doesn't happen on Windows. I made sure this isn't a driver issue by checking with both modesetting and xf86-video-amdgpu DDX and also on xwayland. In xwayland, the issue is less distinct, but still noticeable. Happens with both wine 4.9, wine-staging 4.9 and my custom 4.10 build (4.10 not yet in Arch repository). Get vkquake here: https://github.com/Novum/vkQuake/releases/download/1.01.0/vkquake-1.01.0_wi… You also need the game's free demo content, copy the "id1" folder into the main folder. Since the official servers usually are a mess, you can get it from here as well: https://bugs.freedesktop.org/attachment.cgi?id=143128 -- 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 46633] New: unimplemented function: kernel32.dll.startthreadpoolio
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=46633 Bug ID: 46633 Summary: unimplemented function: kernel32.dll.startthreadpoolio Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mushipao(a)gmail.com Distribution: --- Created attachment 63542 --> https://bugs.winehq.org/attachment.cgi?id=63542 backtrace of exception 3rd party, proprietary software errors out in Wine. 0157:fixme:thread:CreateThreadpoolIo (0x64, 0x42fca0, 0x5fc2a0, (nil)): stub wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Unimplemented function KERNEL32.dll.StartThreadpoolIo called at address 0x7bc51e39 (thread 0157), starting debugger... -- 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 18

[Bug 48817] New: Module_InitDLL fails if LDR_MODULE.Flags was modified
by WineHQ Bugzilla April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=48817 Bug ID: 48817 Summary: Module_InitDLL fails if LDR_MODULE.Flags was modified Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com Distribution: --- I've created a test case here: https://github.com/qsniyg/wine_dll_load_test. I would have made a patch to add this in wine's test suite, but it's rather complex (requiring multiple DLLs), so I'm not sure how to do this. dll1.dll depends on dll2.dll, which therefore will have its DllMain run before dll1's. dll2.dll looks for dll1's LDR_MODULE, then blanks out the Flags attribute, alongside a few others. Since MODULE_InitDLL reads the flags from dll1's now-modified LDR_MODULE, it fails to find the LDR_IMAGE_IS_DLL flag, which prevents dll1's DllMain from being run. The test case runs fine under Windows 10, but not under wine. This is used by certain code protection systems in order to confuse debuggers. -- 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 20

[Bug 18104] New: Final Draft: text to speech fails
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

http://bugs.winehq.org/show_bug.cgi?id=18104 Summary: Final Draft: text to speech fails Product: Wine Version: 1.1.19 Platform: All URL: http://www.finaldraft.com/downloads/demo-final-draft.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jens(a)porup.com Final Draft is the screenwriter's standard word processor. It offers a text to speech feature that does not work in wine. It doesn't break anything if you try; the buttons just don't do anything at all. Terminal output coming soon. -- 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.

2 23

[Bug 42136] New: switching tab in sapi.cpl crashes control
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=42136 Bug ID: 42136 Summary: switching tab in sapi.cpl crashes control Product: Wine Version: 2.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fiendishx(a)gmail.com Distribution: --- Created attachment 56693 --> https://bugs.winehq.org/attachment.cgi?id=56693 console log sapi.cpl is installed by the Microsoft Speech SDK installer from https://download.microsoft.com/download/B/4/3/B4314928-7B71-4336-9DE7-6FA4C… (or via winetricks) $ wine control '.wine/drive_c/Program Files (x86)/Common Files/Microsoft Shared/Speech/sapi.cpl' brings up the Speech Properties control panel. Choosing the tab labeled "Text To Speech" crashes the control. Console log 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.

2 7

[Bug 48052] New: kernel32:debugger - Wine randomly fails to get the thread context
by WineHQ Bugzilla April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=48052 Bug ID: 48052 Summary: kernel32:debugger - Wine randomly fails to get the thread context Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The kernel32:debugger test randomly fails with a variable number of these failures: debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 See https://test.winehq.org/data/tests/kernel32:debugger.html These happen in test_debugger(), when fetch_process_context() tries to get the context of each thread. In Wine GetThreadContext() randomly fails causing a variable number of the above messages depending on how many threads are impacted. All three Wine builds are impacted. The ERROR_ACCESS_DENIED probably comes from get_handle_obj() in server/handle.c. Given that this test was added to test a Wine exception handling race (*), maybe the race is still present? (*) Based on the commit message for: commit 42a9b58b066ff374148cee088ac57cfba46e3b76 Author: Jacek Caban <jacek(a)codeweavers.com> AuthorDate: Mon Aug 26 19:37:20 2019 +0200 kernel32/tests: Add exception handling race test. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The tests were later enabled on Wine by: commit 27da4fa4498c3b6e0e46c72a9cdd13b620726e92 Author: Jacek Caban <jacek(a)codeweavers.com> AuthorDate: Fri Sep 20 16:33:53 2019 +0200 kernel32/tests: Enable debug break exception race tests on i386 Wine. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 48556] New: Nascar racers crash at start
by WineHQ Bugzilla April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=48556 Bug ID: 48556 Summary: Nascar racers crash at start Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maniikarabera(a)protonmail.ch Distribution: --- Created attachment 66370 --> https://bugs.winehq.org/attachment.cgi?id=66370 Crash log with 32 bit prefix Crashes at start. -- 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 45111] New: Winamp - Milkdrop complains
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=45111 Bug ID: 45111 Summary: Winamp - Milkdrop complains Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: stu.axon(a)gmail.com Distribution: --- Clicking the visualisation tab displays a dialog: MILKDROP ERROR Error compiling ps_2_0 warp shader :127:8:error: syntax error, unexpected KW_TEXTURE Then you click OK and get another dialog MILKDROP ERROR Your hardware says that it supports shader model 3.0 [PSVersion==0x300], but it doesn't seem to do it properly - maybe your display is just buggy. You might want to try updating your display driver to the latest WHQL driver from the chipset manufacturer (NVIDIA, ATI, etc) Googling for wine winamp "ps_2_0 warp shader" Shows the issue going back to at least 2010 Tested on AMD Radeon Vega 8 - on wine 3.7-staging -- 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 40502] New: Global objects constructors fail when invoking standard libs
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=40502 Bug ID: 40502 Summary: Global objects constructors fail when invoking standard libs Product: Wine Version: 1.8.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: mirko.ortensi(a)gmail.com Distribution: --- I managed to recompile and link my win32 application but at execution time, it crashes because of a segmentation fault where memset (or the bare printf("HELLO")) is invoked in the global object constructor (any call to standard C library is enough to trigger the crash). The global object is built in the stack, then it seems that at launch time my object constructor is called before C Standard Library is ready. Now, as a workaround I can declare a pointer to global object and instantiate it in the main (tested, it works)...though...this is something I'd like to avoid to keep the code as original as possible. Removing the global objects, everything works like a charm. As far as I understand, global object constructors are called after Wine infrastructure is ready to go, though I have doubts now regarding C Standard Library. (Please check 8.3.3. Starting a Winelib process https://www.winehq.org/docs/winedev-guide/x3172) This code reproduces the error: #include <stdio.h> class Printer { public: Printer(){printf("HI\n");} }; Printer p; int main(void) { return 0; } The issue is reproduced by this code linking to msvcrt: wineg++ -mno-cygwin issue.cpp -o issue Linking to system libs, this code does not reproduce the issue. wineg++ issue.cpp -o issue Now, in my code (pretty big software I am porting to Linux) I still need to isolate root cause, issue is reproduced even linking against system libraries (not Wine's msvcrt, then). Anyway, I think there's a bug somewhere when linking to msvcrt even in this silly piece of 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.

2 10