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

[Bug 23326] New: Cannot change printer settings, Family Tree 7
by wine-bugs＠winehq.org June 8, 2026

June 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=23326 Summary: Cannot change printer settings, Family Tree 7 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jamesl(a)bestweb.net Created an attachment (id=29072) --> (http://bugs.winehq.org/attachment.cgi?id=29072) FTW7 print dialogue, compare Wine to XP Cannot select printer/change print settings with Family Tree Maker 7. Dialogue box comes up, drop-down boxes are working, but radio buttons for switching between "default printer" and an alternate printer are not selectable. Have compared the print dialogue between Wine vs a native install under Windows XP (SP3) and notice some text from the Windows install does not show up under Wine. Also tried the same thing with the "free" version of FTM2005se available at http://past.familytreemaker.com/download/starter.aspx and found it's behavior is the same. So I will describe steps from there, since it would be eaier for someone to get that to test against. STEPS TO RECREATE: 1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005 winecfg"; set winver to "Windows XP", point the Documents directory under Desktop Integration to my own Documents directory 2: install FTW2005 by running "WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine ./FamilyTreeMaker2005se.exe", accept all defaults. 3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later" from popup window (does not affect outcome, as same print problem occurrs in a regular retail version of FTM7) 4: create new file, or use existing file (same result either way) 5: select "File | Print Setup", then try to select radio button for either "Default Printer" or "Specific Printer". Neither can be selected 6: try selecting a "specific printer" from drop-down box. Printer can be selected, but radio buttons still not functional. 7: after selecting a printer other than the default (such as print-to-PDF) and then try printing. Output will still go to the Linux default printer, no edits of the print settings will take effect. The "Family Archive Viewer v6.0" at http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer v11.0" at http://www.genealogy.com/abtffiv.html are other variants that exhibits this behavior. Have attached sample screenshots of Wine vs WinXP versions of the print dialogue. -- 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.

3 18

[Bug 56681] New: 3d games continue receiving mouse input while not focused
by WineHQ Bugzilla June 8, 2026

June 8, 2026

https://bugs.winehq.org/show_bug.cgi?id=56681 Bug ID: 56681 Summary: 3d games continue receiving mouse input while not focused Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine wayland windows seem to get the mouse input even if the application window is not focused. 3D game world continues to respond to mouse input as if the game still had focus. To reproduce: -launch a 3d game in wayland mode (warframe in my example) -open another application and make sure it has focus -observe that when the mouse cursor is over the game window, game still receives input -- 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 13

[Bug 57229] New: Wine apps are unable to open OAuth redirect URLs using the cron:// prefix (probably others too, if they exist)
by WineHQ Bugzilla June 8, 2026

June 8, 2026

https://bugs.winehq.org/show_bug.cgi?id=57229 Bug ID: 57229 Summary: Wine apps are unable to open OAuth redirect URLs using the cron:// prefix (probably others too, if they exist) Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ezequiel.ezb(a)gmail.com Distribution: --- I’ve been trying to log into Notion and Notion Calendar, but without success. These apps require logging into your Google account using OAuth. When selecting this option, you’re redirected to your browser to log in. After logging in, a URL starting with “cron://” is generated, such as: cron://calendar.notion.so/auth?state=provider%3Dgoogle%26client%3Dweb-electron%26nonce%xxxxx%calendar.notion.so&code=xxxxxxxxx&scope=email profile https://www.googleapis.com/auth/directory.readonly openid https://www.googleapis.com/auth/admin.directory.resource.calendar.readonly https://www.googleapis.com/auth/contacts.other.readonly https://www.googleapis.com/auth/contacts https://www.googleapis.com/auth/calendar.settings.readonly https://www.googleapis.com/auth/calendar.events https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email&authuser=0&prompt=consent. I removed specific data for privacy. This URL should redirect to the originating app, but Wine doesn’t handle this correctly. Solving this involves modifying xdg MIME types, which is complex and imperfect. Associating a Wine app with the cron:// URL protocol means all such URLs are sent to a single app, which may not be the correct one. -- 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 59651] New: Greenfish Icon Editor errors on launch with MDB error: Input/Output error
by WineHQ Bugzilla June 7, 2026

June 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=59651 Bug ID: 59651 Summary: Greenfish Icon Editor errors on launch with MDB error: Input/Output error Product: Wine Version: 11.6 Hardware: x86-64 URL: https://greenfishsoftware.org/gfie.php OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tobbi.bugs(a)googlemail.com % ./wine --version wine-11.6-112-g504683b22d3 % openssl sha256 gfie4.5.zip SHA2-256(gfie4.5.zip)= 7cc9b150b3e09e1d59b162fc5aa1073387c91003f1dd6e75749067ae4af3f533 Steps to reproduce: 1. Extract the zip file and start gfie.exe using wine. Expected results: Program starts. Actual results: Error message: MDB error: Input/Output error. -- 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 8

[Bug 59803] New: Program crash on debugger interrupt in wow64 mode
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59803 Bug ID: 59803 Summary: Program crash on debugger interrupt in wow64 mode Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)list.winehq.org Reporter: wine(a)tomashu.dev Distribution: --- Created attachment 81045 --> http://bugs.winehq.org/attachment.cgi?id=81045 backtrace Distro: CachyOS When debugging a 32-bit program in wow64 mode, trying to interrupt its execution with Ctrl+C causes it to crash. As an example, let's take wine's `notepad.exe` as it has both 64 and 32 bit versions. Steps to reproduce: 1. change directory to <wine_prefix>/drive_c/windows 2. launch 32bit version: `winedbg syswow64/notepad.exe` 3. continue program execution (with `c`) 4. interrupt the program (with `Ctrl+C`) 5. the program crashes. The window still exists, but is not responsive. 6. Exit debugger (with `quit`) Repeating the same steps but with 64 bit version does not result in a crash 2. launch 64bit version: `winedbg system32/notepad.exe` Interestingly, when launching e.g. `syswow64/regedit.exe`, the UI doesn't become unresponsive after the crash and continues to work. Maybe its related to multithreading? -- 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 59303] New: FlatOut 2 has not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3.
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59303 Bug ID: 59303 Summary: FlatOut 2 has not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3. Product: vkd3d Version: 1.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 083c:fixme:d3d_shader:shader_spirv_compile_shader Shader log: 083c:fixme:d3d_shader:shader_spirv_compile_shader <anonymous>: E9000: Aborting due to not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3. 083c:fixme:d3d_shader:shader_spirv_compile_shader 083c:err:d3d_shader:shader_spirv_compile_shader Failed to compile shader, ret -5. 083c:err:d3d:wined3d_context_vk_apply_draw_state No pipeline layout set. 083c:err:d3d:adapter_vk_draw_primitive Failed to apply draw state. vkd3d-1.18-211-gd9210a62 -- 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 8

