January 2026 - Wine-Bugs - list.winehq.org

[Bug 59046] wine: Call to unimplemented function icu.dll.ulocdata_getCLDRVersion, aborting wine: Call to unimplemented function icu.dll.uloc_canonicalize, aborting

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59046 --- Comment #4 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- The ICU patches are reverted for Wine-11. Please try with a clean wine prefix. -- 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.

Jan. 2, 2026

[Bug 59046] wine: Call to unimplemented function icu.dll.ulocdata_getCLDRVersion, aborting wine: Call to unimplemented function icu.dll.uloc_canonicalize, aborting

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59046 Alistair <ajftonner(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ajftonner(a)gmail.com --- Comment #3 from Alistair <ajftonner(a)gmail.com> --- Interestingly I've hit this pair of errors. Specifically fedora 42 - XIVLauncher.x86_64 from copr (ver string: 1:1.3.1-1.fc42) wine: Built locally from wine-staging 11.0-rc4 (sadly I don't have the commit to hand) This does not directly affect XIVLauncher, but rather the Dalamud plugin environment. If I run the launcher and disable Dalamud, no issues, but with the Dalamud plugin suite enabled the launcher stalls with xivlauncher-core wine: Call from 00006FFFFF39D887 to unimplemented function icu.dll.ulocdata_getCLDRVersion, aborting wine: Call from 00006FFFFF39D887 to unimplemented function icu.dll.uloc_canonicalize, aborting It is *my* understanding that the Dalamud plugin suite relies heavily on DotNET codebase. Is there some sort of logging/tweaked building I can assist with on 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.

Jan. 2, 2026

[Bug 41689] Cyberduck crashes at launch

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=41689 Andrew Nguyen <arethusa26(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #56085|0 |1 is obsolete| | -- 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.

Jan. 1, 2026

[Bug 41689] Cyberduck crashes at launch

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=41689 Andrew Nguyen <arethusa26(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #56084|0 |1 is obsolete| | -- 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.

Jan. 1, 2026

[Bug 41689] Cyberduck crashes at launch

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=41689 Andrew Nguyen <arethusa26(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #56083|1 |0 is obsolete| | -- 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.

Jan. 1, 2026

[Bug 41689] Cyberduck crashes at launch

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=41689 Andrew Nguyen <arethusa26(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #11 from Andrew Nguyen <arethusa26(a)gmail.com> --- The crash on startup is still an issue in wine-11.0-rc4. I notice the same problem has been reported in the Cyberduck issue tracker here: https://github.com/iterate-ch/cyberduck/issues/15520 This comment https://github.com/iterate-ch/cyberduck/issues/15520#issuecomment-1892210028 seems to identify what is happening on the IKVM side that is causing an exception to be raised on startup. There is a call to System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule with the single name argument "<DynamicMethodHolder>" but the Wine Mono side also expects it to be a valid filename, hence the exception being thrown. This behavior is consistent with the last few lines of a Wine Mono trace with WINE_MONO_TRACE=N:System.IO: [00000024: 2.12102 1] ENTER:c System.IO.Path:GetFileName (string)([STRING:036242a0:<DynamicMethodHolder>]) [00000024:] EXCEPTION handling: System.ArgumentException: Illegal characters in path. [00000024:] EXCEPTION handling: System.TypeInitializationException: The type initializer for 'java.nio.charset.StandardCharsets' threw an exception. [00000024:] EXCEPTION handling: System.TypeInitializationException: The type initializer for 'org.apache.log4j.LogManager' threw an exception. * Assertion at /builds/mono/wine-mono/wine-mono-10.4.1/mono/mono/metadata/object.c:4679, condition `is_ok (error)' not met, function:prepare_run_main, (null) assembly:C:\windows\mono\mono-2.0\lib\mono\4.5\mscorlib.dll type:TypeInitializationException member:(null) -- 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.

Jan. 1, 2026

[Bug 59164] Wrong symlinks for users documents directories since v 10.0

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59164 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #2 from Zeb Figura <z.figura12(a)gmail.com> --- I have a similar setup with symlinks (although to another ext4 drive) and I haven't seen this. Can you attach a log of prefix creation with WINEDEBUG=+server,+shell,+mountmgr,+file ? -- 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.

Jan. 1, 2026

[Bug 58420] Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58420 --- Comment #8 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- I fear I hit now the same bug when trying something in wine gitlab. Running the cygwin64 installer it seems to show up in the post extraction scripts: running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash" abnormal exit: exit code=2816 ... https://gitlab.winehq.org/bernhardu/wine/-/jobs/219836/viewer#L593 A +seh,+module run shows these addresses: mapping PE file L"\\??\\C:\\cygwin64\\bin\\cygwin1.dll" at 0x6ffffc360000-0x6ffffc693000 ... code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=00006FFFFC4AC045 info[0]=0000000000000000 info[1]=FFFFFFFFFFFFFFFF rip=00006ffffc4ac045 rsp=00000007ffffb688 rbp=00000007ffffc0e0 eflags=00010212 rax=00000000000002e7 rbx=00000000000009d0 rcx=00000000ffffffff rdx=0000000000000000 rsi=0000000000000000 rdi=00000007ffffc040 r8=0000000000000000 r9=0000000000000000 r10=0000000800000000 r11=00006ffffc4abfc7 r12=000000010041cce4 r13=00000007ffffc138 r14=0000000000000001 r15=0000000000000000 mxcsr=00001f80 cs=0033 ss=002b https://gitlab.winehq.org/bernhardu/wine/-/jobs/219836/viewer#L6144 https://gitlab.winehq.org/bernhardu/wine/-/jobs/219836/viewer#L7291 In a local debugger with a similar cygwin installation and the package cygwin-debuginfo installed, this address points to the xsave64 instruction: wine 'c:\cygwin64\bin\bash.exe' --login -i $ gdb -q --args dash (gdb) starti (gdb) pipe info share | grep cygwin 0x00006ffffb7b1000 0x00006ffffbae1408 Yes /usr/bin/cygwin1.dll (gdb) b * (0x00006ffffb7b1000 - 0x1000) + (0x00006FFFFC4AC045 - 0x6ffffc360000) Breakpoint 1 at 0x6ffffb8fc045: file sigfe.s, line 134. (gdb) disassemble /r 0x6ffffb8fc045,0x6ffffb8fc045+6 Dump of assembler code from 0x6ffffb8fc045 to 0x6ffffb8fc04b: 0x00006ffffb8fc045 <sigdelayed+126>: 48 0f ae 64 24 30 xsave64 0x30(%rsp) End of assembler dump. And if I understand it right, the issue is the value of $rsp+30 needs to be a 64 bit aligned address, which unfortunately it is not: (gdb) print/x (0x00000007ffffb688+0x30) & 63 $1 = 0x38 -- 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.

Jan. 1, 2026

[Bug 59198] Holoearth: Launcher screen flicker on change or UI interaction

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59198 --- Comment #1 from amppotato(a)proton.me --- Created attachment 80073 --> http://bugs.winehq.org/attachment.cgi?id=80073 Comparison output in wine stable 10.0 -- 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.

Jan. 1, 2026

[Bug 59198] New: Holoearth: Launcher screen flicker on change or UI interaction

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59198 Bug ID: 59198 Summary: Holoearth: Launcher screen flicker on change or UI interaction Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: amppotato(a)proton.me Distribution: --- Created attachment 80072 --> http://bugs.winehq.org/attachment.cgi?id=80072 Wine stdout when interacting with the Launcher program In winehq-staging (Version 11.0-rc4, winehq-staging_11.0~rc4~trixie-1_amd64.deb), the Holoearth Launcher exhibits heavy flickering on each UI change. For example, if the user mouses over the Install/Start button, a frame of black screen is rendered over the window briefly. This does not happen when winehq-stable (Version 10.0, 10.0.0.0~trixie-1) is used instead. Steps to Reproduce: 1. Get the Holoearth installer from https://holoearth.com/en/download/ 2. Install it following the prompts, including the .NET 6 redistributable. 3. Launch the Launcher program with `wine $WINEPREFIX/drive_c/users/$(whoami)/AppData/Roaming/COVER\ corp/Holoearth\ Launcher/Launcher.exe` 3. Observe the flicker when interacting with the "Install" button on the lower right hand side. Additional Notes: No account creation is required to reproduce this, as it happens in the Launcher prior to any log in for this MMO. winetricks dxvk works around this, but that is not required for 10 / stable. However, a comparison test with wine 10 / stable DOES require `winetricks corefonts` because the launcher program will not start without that. I am not filing a bug report for that because it is does not happen in 11.0-rc4. -- 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.

Jan. 1, 2026