September 2024 - Wine-Bugs - list.winehq.org

[Bug 57172] Installing winehq-stable 9.0 in Ubuntu 24.04 LTS does not offer to install Mono or Gecko

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57172 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Rosanne DiMesio <dimesio(a)earthlink.net> --- There are no winehq-stable packages for 24.04 yet, because 24.04 was not yet released when Wine 9.0 came out, and there hasn't been an update to the stable branch. Our packaging for 24.04 started with 9.8. https://dl.winehq.org/wine-builds/ubuntu/dists/noble/main/binary-amd64/ Presumably you encountered this issue with someone else's package; report the problem to them. -- 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.

Sept. 9, 2024

[Bug 57172] New: Installing winehq-stable 9.0 in Ubuntu 24.04 LTS does not offer to install Mono or Gecko

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57172 Bug ID: 57172 Summary: Installing winehq-stable 9.0 in Ubuntu 24.04 LTS does not offer to install Mono or Gecko Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: david.l.bridges(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- When installing winehq-stable in Ubuntu 24.04 LTS, neither Wine Mono nor Wine Gecko are offered (as they should be according to https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Mono and https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Mono. Installation of winehq-stable completes without error, but executing $ wine uninstaller shows that Wine Mono is not present, and executing $ wine iexplore fails for lack of Wine Gecko. Both winehq-devel and winehq-staging offer Mono and Gecko, and those are installed and functional. The winehq-stable installation has been a problem for a few days, at least. I rated Severity as Major on the grounds that the absence of Mono and Gecko will cause many Windows apps to fail if installed with Wine Stable. In addition, the problem affects all Ubuntu flavors and other distros based on Ubuntu 24.04. Many thanks for your attention to this issue. -- 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.

Sept. 9, 2024

[Bug 57163] Wine Mono support msi no longer installs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57163 --- Comment #3 from Esme Povirk <madewokherd(a)gmail.com> --- AFAICT this bug won't affect shared installs (as they use MsiInstallProductW for the support msi directly), but it could affect the custom action used by the Wine Mono runtime msi to install the support msi. -- 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.

Sept. 9, 2024

[Bug 57163] Wine Mono support msi no longer installs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57163 --- Comment #2 from Esme Povirk <madewokherd(a)gmail.com> --- I posted a merge request for this: https://gitlab.winehq.org/wine/wine/-/merge_requests/6464 -- 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.

Sept. 9, 2024

[Bug 57101] Battle.net fails to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57101 lyon(a)pvfree.net changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from lyon(a)pvfree.net --- (In reply to Fabian Maurer from comment #5) > Most likely a dupe of bug 57098. There have been WRITECOPY changes that > break Battle.net Agree, closing as dupe of https://bugs.winehq.org/show_bug.cgi?id=57098 *** This bug has been marked as a duplicate of bug 57098 *** -- 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.

Sept. 9, 2024

[Bug 57098] Battle.net does not start after upgrade to 9.16

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57098 --- Comment #10 from lyon(a)pvfree.net --- *** Bug 57101 has been marked as a duplicate of this bug. *** -- 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.

Sept. 9, 2024

[Bug 57098] Battle.net does not start after upgrade to 9.16

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57098 --- Comment #9 from lyon(a)pvfree.net --- (In reply to Smoerrebroed from comment #8) > So can this be put back into wine-staging? Technically the bug exists in both, not just staging. -- 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.

Sept. 9, 2024

[Bug 57098] Battle.net does not start after upgrade to 9.16

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57098 --- Comment #8 from Smoerrebroed <smoerrebroed(a)souls-of-midgard.de> --- So can this be put back into wine-staging? -- 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.

Sept. 9, 2024

[Bug 29947] Option to set virtual desktops to the current resolution

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=29947 --- Comment #19 from Rémi Bernon <rbernon(a)codeweavers.com> --- You can always start a fullscreen virtual desktop with explorer /desktop=foobar,widthxheight, but otherwise it has to respect the default virtual desktop size doesn't it? -- 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.

Sept. 9, 2024

[Bug 29947] Option to set virtual desktops to the current resolution

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=29947 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |alexhenrie24(a)gmail.com, | |rbernon(a)codeweavers.com --- Comment #18 from Alex Henrie <alexhenrie24(a)gmail.com> --- In Wine 9.8 (commit b86cc9e6589), `wine explorer /desktop=foobar` did open a borderless window that filled the entire screen, but in Wine 9.15 (commit 5ffe201c251) it went back to being a bordered window with a default size. I was hoping that the fullscreen feature would stick around. https://gitlab.winehq.org/wine/wine/-/commit/b86cc9e658959cee47e6e587fec4f7… https://gitlab.winehq.org/wine/wine/-/commit/5ffe201c251977a82303c45db9e644… -- 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.

Sept. 9, 2024

[Bug 57161] when starting captvty, it stops saying it has encontered a problem

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57161 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #2 from Fabian Maurer <dark.shadow4(a)web.de> --- Starts fine for me, don't know any more. -- 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.

Sept. 9, 2024

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

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53407 --- Comment #6 from Jonas <winehq(a)jonass.user.lysator.liu.se> --- Created attachment 77072 --> https://bugs.winehq.org/attachment.cgi?id=77072 Console output 20240909 -- 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.

Sept. 9, 2024

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

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53407 --- Comment #5 from Jonas <winehq(a)jonass.user.lysator.liu.se> --- Created attachment 77071 --> https://bugs.winehq.org/attachment.cgi?id=77071 Backtrace 20240909 Still present in 9.17 -- 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.

Sept. 9, 2024

[Bug 57168] Silent Hill 2 (Konami, 2002): page fault in WOW64 + Pure Wayland

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57168 Manuel <redwindwanderer(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Silent Hill 2 (Konami, |Silent Hill 2 (Konami, |2002): page fault in WOW64 |2002): page fault in WOW64 |mode |+ Pure Wayland -- 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.

Sept. 9, 2024

[Bug 57098] Battle.net does not start after upgrade to 9.16

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57098 --- Comment #7 from Fabian Maurer <dark.shadow4(a)web.de> --- > Can't be staging, because it happens with pure 9.16 and 9.17 too. Obviously, because vanilla wine doesn't have a WRITECOPY implementation to begin with. Staging has one, but it broke due to an update. Or intentionally, since the hack was removed. -- 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.

Sept. 9, 2024

[Bug 57168] Silent Hill 2 (Konami, 2002): page fault in WOW64 mode

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57168 --- Comment #2 from Manuel <redwindwanderer(a)gmail.com> --- (In reply to mrdeathjr28 from comment #1) > In my case work with wine 9.17 using wow64 on xubuntu 24.04 (amd renoir > hardware aka ryzen 5 4600G - vega 7 igpu oc to 2300mhz and ddr4 4133mhz > cas18 mushkin) > > https://i.imgur.com/xek7fjm.png > > https://i.imgur.com/mFQ2U3v.png > > https://i.imgur.com/Mv83wnO.png > > https://i.imgur.com/wYE4HyQ.png Are you using X11 or Wayland there? (Wayland as in "pure Wayland", not XWayland). Could it be that the "WOW64 + Pure Wayland" combination affects compatibility vs "WOW64 + X11/XWayland"? -- 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.

Sept. 9, 2024

[Bug 57171] New: Sumerian Six crashes during mission briefing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57171 Bug ID: 57171 Summary: Sumerian Six crashes during mission briefing Product: vkd3d Version: 1.11 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: cmccarthy(a)codeweavers.com Regression SHA1: fd590c2593bda2e511ba688c8881fbdb2d564774 Distribution: --- Fatal error: [File: E:\UE_5.3\Engine\Source\Runtime\RHI\Private\PipelineStateCache.cpp][Line: 365] Shader compilation failures are Fatal. -- 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.

Sept. 9, 2024

[Bug 57170] Apex Legends game crash without IPv6 kernel module

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57170 --- Comment #2 from Grigory Vasilyev <h0tc0d3(a)gmail.com> --- Cleared log: 01bc:Ret iphlpapi.GetAdaptersInfo() retval=00000000 ret=14029164b 01bc:Call ntdll.RtlInterlockedPopEntrySList(1494759a0) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=7feeaed1aa00 ret=14056c7a3 01bc:Call ntdll.RtlInterlockedPopEntrySList(1494759a0) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=7feeaed1ab80 ret=14056c7a3 01bc:Call ntdll.RtlInterlockedPopEntrySList(1494759a0) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=7feeaed1ab40 ret=14056c7a3 01bc:Call ntdll.RtlInterlockedPushEntrySList(1494759a0,7feeaed1aa00) ret=14056caad 01bc:Ret ntdll.RtlInterlockedPushEntrySList() retval=7feeaed1ab60 ret=14056caad 01bc:Call ntdll.RtlInterlockedPopEntrySList(1494759a0) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=7feeaed1aa00 ret=14056c7a3 01bc:Call KERNEL32.VirtualQuery(7fee8ca30000,7ffffe8af220,00000030) ret=1405747d4 01bc:Call ntdll.NtQueryVirtualMemory(ffffffffffffffff,7fee8ca30000,00000000,7ffffe8af220,00000030,7ffffe8af178) ret=6fffffdfd16a 01bc:Ret ntdll.NtQueryVirtualMemory() retval=00000000 ret=6fffffdfd16a 01bc:Ret KERNEL32.VirtualQuery() retval=00000030 ret=1405747d4 01bc:Call KERNEL32.VirtualFree(7fee8ca30000,00000000,00008000) ret=140574809 01bc:Call ntdll.NtFreeVirtualMemory(ffffffffffffffff,7ffffe8af170,7ffffe8af178,00008000) ret=6fffffdfd603 01bc:Ret ntdll.NtFreeVirtualMemory() retval=00000000 ret=6fffffdfd603 01bc:Ret KERNEL32.VirtualFree() retval=00000001 ret=140574809 01bc:Call ntdll.RtlInterlockedPopEntrySList(149475a80) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=00000000 ret=14056c7a3 01bc:Call ntdll.RtlInterlockedPushEntrySList(1494759a0,7feeaed1a9c0) ret=14056caad 01bc:Ret ntdll.RtlInterlockedPushEntrySList() retval=7feeaed1ab60 ret=14056caad 01bc:Call ntdll.RtlInterlockedPopEntrySList(1494759a0) ret=14056c7a3 01bc:Ret ntdll.RtlInterlockedPopEntrySList() retval=7feeaed1a9c0 ret=14056c7a3 00000017 = AF_INET6 00000002 = SOCK_DGRAM 00000011 = IPPROTO_UDP 01bc:Call ws2_32.socket(00000017,00000002,00000011) ret=14028e7f7 01bc:Call ntdll.NtOpenFile(7ffffe8af418,c0100000,7ffffe8af440,7ffffe8af470,00000000,00000000) ret=6fffffb80667 01bc:Ret ntdll.NtOpenFile() retval=00000000 ret=6fffffb80667 01bc:Call ntdll.NtDeviceIoControlFile(00000144,00000000,00000000,00000000,7ffffe8af470,00120320,7ffffe8af420,00000010,00000000,00000000) ret=6fffffb8078a 01bc:Ret ntdll.NtDeviceIoControlFile() retval=c001273f ret=6fffffb8078a 01bc:Call ntdll.RtlNtStatusToDosError(c001273f) ret=6fffffb807ca 01bc:Ret ntdll.RtlNtStatusToDosError() retval=0000273f ret=6fffffb807ca 01bc:Call ntdll.NtClose(00000144) ret=6fffffb80822 01bc:Ret ntdll.NtClose() retval=00000000 ret=6fffffb80822 01bc:Ret ws2_32.socket() retval=ffffffffffffffff ret=14028e7f7 01bc:Call ws2_32.WSAGetLastError() ret=14028e805 01bc:Ret ws2_32.WSAGetLastError() retval=0000273f ret=14028e805 01bc:Call ws2_32.socket(00000017,00000002,00000011) ret=14028e7f7 01bc:Call ntdll.NtOpenFile(7ffffe8af418,c0100000,7ffffe8af440,7ffffe8af470,572e323300000000,73614c7400000000) ret=6fffffb80667 01bc:Ret ntdll.NtOpenFile() retval=00000000 ret=6fffffb80667 01bc:Call ntdll.NtDeviceIoControlFile(00000144,00000000,00000000,00000000,7ffffe8af470,73614c7400120320,7ffffe8af420,00000010,00000000,00000000) ret=6fffffb8078a 01bc:Ret ntdll.NtDeviceIoControlFile() retval=c001273f ret=6fffffb8078a 01bc:Call ntdll.RtlNtStatusToDosError(c001273f) ret=6fffffb807ca 01bc:Ret ntdll.RtlNtStatusToDosError() retval=0000273f ret=6fffffb807ca 01bc:Call ntdll.NtClose(00000144) ret=6fffffb80822 01bc:Ret ntdll.NtClose() retval=00000000 ret=6fffffb80822 01bc:Ret ws2_32.socket() retval=ffffffffffffffff ret=14028e7f7 01bc:Call ws2_32.WSAGetLastError() ret=14028e805 01bc:Ret ws2_32.WSAGetLastError() retval=0000273f ret=14028e805 01bc:Call ws2_32.socket(00000017,00000002,00000011) ret=14028e7f7 01bc:Call ntdll.NtOpenFile(7ffffe8af418,c0100000,7ffffe8af440,7ffffe8af470,572e323300000000,73614c7400000000) ret=6fffffb80667 01bc:Ret ntdll.NtOpenFile() retval=00000000 ret=6fffffb80667 01bc:Call ntdll.NtDeviceIoControlFile(00000144,00000000,00000000,00000000,7ffffe8af470,73614c7400120320,7ffffe8af420,00000010,00000000,00000000) ret=6fffffb8078a 01bc:Ret ntdll.NtDeviceIoControlFile() retval=c001273f ret=6fffffb8078a 01bc:Call ntdll.RtlNtStatusToDosError(c001273f) ret=6fffffb807ca 01bc:Ret ntdll.RtlNtStatusToDosError() retval=0000273f ret=6fffffb807ca 01bc:Call ntdll.NtClose(00000144) ret=6fffffb80822 01bc:Ret ntdll.NtClose() retval=00000000 ret=6fffffb80822 01bc:Ret ws2_32.socket() retval=ffffffffffffffff ret=14028e7f7 01bc:Call ws2_32.WSAGetLastError() ret=14028e805 01bc:Ret ws2_32.WSAGetLastError() retval=0000273f ret=14028e805 01bc:Call ws2_32.socket(00000017,00000002,00000011) ret=14028e7f7 01bc:Call ntdll.NtOpenFile(7ffffe8af418,c0100000,7ffffe8af440,7ffffe8af470,572e323300000000,73614c7400000000) ret=6fffffb80667 01bc:Ret ntdll.NtOpenFile() retval=00000000 ret=6fffffb80667 01bc:Call ntdll.NtDeviceIoControlFile(00000144,00000000,00000000,00000000,7ffffe8af470,73614c7400120320,7ffffe8af420,00000010,00000000,00000000) ret=6fffffb8078a 01bc:Ret ntdll.NtDeviceIoControlFile() retval=c001273f ret=6fffffb8078a 01bc:Call ntdll.RtlNtStatusToDosError(c001273f) ret=6fffffb807ca 01bc:Ret ntdll.RtlNtStatusToDosError() retval=0000273f ret=6fffffb807ca 01bc:Call ntdll.NtClose(00000144) ret=6fffffb80822 01bc:Ret ntdll.NtClose() retval=00000000 ret=6fffffb80822 01bc:Ret ws2_32.socket() retval=ffffffffffffffff ret=14028e7f7 01bc:Call ws2_32.WSAGetLastError() ret=14028e805 01bc:Ret ws2_32.WSAGetLastError() retval=0000273f ret=14028e805 01bc:Call KERNEL32.GetLastError() ret=1412c31b5 01bc:Ret KERNEL32.GetLastError() retval=0000273f ret=1412c31b5 01bc:Call kernelbase.FlsGetValue(0000000b) ret=1412c31c7 01bc:Call ntdll.RtlFlsGetValue(0000000b,7ffffe8adf50) ret=6fffffe292ef 01bc:Ret ntdll.RtlFlsGetValue() retval=00000000 ret=6fffffe292ef 01bc:Ret kernelbase.FlsGetValue() retval=7feeaed00000 ret=1412c31c7 01bc:Call KERNEL32.IsProcessorFeaturePresent(00000017) ret=1412a9aa8 01bc:Call ntdll.RtlIsProcessorFeaturePresent(00000017) ret=6fffffe104ea 01bc:Ret ntdll.RtlIsProcessorFeaturePresent() retval=7ffe0001 ret=6fffffe104ea 01bc:Ret KERNEL32.IsProcessorFeaturePresent() retval=00000001 ret=1412a9aa8 01bc:err:seh:NtRaiseException Unhandled exception code c0000409 flags 1 addr 0x1412a9ab1 -- 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.

Sept. 9, 2024

[Bug 57170] Apex Legends game crash without IPv6 kernel module

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57170 Grigory Vasilyev <h0tc0d3(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|iphlpapi |-unknown -- 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.

Sept. 9, 2024

[Bug 57170] Apex Legends game crash without IPv6 kernel module

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57170 --- Comment #1 from Grigory Vasilyev <h0tc0d3(a)gmail.com> --- Created attachment 77070 --> https://bugs.winehq.org/attachment.cgi?id=77070 winedebug log +relay,+seh,+tid,+iphlpapi -- 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.

Sept. 9, 2024

[Bug 57168] Silent Hill 2 (Konami, 2002): page fault in WOW64 mode

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57168 mrdeathjr28(a)yahoo.es changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28(a)yahoo.es --- Comment #1 from mrdeathjr28(a)yahoo.es --- In my case work with wine 9.17 using wow64 on xubuntu 24.04 (amd renoir hardware aka ryzen 5 4600G - vega 7 igpu oc to 2300mhz and ddr4 4133mhz cas18 mushkin) https://i.imgur.com/xek7fjm.png https://i.imgur.com/mFQ2U3v.png https://i.imgur.com/Mv83wnO.png https://i.imgur.com/wYE4HyQ.png -- 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.

Sept. 9, 2024

[Bug 57098] Battle.net does not start after upgrade to 9.16

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57098 --- Comment #6 from Ker noa <blue-t(a)web.de> --- (In reply to Fabian Maurer from comment #4) > Okay, so this is a wine-staging issue, to be exact it's bug 29384. > > Since commit c901884ac0af17eeeac309269693d959cfb45e0b (ntdll-WRITECOPY: > Remove patch 0010.) the program is broken. > > > FWIW, using "STAGING_WRITECOPY=1" completely breaks the launcher, it doesn't > even start. Can't be staging, because it happens with pure 9.16 and 9.17 too. -- 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.

Sept. 9, 2024

[Bug 57163] Wine Mono support msi no longer installs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57163 --- Comment #1 from Hans Leidekker <hans(a)meelstraat.net> --- I can't reproduce this. -- 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.

Sept. 9, 2024

[Bug 53574] MSYS2 "pacman -Sy" fails key lookup

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53574 Christopher Degawa <ccom(a)randomderp.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ccom(a)randomderp.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.

Sept. 9, 2024

[Bug 57061] SRWLock is slower than CriticalSection on wine. Why?

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57061 William Horvath <wine(a)horvath.blog> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wine(a)horvath.blog --- Comment #7 from William Horvath <wine(a)horvath.blog> --- https://gitlab.winehq.org/wine/wine/-/merge_requests/3504 Just to add to the discussion, here are some results running these benchmarks with and without this patchset applied: Before: CriticalSection output:0.0854515s input:0.0727398s SRWLock output:0.1495588s input:0.1295463s After: CriticalSection output:0.0900452s input:0.0716042s SRWLock output:0.0934296s input:0.0835009s This was after reverting the patchset that superseded it (which doesn't help this benchmark), and applying it to Wine 9.17. -- 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.

Sept. 9, 2024