- Wine-Bugs - list.winehq.org

[Bug 59900] New: The Sims Complete Collection doesn't launch in WOW64 mode
by WineHQ Bugzilla June 22, 2026

June 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=59900 Bug ID: 59900 Summary: The Sims Complete Collection doesn't launch in WOW64 mode Product: Wine Version: 11.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Created attachment 81227 --> http://bugs.winehq.org/attachment.cgi?id=81227 +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree,+wow While it launches fine in legacy mode, the game fails to launch using Wow64 wine provided by Arch Linux. Attached is a log when launching the app with parameters I was recommended. To assist with reproduction, I've packaged the game installer into an archive. Link to my google drive: https://drive.google.com/file/d/1LisB53e1svvcHl3f2-vQsAXUfVIES7SA/view?usp=… You need to install using start.exe, enter license key from Crack/serial_key.txt, and due to the game using obsolete and non-working SecureDrive DRM, in drive_c/Program Files (x86)/Maxis/The Sims, replace Sims.exe with Sims.exe from the installation's Crack folder. -- 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 58987] New: Wine doesn't use the proper freetype function for fetching the value of FSType.
by WineHQ Bugzilla June 22, 2026

June 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=58987 Bug ID: 58987 Summary: Wine doesn't use the proper freetype function for fetching the value of FSType. Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- When filling in the otmfsType value in OUTLINETEXTMETRICW, wine should call FT_Get_FSType_Flags() according to: https://freetype.org/freetype2/docs/reference/ft2-information_retrieval.htm… Wine however accesses the value directly (against advice of the above link), applies a strange bitmask, and writes the result into otmfsType. I found this while trying to troubleshoot some invalid values I was getting from GetOutlineTextMetrics(). Unfortunately, calling the proper freetype function only fixed some of them. I believe there's an uninitialized value being used somewhere for otmfsType. As I've been getting otmfsType values like 0x6fff for the Liberation fonts / Droid Sans Fallback / Dejima, and 0x80750007 for Abyssinica SIL at random. -- 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 1

[Bug 59897] New: Thief 3 - Deadly Shadows: Unable to play the game on WoW64
by WineHQ Bugzilla June 22, 2026

June 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=59897 Bug ID: 59897 Summary: Thief 3 - Deadly Shadows: Unable to play the game on WoW64 Product: Wine Version: 11.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: kajitsu22(a)gmail.com Distribution: --- Created attachment 81224 --> http://bugs.winehq.org/attachment.cgi?id=81224 Trying to run a vanilla Thief 3 version I tried to launch Thief 3 - Deadly Shadows on my new Wine Staging, version 11.11. Previously I was using Wine Staging of version 10.12, multilib, and the game was running smoothly, without any sort of error. After some time, though, I had to reinstall the system from sctratch, and of course, I opted in to the new WoW64 backend. All I received is inability to even launch the game. I tried using the vanilla GOG version of Thief 3, and I tried to install the latest Sneaky Upgrade. It behaves differently in both cases. OS: Gentoo Linux x86_64 Kernel: 6.18.35-gentoo-r1 Video Card: NVIDIA GTX 2050 Mobile I'm attaching the vannila game log here. -- 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 6

[Bug 59899] New: ARM64 64k alignment change tripled installation size
by WineHQ Bugzilla June 21, 2026

June 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59899 Bug ID: 59899 Summary: ARM64 64k alignment change tripled installation size Product: Wine Version: 10.6 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)list.winehq.org Reporter: martin(a)martin.st CC: julliard(a)winehq.org Regression SHA1: e2686a5dffe9f4db3a983a4c1d2aba4f46f35758 Distribution: --- Before commit e2686a5dffe9f4db3a983a4c1d2aba4f46f35758 (winegcc: Set default section alignment to 64k on ARM64.), the size of a plain install of Wine (configured with "CFLAGS="-O2" CROSSCFLAGS="-O2" ./configure ... --without-x --without-freetype", installed with "make install-lib") tripled. Before this change, the size of the install (measured with "du -hs <prefix>") was 177 MB, after this change it was 536 MB - which seems a bit excessive. Would it be possible to only set the section alignment to 64k, while keeping the file alignment at 4k, to conserve file size - or does the file alignment need to be the same as or higher than the section alignment? -- 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 52739] New: DoNotSpy10 5.3 crashes after opening
by WineHQ Bugzilla June 21, 2026

