May 2023 - Wine-Bugs - list.winehq.org

[Bug 54959] winhttp:notification - test_websocket() times out on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54959 --- Comment #2 from Hans Leidekker <hans(a)meelstraat.net> --- The server sends clients in a redirect loop. Hopefully this will be fixed within a few days, otherwise I'll switch the test to a different server. -- 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.

May 19, 2023

[Bug 54936] Wine 8.7 and 8.8 does not print

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54936 --- Comment #8 from Piotr Caban <piotr.caban(a)gmail.com> --- I've sent a patch that should fix the crash: https://gitlab.winehq.org/wine/wine/-/merge_requests/2860 Please attach a new log if it still doesn't work with the patch. -- 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.

May 19, 2023

[Bug 54960] winhttp:winhttp - test_websocket() fails on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54960 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- Also in Wine one gets a crash which would be a bug within the bug: winhttp.c:3543: Test failed: got 8 winhttp.c:3549: Test failed: got 12019 winhttp.c:3550: Test failed: got 3735928559 Unhandled exception: page fault on write access to 0x0000000000000010 in 64-bit code (0x00000071104850). [...] =>0 0x00000071104850 _InterlockedIncrement(dest=<internal error>) [/home/fgouget/wine/winetest/wow64/../src/include/winnt.h:7016] in winhttp (0x0000000065f878) 1 0x00000071104850 netconn_addref() in winhttp (0x0000000065f878) 2 0x00000071115ff2 WinHttpWebSocketCompleteUpgrade+0x182(hrequest=<internal error>, context=<internal error>) [/home/fgouget/wine/winetest/wow64/../src/dlls/winhttp/request.c:3411] in winhttp (0x0000000065f878) -- 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.

May 19, 2023

[Bug 54960] winhttp:winhttp - test_websocket() fails on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54960 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- See also bug 54959 for a set of failures that started in winhttp:notification at the same time. -- 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.

May 19, 2023

[Bug 54959] winhttp:notification - test_websocket() times out on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54959 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- See also bug 54960 for a set of failures that started in winhttp:winhttp at the same time. -- 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.

May 19, 2023

[Bug 54960] New: winhttp:winhttp - test_websocket() fails on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54960 Bug ID: 54960 Summary: winhttp:winhttp - test_websocket() fails on Windows and Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winhttp:winhttp - test_websocket() fails on Windows and Wine: winhttp.c:3543: Test failed: got 8 winhttp.c:3549: Test failed: got 12019 winhttp.c:3550: Test failed: got 3735928559 winhttp.c:3553: Test failed: got 4317 winhttp.c:3572: Test failed: got 12018 winhttp.c:3577: Test failed: got 12018 winhttp.c:3582: Test failed: got 12018 winhttp.c:3583: Test failed: got 12018 winhttp.c:3588: Test failed: got 12018 winhttp.c:3593: Test failed: got 12018 winhttp.c:3598: Test failed: got 12018 winhttp.c:3603: Test failed: got 12018 winhttp.c:3609: Test failed: got 6 winhttp.c:3610: Test failed: got winhttp.c:3611: Test failed: got 0 winhttp.c:3612: Test failed: got 3735928559 winhttp.c:3615: Test failed: got 6 winhttp.c:3621: Test failed: got 6 winhttp.c:3625: Test failed: got 6 winhttp.c:3628: Test failed: got 6 winhttp.c:3631: Test failed: got 6 winhttp.c:3637: Test failed: got 6 winhttp.c:3638: Test failed: got winhttp.c:3639: Test failed: got 0 winhttp.c:3640: Test failed: got 3735928559 winhttp.c:3646: Test failed: got 6 winhttp.c:3647: Test failed: got winhttp.c:3648: Test failed: got 0 winhttp.c:3649: Test failed: got 3735928559 winhttp.c:3652: Test failed: got 6 winhttp.c:3655: Test failed: got 6 winhttp.c:3659: Test failed: got 6 winhttp.c:3662: Test failed: got 6 winhttp.c:3665: Test failed: got 6 winhttp.c:3669: Test failed: got 6 winhttp.c:3672: Test failed: got 6 winhttp.c:3675: Test failed: got 6 winhttp.c:3678: Test failed: got 6 winhttp.c:3681: Test failed: got 6 winhttp.c:3684: Test failed: got 6 winhttp.c:3688: Test failed: got 6 winhttp.c:3689: Test failed: got 3735928559 winhttp.c:3692: Test failed: got 6 winhttp.c:3698: Test failed: got 6 winhttp.c:3699: Test failed: got 57005 winhttp.c:3700: Test failed: got 3735928559 See https://test.winehq.org/data/patterns.html#winhttp:winhttp It looks like this is not a regression but a change in the server behavior that broke the test. If that change is not temporary the test will need to be adjusted. -- 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.

May 19, 2023

[Bug 54959] New: winhttp:notification - test_websocket() times out on Windows and Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54959 Bug ID: 54959 Summary: winhttp:notification - test_websocket() times out on Windows and Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winhttp:notification - test_websocket() times out on Windows and Wine: notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:118: Test failed: 994: expected status 0x20000 got 0x1 notification.c:123: Test failed: 994: expected callback 0x1 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x2 notification.c:123: Test failed: 994: expected callback 0x2 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4 notification.c:123: Test failed: 994: expected callback 0x4 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x8 notification.c:123: Test failed: 994: expected callback 0x8 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x200000 notification.c:123: Test failed: 994: expected callback 0x200000 to be called from the same thread winhttp:notification:1448 done (258) in 120s 9182B This is not a regression but rather an issue with the server. lsof shows the test stuck with a connection to 104.21.29.32 (but that's a CloudFlare IP). So the server's behavior must have changed recently and if that's not temporary the test will need to be adjusted. -- 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.

May 19, 2023

[Bug 54958] Wine leaks DBUS connections

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54958 hamiltonone(a)rambler.ru changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |integration -- 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.

May 19, 2023

[Bug 54920] Clear Sailing: Wine crashes and leaves desktop in low resolution

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54920 Jonas <winehq(a)jonass.user.lysator.liu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Clear Sailing: crashes and |Clear Sailing: Wine crashes |leaves desktop in low |and leaves desktop in low |resolution |resolution -- 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.

May 19, 2023

[Bug 53407] Hogia Hemekonomi Missing date picker widget (Wine crash?)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53407 Jonas <winehq(a)jonass.user.lysator.liu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Hogia Hemekonomi Missing |Hogia Hemekonomi Missing |date picker widget (wine |date picker widget (Wine |crash?) |crash?) -- 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.

May 19, 2023