[Bug 58668] New: SolidWorks - Certain buttons fail to trigger actions
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=58668 Bug ID: 58668 Summary: SolidWorks - Certain buttons fail to trigger actions Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- Created attachment 79253 --> http://bugs.winehq.org/attachment.cgi?id=79253 SolidWorks 2023 buttons not working on Wine-10.14 Clicking certain buttons in SolidWorks no longer trigger an action, but stop at selecting the button instead. This bug must have been introduced some time after wine-9.22, as wine-9.22 works fine. Please see attached screen grab for SolidWorks 2023sp05: The buttons in question are - <Close>, aka green tick mark - "Rectangle Type" selection When building wine-10.14 from source, replacing the wine-10.14 folder "dlls/comctl32" with the older one from wine-9.22 fixes the problem and the SolidWorks buttons work again. -- 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 7

[Bug 59811] New: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59811 Bug ID: 59811 Summary: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10 Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: DANIELE.AMODEO(a)OUTLOOK.COM Distribution: --- Red Dead Redemption 2 fails to launch with "Error Code 18: failed to initialize graphics device" since upgrading Wine Staging from 11.9 to 11.10. Downgrading back to Wine Staging 11.9 immediately resolves the issue. System: - OS: Arch Linux - GPU: AMD Radeon RX 6950 XT - Driver: RADV Mesa 26.1.1 - Wine mode: wow64 (64-bit prefix) - DXVK and VKD3D installed via winetricks - Graphics API set to kSettingAPI_DX12 in system.xml Steps to reproduce: 1. Install Wine Staging 11.10 2. Launch Red Dead Redemption 2 via Wine 3. Error Code 18 appears immediately, game does not start Expected: game launches normally (as it did with 11.9) Actual: "Rockstar Games failed to initialize graphics device. Error Code: 18" Suspected cause: dcomp-DCompositionCreateDevice2 patches introduced in 11.10. -- 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 59793] New: zeiss zen lite fails to install - installer crashes
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59793 Bug ID: 59793 Summary: zeiss zen lite fails to install - installer crashes Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 81031 --> http://bugs.winehq.org/attachment.cgi?id=81031 backtrace of crash when trying to install ZeissZenLite Trying to install zeiss zen lite (download is available from here [1]) in a new WINEPREFIX fails with a crash. The backtrace is attached. [1] https://www.zeiss.com/microscopy/en/products/software/zeiss-zen-lite.html [2] https://zeiss-microscopy-installer.azureedge.net/public/latest/ZeissMicrosc… -- 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 7

[Bug 59679] New: Some sections of PKHeX crash with Wine 11.5+
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59679 Bug ID: 59679 Summary: Some sections of PKHeX crash with Wine 11.5+ Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tw0ali(a)tutanota.com Distribution: --- Created attachment 80775 --> http://bugs.winehq.org/attachment.cgi?id=80775 PKHeX logs Some sections of PKHeX crash starting from Wine version 11.5 (including 11.6 and 11.7). For example, “Trainer Info” or the “Search” button in the boxes. This bug is not reproducible in version 11.4, which is the last version without issues. -- 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