June 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=52739 Bug ID: 52739 Summary: DoNotSpy10 5.3 crashes after opening Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Created attachment 72105 --> https://bugs.winehq.org/attachment.cgi?id=72105 Full Crash log ``` ================================================================= Native Crash Reporting ================================================================= Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Managed Stacktrace: ================================================================= ================================================================= wine: Unhandled page fault on write access to 0000000000000000 at address 000000001288E091 (thread 0708), starting debugger... ... =>0 0x000000001288e091 EntryPoint+0x7cee1() in xul (0x000000001c65f020) 1 0x0000000014b71300 EntryPoint+0x2360150() in xul (0x000000001c65f020) 2 0x0000000014b752f8 EntryPoint+0x2364148() in xul (0x000000001c65f020) 3 0x0000000014b9a0b0 EntryPoint+0x2388f00() in xul (0x000000001c65f020) 4 0x0000000014b9ec75 EntryPoint+0x238dac5() in xul (0x000000001c65f020) 5 0x0000000014b9e9a6 EntryPoint+0x238d7f6() in xul (0x000000001c65f020) 6 0x0000000014ba200e EntryPoint+0x2390e5e() in xul (0x000000001c65f020) 7 0x0000000014ba206d EntryPoint+0x2390ebd() in xul (0x000000001c65f020) 8 0x0000000010872dcf detach_gecko_browser+0x10f(This=000000000F541B00) [Z:\usr\src\packages\BUILD\dlls\mshtml\nsembed.c:2352] in mshtml (0x000000001c65f020) 9 0x00000000107c24cf NtCurrentTeb(This=0000000000000000) [Z:\usr\src\packages\BUILD\include\winnt.h:2157] in mshtml (0x000000001c65f020) 10 0x00000000107c24cf GetProcessHeap(This=<register R12 not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml (0x000000001c65f020) 11 0x00000000107c24cf heap_free(This=<register R12 not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml (0x000000001c65f020) 12 0x00000000107c24cf HTMLDocumentObj_Release+0x17f(iface=<register RBX not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml (0x000000001c65f020) 13 0x000000006f50683f deactivate_document+0x17f(This=<register RBX not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\ieframe\dochost.c:572] in ieframe (0x000000001c65f020) 14 0x000000006f51e0bb OleObject_SetClientSite+0x26b(iface=<register RBX not accessible in this frame>, pClientSite=<internal error>) [Z:\usr\src\packages\BUILD\dlls\ieframe\oleobject.c:498] in ieframe (0x00000 0001c65f020) ``` Steps to reproduce: - Download and install app - Change windows version to 10 - Run app - After while(1-5s) app should 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.

2 6

[Bug 29719] New: Aliwangwang crash after login
by wine-bugs＠winehq.org June 21, 2026

June 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=29719 Bug #: 29719 Summary: Aliwangwang crash after login Product: Wine Version: 1.3.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Classification: Unclassified wine-1.3.37-447-ge79644e 1. Download installer of AliWangWang : http://download.taobaocdn.com/wangwang/AliIM2011_taobao(6.50.27T).exe ( from http://www.taobao.com/wangwang/2010_fp/seller.php ) sha1sum AliIM2011_taobao$6.50.27T$.exe c70d449bc48eed24dce2e5274c636b5128c202d1 AliIM2011_taobao(6.50.27T).exe 2. install with wine: $ LANG=C wine AliIM2011_taobao(6.50.27T).exe (use LANG=C to workaround bug 10063) 3. download http://bugs.winehq.org/attachment.cgi?id=34748 as clsidall.reg, import with regedit, works around Bug 27196 ( dup of bug 25340) 4. winetricks vcrun2008 5. Start wangwang: $ wine AliIM.exe 6. login to WangWang After some time, WangWang will crash. Different patterns of crash have been found, winetricks ie8 will avoid the crash. -- 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 11

