wine-bugs

wine-bugs@winehq.org

1 participants
158740 discussions

[Bug 53467] New: evr:evr sometimes crashes on Windows
by WineHQ Bugzilla 31 Jul '22

31 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53467 Bug ID: 53467 Summary: evr:evr sometimes crashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com evr:evr sometimes crashes on Windows: * 2022-07-05 w864-64 03f8:evr: 921 tests executed (0 marked as todo, 0 failures), 0 skipped. evr.c:3105: this is the last test seen before the exception 03f8:evr: unhandled exception c0000005 at 00007FFDBDCF7774 * 2022-07-06 w864-64 No trace from the child -> earlier crash? 092c:evr: unhandled exception c0000005 at 00007FFDBCA57764 * 2022-07-08 w1064-tsign-32 evr.c:2123: Test failed: Unexpected size 0 x 0. evr.c:2136: Test failed: Unexpected size 0 x 0. evr.c:2287: Test failed: Failed to create default presenter, hr 0x80070008. evr.c:2287: this is the last test seen before the exception 1bf0:evr: unhandled exception c0000005 at 004030FB The 3 crash modes all started happening at about the same time and seem to all still be happening. So it is likely they all have the same cause. The first Windows crash happened on 2022-07-05 and crashes are rare enough to not happen every day. So it is possible that the crashes are caused by the patch that fixed the Wine crashes (see bug 53201). -- 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 53466] New: kernel32:sync sometimes crashes with STATUS_RESOURCE_NOT_OWNED on Windows
by WineHQ Bugzilla 31 Jul '22

31 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53466 Bug ID: 53466 Summary: kernel32:sync sometimes crashes with STATUS_RESOURCE_NOT_OWNED on 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 kernel32:sync sometimes crashes with STATUS_RESOURCE_NOT_OWNED on Windows: kernel32:sync start dlls/kernel32/tests/sync.c sync.c:596: memory resource notifications not supported 07bc:sync: unhandled exception c0000264 at 00007FFDCF54D1B0 https://test.winehq.org/data/patterns.html#kernel32:sync This happens on all Windows versions, from Windows 7 to Windows 10 21H2. kernel32:sync also crashed once due to a stack overflow (2022-07-27 w10pro64-hi-u8-64): kernel32:sync start dlls/kernel32/tests/sync.c sync.c:596: memory resource notifications not supported kernel32:sync:16a8 done (-1073740791) in 2s Where -1073740791 == 0xc0000409 == STATUS_STACK_BUFFER_OVERRUN. It's not clear if these two are related. -- 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 51182] New: test_write_console() fails in conhost:tty on Windows 1909
by WineHQ Bugzilla 31 Jul '22

