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

[Bug 60137] Notion Installer Immediately Crashes

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60137 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.notion.com/desk | |top Status|UNCONFIRMED |NEW Keywords| |download Ever confirmed|0 |1 --- Comment #7 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- I see this when compiling --without-mingw. There's no crash with the official DEBs. Did you compile Wine 11.14 yourself? Did you use --without-mingw? Which distro do you use? -- 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.

Aug. 8, 2026

[Bug 60142] New: CertGetCertificateContextProperty does not support CERT_SIGN_HASH_CNG_ALG_PROP_ID

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60142 Bug ID: 60142 Summary: CertGetCertificateContextProperty does not support CERT_SIGN_HASH_CNG_ALG_PROP_ID Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)list.winehq.org Reporter: kedarh(a)microsoft.com Target Milestone: --- Distribution: --- Created attachment 81741 --> http://bugs.winehq.org/attachment.cgi?id=81741 sample code showing failure to retrieve key and signing algorithm from cert Calling CertGetCertificateContextProperty on a CERT_CONTEXT with property CERT_SIGN_HASH_CNG_ALG_PROP_ID fails with CRYPT_E_NOT_FOUND. Can this be supported? -- 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.

Aug. 7, 2026

[Bug 60141] New: CertCreateSelfSignCertificate with default parameters makes insecure RSA 512 cert

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60141 Bug ID: 60141 Summary: CertCreateSelfSignCertificate with default parameters makes insecure RSA 512 cert Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)list.winehq.org Reporter: kedarh(a)microsoft.com Target Milestone: --- Distribution: --- Created attachment 81740 --> http://bugs.winehq.org/attachment.cgi?id=81740 sample program that creates a self signed cert using default parameters and writes it to disk On Win10+, if you call CertCreateSelfSignCertificate and pass in default parameters like hCryptProvOrNCryptKey=NULL and pKeyProvInfo=NULL, the resulting certificate has an RSA 1024 public key. On Wine 10.0, it generates a certificate with an RSA 512 key. There are a few significant downsides here: 1. It is a difference in behavior from Win10 and Win11 default configuration. 2. RSA 512 is widely considered to be deprecated. 3. RSA 512 does not work properly for signing and signature validation. See the bug I just filed: Bug 60140. Why point #3 matters is that in TLS, modern versions of Windows Server, rsa_pss_rsae_sha256 (0x0804) is at the top of the signature algorithm list in the Certificate Request message (when client certificates are used), so if the client generates an RSA 512 key, it will never succeed the TLS negotiation. There are surely clients using default parameters to CertCreateSelfSignCertificate that used to work, but will fail to connect to certain TLS servers now. I've attached a sample program that demonstrates the issue. ----- The reason why this is happening, at least in part, is that CertCreateSelfSignCertificate calls CRYPT_CreateKeyProv when hProv is not passed in, which calls if (CryptAcquireContextW( &hProv, container, MS_DEF_PROV_W, PROV_RSA_FULL, CRYPT_NEWKEYSET )) https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/crypt32/cert.c#L3786 MS_DEF_PROV_W is the "Base" cryptographic provider, which is set to use the default key length 512: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/rsaenh/rsaenh.c?ref_… On Windows, the default provider is set via registry key on a per purpose basis (can be different for signature, key exchange, etc..). A good way to fix this would be to use a similar registry lookup for it, and use the same default that Win10 and Win11 use today: the "Enhanced" provider. -- 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.

Aug. 7, 2026