[Bug 56664] New: winecfg not exposing an option for 7.1 surround sound audio output (winepulse.drv)
by WineHQ Bugzilla June 21, 2026

June 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=56664 Bug ID: 56664 Summary: winecfg not exposing an option for 7.1 surround sound audio output (winepulse.drv) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ib10evp0(a)gmx.org Distribution: --- Using a self-compiled winecfg from a Wine build based on commit `ae9bdbda3be2b4ab5be34463fe1daec6c11cc7e6` (post 9.8), I see no option to set 7.1 output for the pulse audio driver in winecfg. Only Mono, Stereo, Quadrophonic and 5.1 is available even though my system is set to 7.1 output in the host os configuration. Setup: Wine & winecfg (self-compiled) @ ae9bdbda3be2b4ab5be34463fe1daec6c11cc7e6 (post Wine 9.8) Ubuntu 22.04 with Pulseaudio Audio device profile set to 7.1 output in system configuration (test sounds output properly to 7.1 speaker system) -- 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 5

[Bug 59898] New: Wine on aarch64 fails on linux with CONFIG_ARM64_VA_BITS=39
by WineHQ Bugzilla June 21, 2026

June 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59898 Bug ID: 59898 Summary: Wine on aarch64 fails on linux with CONFIG_ARM64_VA_BITS=39 Product: Wine Version: 8.11 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)list.winehq.org Reporter: martin(a)martin.st CC: julliard(a)winehq.org Regression SHA1: ac1761d1dae8bf114a05e28ed6886deba6c2c860 Distribution: --- Since commit ac1761d1dae8bf114a05e28ed6886deba6c2c860, "loader: Build the preloader as PIE on 64-bit.", Wine on aarch64 fails on linux kernels that are configured with CONFIG_ARM64_VA_BITS=39. In my case, old and small SBCs have kernels built with CONFIG_ARM64_VA_BITS=39 (or CONFIG_ARM64_VA_BITS_39=y, which then sets CONFIG_ARM64_VA_BITS to that value). From https://github.com/raspberrypi/linux/blob/rpi-6.18.y/arch/arm64/configs/bcm…, it seems like even very recent configurations for raspberry pi 4 have this set, while kernels for raspberry pi 5 are configured with more virtual address bits. Before ac1761d1dae8bf114a05e28ed6886deba6c2c860, WINEPRELOADER_LDFLAGS contained "-Wl,-Ttext=0x7d400000". After that commit, if the "-static-pie" option isn't supported, WINEPRELOADER_LDFLAGS ends up containing "-Wl,-Ttext=0x7d7d00000000" instead. I.e. - previously, we set the text section address of 0x7d400000, while we now set 0x7d7d00000000. The former is a 31 bit address, while the latter is a 47 bit address. Kernels with CONFIG_ARM64_VA_BITS_39=y just immediately segfault if they try to execute a binary linked with -Ttext=0x7d7d00000000. Any virtual address with 39 bits or fewer works, while higher addresses won't work. Reversing the change, setting -Wl,-Ttext=0x7d400000, makes the binaries work fine (in brief testing) on such aarch64 linux devices. I'm not sure if there's any immediate drawbacks to it - but I guess it would be nice to set an address with less than 39 bits, at least for aarch64. -- 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 59867] New: Cloudflare issue
by WineHQ Bugzilla June 21, 2026

June 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59867 Bug ID: 59867 Summary: Cloudflare issue Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)list.winehq.org Reporter: jackgaunt57(a)gmail.com I cannot seem to get past the Cloudflare, i have cleared my cash and have no extensions active, all cookies allowed. My only issue is that my chrome is an out of date version as my imac is from 2011 and i’m now just stuck on how to enter the site and i’m not sure how to go about asking for help for this. 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.

1 2

[Bug 59406] Super Hexagon: if gamepad is connected, game will ignore every input after selecting anything from title screen
by WineHQ Bugzilla June 21, 2026

June 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59406 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Rémi Bernon <rbernon(a)codeweavers.com> --- Should probably be fixed after 4377bdebd6b94ee8539b99599f4abaf1ad7e1904, please reopen if not. -- 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 0