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

[Bug 53099] New: wineserver (gcc -O0) crash when exiting LiLi USB Creator
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53099 Bug ID: 53099 Summary: wineserver (gcc -O0) crash when exiting LiLi USB Creator Product: Wine Version: 7.10 Hardware: x86-64 URL: http://download.tuxfamily.org/lilicreator/stable/Linux Live%20USB%20Creator%202.9.4.exe OS: Linux Status: NEW Keywords: download, regression, source Severity: critical Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Regression SHA1: a61188bfa5bf20443b11f397d8ef6e7e5fd4bdf1 Distribution: Ubuntu Created attachment 72529 --> https://bugs.winehq.org/attachment.cgi?id=72529 Wine 7.10 (gcc -O0) console output When Wine is compiled with -O0 (no optimisation), wineserver crashes when exiting the LinuxLive USB Creator. -O1, -O2 or -O3 optimisation doesn't experience the crash.Tried with GCC 7 and 8. [334632.437161] wineserver[471477]: segfault at aaaaaace ip 00000000566503c3 sp 00000000ffb530a0 error 4 in wineserver[56634000+99000] [334632.437172] Code: 8d 90 38 6d fd ff 52 89 c3 e8 e9 ad fe ff 90 8b 5d fc c9 c3 55 89 e5 83 ec 08 e8 c7 cc fe ff 05 10 1a 08 00 8b 45 08 8b 40 28 <8b> 40 24 83 ec 08 ff 75 0c ff 75 08 ff d0 83 c4 10 90 c9 c3 55 89 gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 gcc-8 (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0 Bisect shows this started happening at commit a61188bfa5bf20443b11f397d8ef6e7e5fd4bdf1 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Fri Nov 27 18:13:59 2020 +0100 server: Use separated fd ops for unbound console input. 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 8

