wine-bugs July 2023

wine-bugs@winehq.org

1 participants
3313 discussions

[Bug 30155] New: secdrv.sys from SafeDisc v2.05.030 does not work
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=30155 Bug #: 30155 Summary: secdrv.sys from SafeDisc v2.05.030 does not work Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: stefan(a)codeweavers.com Classification: Unclassified Created attachment 39336 --> http://bugs.winehq.org/attachment.cgi?id=39336 service,relay,winedevice,ntoskrnl log SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is that the application exits with exit code 0 without any output. This affects for example the Command and Conquer Red Alert 2 installer, which is safedisc protected for some reason. The problem seems to be related to the specific secdrv.sys version. If I take a secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's revenge expansion) and put it in C:\windows\system32\drivers, the installer works. ProtectId says: Scanning -> D:\Setup\Setup.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh) Byte(s) -> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h [File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027) [!] Safedisc v2.05.030 detected ! [i] Appended data contents.... [.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947 byte(s) -> ~de7bc4.tmp [.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208 byte(s) -> clcd32.dll [.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784 byte(s) -> clcd16.dll [.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584 byte(s) -> mcp.dll [.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220 byte(s) -> ~df394b.tmp [.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304 byte(s) -> drvmgt.dll [.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768 byte(s) -> secdrv.sys [.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248 byte(s) -> ~ef7194.tmp [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.640 Second(s) The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010 driver is f376a1580204e47f37a721e1cbc5582a. I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of the setup tool. -- 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 32

[Bug 55305] New: advapi32:eventlog - test_autocreation() fails on the Windows 10 2004 and 2009 VMs
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55305 Bug ID: 55305 Summary: advapi32:eventlog - test_autocreation() fails on the Windows 10 2004 and 2009 VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 74901 --> https://bugs.winehq.org/attachment.cgi?id=74901 Minimal eventlog to reproduce the test_autocreation() failure advapi32:eventlog - test_autocreation() fails on the Windows 10 2004 and 2009 VMs: eventlog.c:1156: Test failed: Expected an eventlog file See http://winetest.dolphin/data/patterns.html#advapi32:eventlog This failure is systematic and specific to these two Windows configurations. Also it happens even when running advapi32:eventlog on its own. Commenting out parts of the test shows that the failure is caused by the final CloseEventLog(handle) in test_clear(). See the attached patch to minimally reproduce this failure. This is similar to bug 54614: advapi32:eventlog causes the event log service to crash which breaks test_autocreation(): Source : Service Control Manager Event ID : 7031 The Windows Event Log service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. -- 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 1

[Bug 55301] New: gdi32:font - test_bitmap_font_metrics(System) fails in Wine for the Japanese and Chinese locales
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55301 Bug ID: 55301 Summary: gdi32:font - test_bitmap_font_metrics(System) fails in Wine for the Japanese and Chinese locales Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font - test_bitmap_font_metrics(System) fails in Wine for the Japanese and Chinese locales. In the ja_JP locale: font.c:986: Test failed: System(18): tm.tmWeight 700 != 400 In the zh_CN locale: font.c:993: Test failed: System(16): tm.tmInternalLeading 0 != 3 See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian 11 and Testing VMs -- 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 1

[Bug 55303] New: gdi32:font - test_lang_names() fails in Wine for the Japanese locale
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55303 Bug ID: 55303 Summary: gdi32:font - test_lang_names() fails in Wine for the Japanese locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font - test_lang_names() fails in Wine for the Japanese locale: font.c:7268: Test failed: 2: (1) unexpected lfFaceName L"\30d5\30a9\30f3\30c8\540d Cond (ja)" font.c:7276: Test failed: 2: (1) unexpected elfStyle L"Regular" font.c:7268: Test failed: 2: (0) unexpected lfFaceName L"Wine_Lang_Names" font.c:7276: Test failed: 2: (0) unexpected elfStyle L"Regular" font.c:7310: Test failed: 2: EnumFontFamiliesExW unexpected count 0. font.c:7319: Test failed: 2: EnumFontFamiliesExW unexpected count 0. See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian 11 and Testing VMs. -- 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 1

[Bug 55302] New: gdi32:font fails in Wine for the Chinese locale
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55302 Bug ID: 55302 Summary: gdi32:font fails in Wine for the Chinese locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font fails in Wine for the zh_CN locale: test_GetCharABCWidths(): font.c:1238: Test failed: GetCharABCWidthsA 100 - 100 should have failed font.c:1238: Test failed: GetCharABCWidthsA ffff - ffff should have failed test_font_charset(): font.c:2703: Test failed: 0 vs 2: indices shouldn't match test_bitmap_font_glyph_index(): font.c:6925: Test failed: expected a9, got 3f (Courier:0) font.c:6925: Test failed: expected a9, got 3f (Small Fonts:0) font.c:6870: Tests skipped: expected Fixedsys, got Noto Sans CJK SC font.c:6925: Test failed: expected a9, got 3f (System:0) See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian 11 and Testing VMs. There are other failures, see bug 55299 and bug 55301. -- 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 1

