November 2021 - Wine-Bugs - list.winehq.org

[Bug 51227] urlmon:url breaks the wininet:http test on Windows 10 1709+ (7 failures)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51227 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|urlmon:url breaks the |urlmon:url breaks the |wininet:http test on |wininet:http test on |Windows 10 1709+ |Windows 10 1709+ (7 | |failures) -- 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.

Nov. 21, 2021

[Bug 51821] EVE Online Client Crashes Due to differences in how Wine and Windows handle LdrGetDllPath with dwFlags 0x8 and relative path

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51821 nick(a)foxsec.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com, | |z.figura12(a)gmail.com -- 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.

Nov. 21, 2021

[Bug 51821] EVE Online Client Crashes Due to differences in how Wine and Windows handle LdrGetDllPath with dwFlags 0x8 and relative path

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51821 --- Comment #20 from nick(a)foxsec.net --- Created attachment 71085 --> https://bugs.winehq.org/attachment.cgi?id=71085 Upstream patch v5 - 2/2 I've attached the patches I've been trying to get upstreamed for a bit, but it's been slow-going because there aren't a lot of maintainers who are comfortable with this area of the codebase. @zf, @gofman etc., would you guys consider adding this to wine-staging for now? I'm planning to continue trying to get these upstreamed but I'm not sure it's going to be able to happen before the upcoming code freeze. Please let me know if there's anything I can do to help. Thanks! -- 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.

Nov. 21, 2021

[Bug 51821] EVE Online Client Crashes Due to differences in how Wine and Windows handle LdrGetDllPath with dwFlags 0x8 and relative path

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51821 nick(a)foxsec.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick(a)foxsec.net --- Comment #19 from nick(a)foxsec.net --- Created attachment 71084 --> https://bugs.winehq.org/attachment.cgi?id=71084 Upstream patch v5 - 1/2 -- 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.

Nov. 21, 2021

[Bug 52072] winmm:mci fails in wow64 Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52072 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |7c5761ed40f0b8cead7fa837b74 | |5b687d5df67d8 Keywords| |regression, source, | |testcase -- 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.

Nov. 21, 2021

[Bug 52072] New: winmm:mci fails in wow64 Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52072 Bug ID: 52072 Summary: winmm:mci fails in wow64 Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winmm:mci started failing in wow64 Wine on 2021-11-11. It now has 51 failures: mci.c:248: Test failed: status 4(mode): MCIERR_UNSUPPORTED_FUNCTION mci.c:328: Test failed: status mode: MCIERR_UNSUPPORTED_FUNCTION mci.c:656: Test marked todo: mci info new file returned 0=NOERROR mci.c:660: Test marked todo: status x length initial: MCIERR_UNSUPPORTED_FUNCTION mci.c:665: Test failed: mci status samplespersec returned MCIERR_UNSUPPORTED_FUNCTION mci.c:732: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:781: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:812: Test failed: mci status length returned MCIERR_UNSUPPORTED_FUNCTION mci.c:827: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:848: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:849: Test failed: mci status mode: after play from 0 to 0 mci.c:860: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:903: Test failed: mci status position notify returned MCIERR_UNSUPPORTED_FUNCTION mci.c:906: Test failed: Expect message 0001 from status position mci.c:909: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:910: Test failed: mci status mode: mci.c:915: Test marked todo: Expect message 0001 from play to 250 wait notify mci.c:955: Test failed: mci status mode returned MCIERR_UNSUPPORTED_FUNCTION mci.c:956: Test failed: mci status mode: mci.c:974: Test failed: mci status position returned MCIERR_UNSUPPORTED_FUNCTION mci.c:975: position after Sleep: ms [...] https://test.winehq.org/data/patterns.html#winmm:mci Note that besides the test failures the "mci status mode: " and "position after Sleep: ms" messages are suspicious. All four Linux test machines are impacted by this: the failure test pattern makes it obvious for cw-gtx560, cw-rx460 and the TestBot's debiant2 VM. fg-deb64 is impacted as well but it is masked by the preexisting timeout. Strangely a bisect shows that these failures started with this commit: commit 7c5761ed40f0b8cead7fa837b745b687d5df67d8 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Nov 11 16:21:00 2021 +0100 wrc: Ignore the target option. Nothing in resource files depends on the pointer size. 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.

Nov. 21, 2021

[Bug 51949] black boxes for mouse pointer and windows in wine-staging-6.20

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51949 --- Comment #15 from Mike Purtell <mmikeinsantarosa(a)gmail.com> --- Hope this isn't cross posting but I figured additional information somewhere would be useful. Someone here pointed me to 3 patches for photoshop but I can't locate that reference and link to the patches but I kept them once posted. The author is Fabian Maurer <dark.shadow4(a)web.de> The patches are called pspatch1of3.patch pspatch2of3.patch pspatch3of3.patch Photoshop-6 would not run on a build of wine-6.21 with or without these patches. I did a fresh build of wine-6.22 without the 3 patches and photoshop now launches but has a square box for a pointer and cardfile windows are blacked out. I rebuilt wine-6.22 with the 3 patches and the mouse pointer for photoshop problem is fixed. Cardfile launches but any selected window is blacked out. I will rebuild wine-6.22 again with just the cardfile patch you just pointed me to here and test cardfile and photoshop then I'll rebuild it again with the cardfile patch and the 3 photoshop patches and test and post results here if that is OK. -- 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.

Nov. 20, 2021

[Bug 52071] mshtml:script fails in externalDisp_InvokeEx() on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52071 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |6b2c20c6a1aa046c5f0317221b5 | |2609bcaa11295 Keywords| |regression, source, | |testcase -- 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.

Nov. 20, 2021

[Bug 52071] New: mshtml:script fails in externalDisp_InvokeEx() on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52071 Bug ID: 52071 Summary: mshtml:script fails in externalDisp_InvokeEx() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mshtml:script fails in externalDisp_InvokeEx() on all Windows versions from 7 to 10/21H1. script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11" script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick string = function ondblclick(event)\n{\nstring\n}" script.c:3417: Running documentmode.js script in edge;123 mode... script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11" script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick string = function ondblclick(event)\n{\nstring\n}" https://test.winehq.org/data/patterns.html#mshtml:script A bisect shows that this failure appeared with the commit below: commit 6b2c20c6a1aa046c5f0317221b52609bcaa11295 Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Date: Tue Nov 16 19:58:16 2021 +0200 mshtml: Clear the string dprop associated with the builtin attribute when removing it. Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Note that this failure was reported by the TestBot: https://www.winehq.org/pipermail/wine-devel/2021-November/200830.html https://source.winehq.org/patches/data/219693.testbot -- 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.

Nov. 20, 2021

[Bug 52070] New: error messages when graphics driver is null

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52070 Bug ID: 52070 Summary: error messages when graphics driver is null Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: maliku(a)posteo.net Distribution: --- Following the documentation of https://wiki.winehq.org/Useful_Registry_Keys I set the graphics driver to "null", rather than "x11" I get these errors from the wine output, when I was expecting them to be suppressed, or at least not raised as errors 0418:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0418:err:winediag:nodrv_CreateWindow The explorer process failed to start. 0418:err:systray:initialize_systray Could not create tray window -- 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.

Nov. 20, 2021