31 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=51182 Bug ID: 51182 Summary: test_write_console() fails in conhost:tty on Windows 1909 Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_write_console() fails in conhost:tty on Windows 1909, probably because conhost.exe is broken in Windows 10 <= 2004: tty.c:581: Test failed: 0: expected "abc" got "\x1b[H \x1b[32m0\x1b[41m1\x1b[30m2\x1b[m\x1b[20X\x1b[20C\r\n\x1b[30X\x1b[30C\r\n\x1b[30X\x1b[30C\r\n abc \x1b[30ma\x1b[m\x1b[17X\x1b[17C\r\n child z\r\nz\x1b[29X\x1b[29C\r\n bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nx"... tty.c:586: Test failed: 0: expected " " got "\x1b[H \x1b[32m0\x1b[41m1\x1b[30m2\x1b[m\x1b[20X\x1b[20C\r\n\x1b[30X\x1b[30C\r\n\x1b[30X\x1b[30C\r\n abc \x1b[30ma\x1b[m\x1b[17X\x1b[17C\r\n child z\r\nz\x1b[29X\x1b[29C\r\n bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nx"... tty.c:587: Test failed: 0: expected "t" got "\x1b[H \x1b[32m0\x1b[41m1\x1b[30m2\x1b[m\x1b[20X\x1b[20C\r\n\x1b[30X\x1b[30C\r\n\x1b[30X\x1b[30C\r\n abc \x1b[30ma\x1b[m\x1b[17X\x1b[17C\r\n child z\r\nz\x1b[29X\x1b[29C\r\n bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nx"... tty.c:589: Test failed: expected empty buffer, got "\x1b[H \x1b[32m0\x1b[41m1\x1b[30m2\x1b[m\x1b[20X\x1b[20C\r\n\x1b[30X\x1b[30C\r\n\x1b[30X\x1b[30C\r\n abc \x1b[30ma\x1b[m\x1b[17X\x1b[17C\r\n child z\r\nz\x1b[29X\x1b[29C\r\n bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nx"... tty.c:593: Test failed: 0: expected "\rr abc tx" got "\x1b[m\rr abc tx\x1b[4;2H\x1b[?25h" tty.c:595: Test failed: 0: expected "\x1b[4;2H" got "\x1b[m\rr abc tx\x1b[4;2H\x1b[?25h" tty.c:596: Test failed: 0: expected "\x1b[?25h" got "\x1b[m\rr abc tx\x1b[4;2H\x1b[?25h" tty.c:597: Test failed: expected empty buffer, got "\x1b[m\rr abc tx\x1b[4;2H\x1b[?25h" tty.c:666: Test failed: Read file failed: 996 tty.c:666: Test failed: 0: expected "\x1b[11;29H" got "\x08\x1b[?25h" tty.c:667: Test failed: 0: expected "\x1b[?25h" got "\x08\x1b[?25h" tty.c:669: Test failed: expected empty buffer, got "\x08\x1b[?25h" tty.c:694: Test failed: 0: expected "\r\nc" got "\x1b[?25h" tty.c:706: Test failed: 0: expected "\x1b[40;29H" got "\r\nc\x1b[29X\x1b[29C\x1b[40;29H\x1b[?25h" tty.c:708: Test failed: expected empty buffer, got "\r\nc\x1b[29X\x1b[29C\x1b[40;29H\x1b[?25h" tty.c:729: Test failed: 0: expected "\n" got "\x1b[?25h" tty.c:730: Test failed: 0: expected "\x1b[30X" got "\x1b[?25h" tty.c:731: Test failed: 0: expected "\x1b[30C" got "\x1b[?25h" tty.c:732: Test failed: 0: expected "\r" got "\x1b[?25h" tty.c:741: Test failed: 0: expected "\x1b[12;29H" got "\r\n\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:746: Test failed: 0: expected "43\x08" got "\r\n\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:748: Test failed: expected empty buffer, got "\r\n\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:752: Test failed: 0: expected "\x08" got "43\x1b[12;29H\x1b[?25h" tty.c:756: Test failed: expected hide cursor escape tty.c:757: Test failed: 0: expected "23" got "43\x1b[12;29H\x1b[?25h" tty.c:759: Test failed: 0: expected "\x1b[12;29H" got "43\x1b[12;29H\x1b[?25h" tty.c:760: Test failed: 0: expected "\x1b[?25h" got "43\x1b[12;29H\x1b[?25h" tty.c:761: Test failed: expected empty buffer, got "43\x1b[12;29H\x1b[?25h" tty.c:789: Test failed: 0: expected "\x1b[28C" got "\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:791: Test failed: expected empty buffer, got "\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:862: Test failed: 0: expected "\x1b[21;29H" got "\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... tty.c:864: Test failed: expected empty buffer, got "\x1b[Habcchild z\r\n123\x1b[27X\x1b[27C\r\ncde bo\x1b[30m\r\nxxx890\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\nxx5677\x1b[m\x1b[24X\x1b[24C\x1b[30m\r\n902344\x1b[m\x1b[24X\x1b[24C\r\n xxx\x1b[24X\x1b[24C\r\n\x1b[30X\x1b[30C\r\n "... These failures can be reproduced on cw-rx46-1909, wc-gtx560-1909 and the TestBot's w1064v1909: https://test.winehq.org/data/patterns.html#conhost.exe:tty They don't happen on Windows 10 1809 and lower because the test detects that conhost.exe is broken there: tty.c:1645: Tests skipped: Skipping tty output tests on broken Windows version And the test succeeds on Windows 10 >= 2004 (or rather has unrelated failures). So it looks like 1909 fell between the cracks and that the test should skip too somehow. This test was introduced by the commit below: commit 5d96c5aac883b343ddcfbe6f6b1b96ad6827a46b Author: Jacek Caban <jacek(a)codeweavers.com> AuthorDate: Fri Sep 11 14:31:24 2020 +0200 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Fri Sep 11 16:55:40 2020 +0200 conhost/tests: Add WriteConsole tests. 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 5

[Bug 14797] New: Setting up SSL Email access
by wine-bugs＠winehq.org 31 Jul '22

31 Jul '22

http://bugs.winehq.org/show_bug.cgi?id=14797 Summary: Setting up SSL Email access Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: msetzerii(a)gmail.com Pegasus Mail is a critical program that I use on my only windows 98, and am looking to move to complete linux. The regular email via port 25 and 110 seem to work fine, but with accounts like gmail, one must use secure ports 995 and 465. Attempts to do this result in no trace file. I'm not clear if and how these ports need to be activated in wine, or if some dll needs to be added. There isn't any error message, it just fails with no trace information available. -- 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 66

[Bug 53202] New: shell32:autocomplete - test_custom_source() sometimes does not get autocompletion on Windows
by WineHQ Bugzilla 31 Jul '22

31 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53202 Bug ID: 53202 Summary: shell32:autocomplete - test_custom_source() sometimes does not get autocompletion on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shell32:autocomplete - test_custom_source() sometimes does not get autocompletion on Windows: autocomplete.c:733: Test failed: Expected L"auto complete", got L"au" autocomplete.c:734: Test failed: Expected 1 reset, got 0 autocomplete.c:740: Test failed: Expected 1 reset, got 0 autocomplete.c:743: Test failed: Expected 1 reset, got 0 https://test.winehq.org/data/patterns.html#shell32:autocomplete This is known to happen on Windows 10 1507 to 21H1 but the failure rate is pretty low. -- 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 53459] New: wininet:http - test_security_flags() sometimes fails on Windows due to a security channel error
by WineHQ Bugzilla 31 Jul '22

31 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53459 Bug ID: 53459 Summary: wininet:http - test_security_flags() sometimes fails on Windows due to a security channel error Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wininet:http - test_security_flags() sometimes fails on Windows due to a security channel error: http.c:6590: Test failed: req_error = 12157 http.c:6598: Test failed: expected status 30 (INTERNET_STATUS_SENDING_REQUEST) 1 times, received 0 times http.c:6599: Test failed: expected status 31 (INTERNET_STATUS_REQUEST_SENT) 1 times, received 0 times http.c:6600: Test failed: expected status 40 (INTERNET_STATUS_RECEIVING_RESPONSE) 1 times, received 0 times http.c:6601: Test failed: expected status 41 (INTERNET_STATUS_RESPONSE_RECEIVED) 1 times, received 0 times http.c:6606: Test failed: flags = 8, expected 0 http.c:6607: Test failed: INTERNET_OPTION_SECURITY_FLAGS flags = 1180, expected 20001181 http.c:6607: Test failed: INTERNET_OPTION_SECURITY_FLAGS(98) flags = 1180, expected 20001181 http.c:6612: Test failed: size = 0 https://test.winehq.org/data/patterns.html#wininet:http This failure is quite rare (~1.2%) and seems to only happen on Windows 7 and 8. * 2022-04-27 cw-rx460 (win81) and w864 * 2022-05-18 cw-rx460 (win81) * 2022-05-19 w7u-el * 2022-07-29 w864 -- 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 53457] New: Rosetta Stone 3.45 Failing to Launch
by WineHQ Bugzilla 30 Jul '22

30 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53457 Bug ID: 53457 Summary: Rosetta Stone 3.45 Failing to Launch 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: exDragon945(a)protonmail.com Distribution: --- I have tried running this program in Bottles, directly on system wine and PlayonLinux ( so I can use old Wine versions like 2.2.1-staging). The program launches into its GUI but its GUI throws an error that I have not been able to find an explanation for. Fatal Application Error: #2111 Error #2032 In any way I launch it, it always goes to the GUI to show these errors but the terminal errors change depending on how I launch it. When launching it with system wine, I get these errors: 0070:fixme:imm:ImeSetActiveContext (007BB960, 0): stub 0070:fixme:imm:ImmReleaseContext (00010020, 007BB960): stub 0100:fixme:imm:ImeSetActiveContext (00B31D80, 1): stub 0100:fixme:imm:ImmReleaseContext (0001006C, 00B31D80): stub 0100:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION When launching with bottles, I get these errors: Windows path detected. Avoiding validation. 002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).\ When running it with PlayonLinux I get these errors: Gtk-CRITICAL **: 18:52:50.218: gtk_window_resize: assertion 'width > 0' failed Message: Notice: PlayOnLinux deliberately disables winemenubuilder. See http://www.playonlinux.com/fr/page-26-Winemenubuilder.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 1

[Bug 53442] New: Total War Shogun 2 needs D3DX_FILTER_BOX for memory management.
by WineHQ Bugzilla 30 Jul '22

30 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53442 Bug ID: 53442 Summary: Total War Shogun 2 needs D3DX_FILTER_BOX for memory management. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Total War Shogun 2 uses the D3DX_FILTER_BOX filter to downscale it's textures. Both during normal usage, but more critically, when it's VRAM budget is low or over-committed. This can be seen on Intel GPUs in the game's stderr output with a line similar to: ---snip--- ** Downsizing Textures, Over Budget by : 115 Mb ---snip--- Followed by (in wine-7.12 or older) or prior (in wine-7.13 or later) multiple fixmes: ---snip--- 0024:fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x5. ---snip--- See also the attached log from wine-7.13. As this filter is used for memory management in a 32bit game, it's implementation would help alleviate some OOM errors. -- 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 53454] New: kernel32:loader - map_image_section() sometimes gets the test dll instead of fallback
by WineHQ Bugzilla 30 Jul '22

30 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53454 Bug ID: 53454 Summary: kernel32:loader - map_image_section() sometimes gets the test dll instead of fallback 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 kernel32:loader - map_image_section() sometimes gets the test dll instead of fallback: loader.c:691: Test failed: 1444: got test dll but expected fallback https://test.winehq.org/data/patterns.html#kernel32:loader Nowadays it only happens in 64-bit on w1064v1709 and w10pro64 (21H1). But in the past very similar failures happened in both 32-bit and 64-bit on cw-gtx560 and cw-rx460 when running Windows 10 1709. For instance: loader.c:716: Test failed: 1444: got test dll but expected fallback loader.c:716: Test failed: 1450: got test dll but expected fallback loader.c:716: Test failed: 1456: got test dll but expected fallback loader.c:716: Test failed: 1463: got test dll but expected fallback loader.c:716: Test failed: 1490: got test dll but expected fallback or loader.c:716: Test failed: 1330: got test dll but expected fallback loader.c:716: Test failed: 1337: got test dll but expected fallback loader.c:716: Test failed: 1344: got test dll but expected fallback loader.c:716: Test failed: 1352: got test dll but expected fallback loader.c:716: Test failed: 1359: got test dll but expected fallback loader.c:716: Test failed: 1369: got test dll but expected fallback loader.c:716: Test failed: 1374: got test dll but expected fallback loader.c:716: Test failed: 1379: got test dll but expected fallback loader.c:716: Test failed: 1384: got test dll but expected fallback loader.c:716: Test failed: 1389: got test dll but expected fallback But these machines have been retired. -- 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 53452] New: ws2_32:protocol - GetAddrInfoExW() times out sometimes
by WineHQ Bugzilla 30 Jul '22

30 Jul '22

https://bugs.winehq.org/show_bug.cgi?id=53452 Bug ID: 53452 Summary: ws2_32:protocol - GetAddrInfoExW() times out sometimes 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 - GetAddrInfoExW() times out sometimes. For instance: /* no comment */ protocol.c:1979: Test failed: wait failed protocol.c:1981: Test failed: overlapped result is 10036 protocol.c:1983: Test failed: overlapped.Internal = 2734 protocol.c:1984: Test failed: overlapped.Pointer != &result protocol.c:1985: Test failed: result == NULL /* hints */ protocol.c:2009: Test failed: wait failed protocol.c:2011: Test failed: overlapped result is 10036 protocol.c:2012: Test failed: result == NULL /* completion routine, non-existing domain */ protocol.c:2065: Test failed: wait failed protocol.c:2067: Test failed: overlapped result is 10036 protocol.c:2069: Test failed: overlapped.Internal = 2734 protocol.c:2071: Test failed: got 0 With only 3 known instances this failure is pretty rare but can impact both Windows and Wine: * 2022-05-06 linux_MX-i3 -> hints + non-existing domain * 2022-05-16 cw-gtx560-1909 -> no comment * 2022-07-28 w1064-adm -> hints While it looks very much like this is caused by network issues, it may be that the 1 second timeout is too short. -- 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

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