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

[Bug 54420] preloader warning "failed to reserve range" macOS Ventura

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54420 --- Comment #1 from Brendan Shanks <bshanks(a)codeweavers.com> --- Yep, dyld (at least on Ventura, didn't test Monterey) allocates private memory in that region very early, before any part of the preloader runs. A zero-fill section does succeed in reserving this memory, but the dyld allocations start right after, so picking the size would be tricky. Once wow64 is working upstream there will likely be other memory reservation changes needed, we can revisit this then. (We know of an EXE with an image base of 0x10000 that fails to run on Ventura, but does work when a zerofill is used to reserve it, so that's promising). ==== regions for process 61077 (non-writable and writable regions are interleaved) REGION TYPE START - END [ VSIZE RSDNT DIRTY SWAP] PRT/MAX SHRMOD PURGE REGION DETAIL dyld private memory 1000-41000 [ 256K 48K 48K 0K] rw-/rwx SM=PRV dyld private memory 41000-81000 [ 256K 16K 16K 0K] rw-/rwx SM=PRV -- 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.

Feb. 1, 2023

[Bug 54413] ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54413 --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- Socket handles *are* NT handles, which is why you can duplicate them. The way it actually (seems to) work is that they have some in-process data as well. I'm not sure what this in-process data comprises—we don't store any—but it may simply have to do with layered service providers (which we don't implement). Hence if you just create an NT socket handle in a target process, ws2_32 won't know about it, and will conclude it's not a socket when trying to look it up. In order to tell ws2_32 about it you're supposed to use WSADuplicateSocket() instead of DuplicateHandle() and then import it on the other end with WSASocket(). (Internally WSADuplicateSocket() seems to just call DuplicateHandle() and stash the socket handle in the returned struct.) Which all makes this test failure very confusing—how did ws2_32 find out about this socket? -- 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.

Feb. 1, 2023

[Bug 54420] New: preloader warning "failed to reserve range" macOS Ventura

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54420 Bug ID: 54420 Summary: preloader warning "failed to reserve range" macOS Ventura Product: Wine Version: 8.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com CC: bshanks(a)codeweavers.com The usual Apple made changes that affects macOS Ventura preloader: Warning: failed to reserve range 0000000000010000-0000000000110000 -- 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.

Feb. 1, 2023

[Bug 54413] ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54413 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- Yes. It's as if sockets and handles are in separate namespaces and we sometimes get a collision. But if that were the case DuplicateHandle() should never work on sockets so that hypothesis makes no sense. The Microsoft documentation does say one should not use DuplicateHandle() on sockets, mostly because "the duplicate handle may not be recognized by Winsock at the target process" which is not the issue here. It's strange how this seems to suggest DuplicateHandle() of sockets works but is unreliable. And more importantly it does not say why it would be unreliable. The documentation also says "DuplicateHandle interferes with internal reference counting on the underlying (socket?) object". But I don't see how this could be the issue here. It does suggest our test is doing something it shouldn't. But then testing corner cases is not not uncommon... -- 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.

Feb. 1, 2023

[Bug 52354] winemac.drv not functional on non metal GPUs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52354 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |63bf2677ed22d26ff1f5ff1886f | |de08b1f5fb00c -- 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.

Feb. 1, 2023

[Bug 52354] winemac.drv not functional on non metal GPUs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52354 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #54 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Let's call this one FIXED, thanks everyone for getting this done. -- 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.

Feb. 1, 2023

[Bug 54357] Spurious fixme message when calling ScrollWindow()

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54357 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |8870d51d3e09565463baa11ce7d | |2b43c9ca252e4 --- Comment #2 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Fixed by https://gitlab.winehq.org/wine/wine/-/commit/8870d51d3e09565463baa11ce7d2b4… -- 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.

Feb. 1, 2023

[Bug 51313] gdi32:driver sometimes fails with a STATUS_GRAPHICS_PRESENT_OCCLUDED error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51313 Hans Leidekker <hans(a)meelstraat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |a744265c1e81237dc0e7c37176c | |cb2aadf8d940f Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Hans Leidekker <hans(a)meelstraat.net> --- Fixed with 2d19baa6b57643e56c6e7982a4e43564d24dc7f3 and a744265c1e81237dc0e7c37176ccb2aadf8d940f. -- 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.

Feb. 1, 2023

[Bug 54419] New: RICHED20: Word Break Procedure of Rich TextBox should consider punctuation

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54419 Bug ID: 54419 Summary: RICHED20: Word Break Procedure of Rich TextBox should consider punctuation Product: Wine Version: 8.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: katayama.hirofumi.mz(a)gmail.com Distribution: --- Created attachment 73977 --> https://bugs.winehq.org/attachment.cgi?id=73977 the patch to the word break procedure of rich textbox The default word break procedure of rich textbox didn't consider punctuation. This patch will add punctuation check to the default word break procedure. -- 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.

Feb. 1, 2023

[Bug 54418] New: gdiplus: SOFTWARE_GdipFillPath is not anti-aliased, making the UI interface invisible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54418 Bug ID: 54418 Summary: gdiplus: SOFTWARE_GdipFillPath is not anti-aliased, making the UI interface invisible Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- When some fonts use fillpath for drawing, when the font is extremely small, it will be difficult for people to read, or even part of it will be missing -- 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.

Feb. 1, 2023