[Bug 59186] Starcraft 2 detects wrong graphics card

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59186 --- Comment #60 from calmstorm(a)posteo.de --- (In reply to Stian Low from comment #59) > (In reply to calmstorm from comment #58) > > If so tell me how specifically to do so. if the latter I mean. > > Reporter suggests trying combos of the 3 flags listed (reemit,sync,stall) > specifically for UHD Graphics 620: > - INTEL_DEBUG=reemit,sync,stall ### FOR RDR1 > - INTEL_DEBUG=reemit ### FOR RE2R > > So for example: > > INTEL_DEBUG=reemit,sync,stall wine Starcraft2.exe > > > Mesa 3d docs for flags that may further help debug/workaround performance > issues for UHD Graphics 620: > - > https://gallium.readthedocs.io/en/latest/envvars.html#i945-i965-driver- > environment-variables-non-gallium > > Please report if any combo of flags improve performance because it may help > wine better support your type of graphics card without requiring those > workarounds. Seemed to slow it down when I first booted into SC2. I don't know if it helps when you actually in game though. From what I saw though it didn't look like it helped at all. -- 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.

Aug. 7, 2026

[Bug 60140] New: Signature from BCryptSignHash with RSA 512 key and PSS padding cannot be verified

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60140 Bug ID: 60140 Summary: Signature from BCryptSignHash with RSA 512 key and PSS padding cannot be verified Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)list.winehq.org Reporter: kedarh(a)microsoft.com Target Milestone: --- Distribution: --- Created attachment 81739 --> http://bugs.winehq.org/attachment.cgi?id=81739 sample C++ application that signs data and verifies signature Signing data using BCryptSignHash with an RSA 512-bit key and BCRYPT_PAD_PSS successfully produces a signature, but using the same key pair to validate the signature fails with STATUS_INVALID_SIGNATURE. There are a few problems with this: 1. The same BCryptSignHash with RSA 512 key and PSS padding on Win10 or Win11 fails with STATUS_INVALID_PARAMETER. That's a behavior difference with Windows. 2. Of course, the signature validation failure is an error too. I'm attaching a minimal repro that demonstrates the problem. -- 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.

Aug. 7, 2026

[Bug 59726] Syscall emulation on Linux using Syscall User Dispatch broken with glibc < 2.34

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59726 --- Comment #21 from Zeb Figura <z.figura12(a)gmail.com> --- Thank you, it does seem to be working correctly then! -- 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.

Aug. 7, 2026

[Bug 21940] Rise of Legends Demo crashes with null pointer reference in msxml3?

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=21940 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #31 from Stian Low <wineryyyyy(a)gmail.com> --- Created attachment 81738 --> http://bugs.winehq.org/attachment.cgi?id=81738 Screenshots demo launch crash fixed via WINEDLLOVERRIDES="d3dx9_27=n,b for wine-11.14-a37867ddf84 for renderer=gl and vulkan (gl works, vulkan bugged) (In reply to Nikolay Sivov from comment #30) > With current wine I had to set d3dx9_27 to native,builtin (it's used for > shader compilation), and after that the game starts. Doesn't look like that > linked patch is important here. > > Could someone please retest? The original msxml crash is likely still there > with wine-11.0, could use that as a bad version. Confirming d3dx9_27 native override seems all that is needed for support for latest. I'll report renderer=vulkan bugs if not already covered by existing bug reports. -- 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.

Aug. 7, 2026

[Bug 60012] HOTAS controlls by WinWing are not recognized and even aggresively mapped as some x-box controller.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60012 0x_ontos <winehq.faculty027(a)simplelogin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from 0x_ontos <winehq.faculty027(a)simplelogin.com> --- The fix was merged. -- 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.

Aug. 7, 2026

[Bug 60112] msvcrt: fopen incorrectly uses CreateFileW instead of CreateFileA

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60112 --- Comment #1 from Bartosz <gang65(a)poczta.onet.pl> --- Thanks for the patch. Could you please create Merge Request in git repository: https://gitlab.winehq.org/wine/wine/-/merge_requests -- 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.

Aug. 7, 2026

[Bug 60112] msvcrt: fopen incorrectly uses CreateFileW instead of CreateFileA

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=60112 Bartosz <gang65(a)poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65(a)poczta.onet.pl -- 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.

Aug. 7, 2026