[Bug 53756] New: configure fails in 32-bit gcc checking pthread_create using -Wl,--disable-stdcall-fixup
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53756 Bug ID: 53756 Summary: configure fails in 32-bit gcc checking pthread_create using -Wl,--disable-stdcall-fixup Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: zakarjor(a)yahoo.com Distribution: --- in 32-bit wine build, ./configure fails with the following message: checking for pthread_create in -lpthread... no configure: error: pthread 32-bit develment files not found. Wine cannot support threads without libpthread. Use the --without-pthread option if you really want this. Checking config.log, the problem seems to be related to a second test of -Wl,--disable-stdcall-fixup for cross-compiler, which sets CFLAGS with that argument, and pthread test uses gcc that doesn't have that flag. in case $host_cpu in *i[3456]86*), it checks -Wl,--disable-std-call-fixup and since gcc doesn't have it, CFLAGS is not changed, but further down, when it tests the same flag for cross-compiler, since 32-bit mingw gcc has that flag, CCFLAGS now appends that flag. Eventually when pthread_create is tested using gcc with CFLAGS containing the unknown flag for gcc, it fails to compile, and wrongly says it couldn't find pthread_create. This works for case x86_64 since no such flag test exists. This looks like a regression by changes in https://gitlab.winehq.org/wine/wine/-/commit/8b7baa1128d974b6b9e4fc49853242… -- 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 53550] New: Some Catalan locales not properly handled
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53550 Bug ID: 53550 Summary: Some Catalan locales not properly handled Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marc.ruiz+wine(a)live.com Distribution: --- My system has locale ca_AD.UTF-8 which is for Catalan. However Wine apparently does not recognize it as Catalan, it only recognizes ca_ES. How to reproduce: LANG=ca_AD.UTF-8 winecfg -> UI is shown in English (wrong). LANG=ca_ES.UTF-8 winecfg -> UI is shown in Catalan (right). LANG=ca_FR.UTF-8 winecfg -> UI is shown in English (wrong). LANG=ca_IT.UTF-8 winecfg -> UI is shown in English (wrong). I have actually discovered this while running YY-CHR (https://appdb.winehq.org/objectManager.php?sClass=version&iId=22701) Running this program with WINEDEBUG=nls I have discovered that ca_ES is mapped to locale CAT and ca_AD and the others to ZZZ. -- 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 53525] New: dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=53525 Bug ID: 53525 Summary: dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinpu:hid - test_hid_multiple_tlc() sometimes fails with testsigning turned on: hid.c:3926: Test failed: Failed to find HID device matching L"\\\\?\\hid#vid_1209&pid_0001&col02" hid.c:3930: Test failed: got error 2 hid.c:3040: Test failed: HidD_GetPreparsedData failed with error 6 hid.c:3043: Test failed: got "\\\x00\\\x00?\x00\\\x00" expected "HidP KDR" https://test.winehq.org/data/patterns.html#dinput:hid These failures happened on both fgtb-w10pro64-tsign and w1064-tsign and only those. So they seem to be specific to Windows 10 with test signing turned on. -- 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 52997] New: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay.
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=52997 Bug ID: 52997 Summary: Integration of D3D12 support with a PE build of vkd3d causes a crash in Steam Overlay. Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: cmccarthy(a)codeweavers.com Distribution: --- Launching a D3D12 game with Steam Overlay enabled results in a null pointer dereference right after a call to D3D11On12CreateDevice(). Changing the returned values alters the crash location. This is a regression caused by integration of a vkd3d PE build in commit 5d62e5603. The call to D3D11On12CreateDevice() doesn't occur when using an ELF vkd3d build. -- 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 8

[Bug 52873] New: oleaut32:typelib fails in Wine in Hindi
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=52873 Bug ID: 52873 Summary: oleaut32:typelib fails in Wine in Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:typelib fails in Wine in Hindi: typelib.c:2514: Test failed: got: L"default?" typelib.c:2526: Test failed: got: L"default?" typelib.c:3314: Test failed: got: L"default?" typelib.c:3326: Test failed: got: L"default?" https://test.winehq.org/data/patterns.html#oleaut32:typelib A bisect shows that the test started failing with the commit below: commit e81327358a26b160740b3421a4c7f300b4d2f06f Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Apr 13 15:13:16 2022 +0200 kernelbase: Move codepage initialization to ntdll. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Oddly this is the same commit as for a recent set of vbscript:run failures (see bug 52872). -- 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 52779] New: Construction Set Extender crash with an Assertion Error in wine 7.5
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=52779 Bug ID: 52779 Summary: Construction Set Extender crash with an Assertion Error in wine 7.5 Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: --- Using wine 7.5 Consturction Set Extender (plugin for Oblivion Construction Set) crash with the following assertion Assertion failed: Data != ActiveComboBoxes.cend(), file Y:\CSE\Construction-Set-Extender\UIManager.cpp, line 623 Everything works fine with wine 7.4 There is no log except the common imm fixme and a lot of d3d:wined3d_check_device_format_conversion and d3d:state_linepattern_w that are present even in 7.4 Bisection in progress -- 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 12

[Bug 42797] New: ICU64 for VICE: No highlighted read/ write-colors in Memory-window.
by wine-bugs＠winehq.org Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=42797 Bug ID: 42797 Summary: ICU64 for VICE: No highlighted read/write-colors in Memory-window. Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: enkorv(a)yahoo.com Distribution: --- Created attachment 57824 --> https://bugs.winehq.org/attachment.cgi?id=57824 terminal output when running ICU64.exe VICE is a Commodore 64 (and siblings) emulator. "ICU64 for VICE" is a hacking tool that piggybacks onto the emulator and shows memory maps in useful ways. When starting ICU64.exe it opens a small toolbar and starts the VICE emulator as well. When selecting Memory in the toolbar a window opens which shows the memory map of the Commodore 64. It should also highlight the memory read and writes as well as where the CPU is currently running, using color highlighting. This part doesn't work so the window just has a black background. You can still zoom in and out in the memory map (using mouse scroll-wheel) and see the values of the memory locations changing live. An example of how the color highlighting typically looks is here (could not find a clip of ICU64 for VICE, so this clip shows ICU64 for Frodo, which is another Commodore 64 emulator): https://www.youtube.com/watch?v=tjcvR5McmSg Testing and wine-environment: Ubuntu 16.10 - 4.8.0-46-generic wine-2.4 ICU64 needs Microsoft .NET Framework 2.0 (see http://icu64.blogspot.se/p/download.html ) WINEPREFIX=~/.winetest2017 WINEARCH=win32 wineboot WINEPREFIX=~/.winetest2017 winetricks dotnet2 ICU64 - https://sites.google.com/site/mathfigure/icu64vice23-v0.1.2.zip c89d54ea7d64834694c3590660dee69e0738a418 WinVICE 2.3 - https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/W… b2a7ffafbcef1ab159681002616d9cf819c1ef84 Download both, unzip into same folder and run ICU64.exe. -- 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 2

[Bug 31927] New: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'
by wine-bugs＠winehq.org Dec. 21, 2022

Dec. 21, 2022

http://bugs.winehq.org/show_bug.cgi?id=31927 Bug #: 31927 Summary: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0' Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: winsock AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Running in a loop for about 15 minutes, I got: sock.c:5385: Test succeeded inside todo block: GetQueuedCompletionStatus returned 0 sock.c:5386: Test succeeded inside todo block: Last error was 64 make: *** [sock.ok] Error 2 -- 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 10

[Bug 54094] New: kernel32:process - test_services_exe() sometimes fails due to an invalid buffer size in Windows
by WineHQ Bugzilla Dec. 21, 2022

Dec. 21, 2022

https://bugs.winehq.org/show_bug.cgi?id=54094 Bug ID: 54094 Summary: kernel32:process - test_services_exe() sometimes fails due to an invalid buffer size in Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_services_exe() sometimes fails due to an invalid buffer size in Windows: process.c:4962: Test failed: got 0xc0000004 See https://test.winehq.org/data/patterns.html#kernel32:process Where 0xc0000004 == STATUS_INFO_LENGTH_MISMATCH This causes a little bit over one failure per month. I think the failure simply happens when a process is started between the first call to NtQuerySystemInformation(), which returns the buffer size to hold the *array* of SYSTEM_PROCESS_INFORMATION structures, and the time we call it again with that size. Obviously we don't start new processes ourselves so it must be a scheduled task or some equivalent. We should probably loop a couple of times to defend against that. -- 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