[Bug 55300] New: gdi32:font - test_bitmap_font_metrics() fails in Wine for the Arabic locale
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55300 Bug ID: 55300 Summary: gdi32:font - test_bitmap_font_metrics() fails in Wine for the Arabic locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font - test_bitmap_font_metrics() fails in Wine for the Arabic locale (ar_MA): font.c:995: Test failed: Small Fonts(11): tm.tmAveCharWidth 5 != 4 font.c:996: Test failed: Small Fonts(11): tm.tmFirstChar = 20 font.c:1001: Test failed: Small Fonts(11): tm.tmDefaultChar = 80 font.c:1002: Test failed: Small Fonts(11): tm.tmBreakChar = 20 font.c:1008: Test failed: Small Fonts(11): tm.tmMaxCharWidth 9 != 10 See See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian 11 and Testing VMs. -- 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 55297] New: dlls/ntdll/unix fails to build with gcc-10 and AddressSanitizer
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55297 Bug ID: 55297 Summary: dlls/ntdll/unix fails to build with gcc-10 and AddressSanitizer Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian Building Wine with AddressSanitizer enabled fails in dlls/ntdll/unix with pthread errors. To reproduce: #!/bin/bash export ASAN_OPTIONS=detect_leaks=0 export CFLAGS="-O0 -g -fsanitize=address" export LDFLAGS="-fsanitize=address" ./configure make ... /usr/bin/ld: dlls/ntdll/unix/loader.o: in function `init_paths': /home/austin/wine/dlls/ntdll/unix/loader.c:618: undefined reference to `dladdr' /usr/bin/ld: dlls/ntdll/unix/loader.o: in function `dlopen_dll': /home/austin/wine/dlls/ntdll/unix/loader.c:1166: undefined reference to `dlerror' /usr/bin/ld: /home/austin/wine/dlls/ntdll/unix/loader.c:1170: undefined reference to `dlsym' /usr/bin/ld: dlls/ntdll/unix/thread.o: in function `start_thread': /home/austin/wine/dlls/ntdll/unix/thread.c:1102: undefined reference to `pthread_setspecific' -- 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 0

[Bug 51669] New: EverQuest d3d:wined3d acquires unexpected context
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51669 Bug ID: 51669 Summary: EverQuest d3d:wined3d acquires unexpected context Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: johnherschelfreeman2013(a)gmail.com Distribution: --- Created attachment 70543 --> https://bugs.winehq.org/attachment.cgi?id=70543 err wined3d_context_gl_reacquire In game launcher and game client -- 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 53198] New: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53198 Bug ID: 53198 Summary: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507: protocol.c:2459: Test failed: Test 0: Got unexpected ret 0 protocol.c:2459: Test failed: Test 1: Got unexpected ret 0 protocol.c:2459: Test failed: Test 2: Got unexpected ret 0 protocol.c:2459: Test failed: Test 3: Got unexpected ret 0 protocol.c:2459: Test failed: Test 4: Got unexpected ret 0 protocol.c:2459: Test failed: Test 5: Got unexpected ret 0 protocol.c:2459: Test failed: Test 12: Got unexpected ret 0 protocol.c:2459: Test failed: Test 13: Got unexpected ret 0 protocol.c:2459: Test failed: Test 14: Got unexpected ret 0 protocol.c:2459: Test failed: Test 15: Got unexpected ret 0 protocol.c:2459: Test failed: Test 16: Got unexpected ret 0 protocol.c:2459: Test failed: Test 28: Got unexpected ret 0 protocol.c:2459: Test failed: Test 29: Got unexpected ret 0 https://test.winehq.org/data/patterns.html#ws2_32:protocol This really looks like a Windows 10 1507 bug so it's tempting to add a broken((hinttests[i].family == AF_UNSPEC && hinttests[i].sock_type != 999) && ...). But it's strange that there is no failure on index 6 for instance since it's the same test after line 2455 (hint.ai_family = AF_INET6): 0: {AF_UNSPEC, SOCK_STREAM, IPPROTO_TCP, 0}, /* 0 */ 6: {AF_INET, SOCK_STREAM, IPPROTO_TCP, 0}, -- 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 55270] New: NVIDIA OptiX SDK samples hang forever
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55270 Bug ID: 55270 Summary: NVIDIA OptiX SDK samples hang forever Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no Distribution: --- Running NVIDA OptiX SDK samples hangs forever before drawing to screen. I have bisected this to this particular patch: https://gitlab.winehq.org/wine/wine/-/commit/18ae96e5fb3cbbd53f1a022ba81203… This patch is from the https://gitlab.winehq.org/wine/wine/-/merge_requests/416 MR Reverting this by removing XLockDisplay runs the samples again. I am not sure why the need for a mutex + XLockDisplay is there, but i assume the reasoning is perfectly fine - but maybe only IF one actually expect/get an error? The OptiX samples hits the "ignored_error" thing, but seemingly just stops without releasing the XDisplay again and thus just hang. If interested in testing these OptiX samples, i have a pre-compiled set here: https://github.com/SveSop/wine-nvoptix/pull/20#issuecomment-1079719794 (Read installation instructions in that post - since the SDK hard-links binaries to images and whatnot in the folder structure) All of the samples in THAT particular archive do run if you use latest "nvidia-libs" from here: https://github.com/SveSop/nvidia-libs/actions Only nvcuda and nvoptix is needed - no need for DXVK/DXVK-NVAPI to run these samples - but you DO need NVIDIA RTX 2xxx gpu, and with the aforementioned revert of XLockDisplay it runs on wine-8.12 from GIT. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs July 2023