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 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 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 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

[Bug 37821] New: Wisterer HX freeze on sunday event
by wine-bugs＠winehq.org June 4, 2026

June 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=37821 Bug ID: 37821 Summary: Wisterer HX freeze on sunday event Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sweepers(a)gmx.de Distribution: --- Created attachment 50371 --> https://bugs.winehq.org/attachment.cgi?id=50371 console log calling "wine wistererhx.exe" Hi, found a problem in windows application "Wisterer HX" Version 4.2.32 It's a lightweight software for calendar management, diary, adress database, schedule and birthday reminder etc. Unfortunately only available in german, but i'll try to translate... Homepage is http://www.wisterer.de but the download is redirected to other sites. download zip with setup exe: http://www.chip.de/downloads/Wisterer-HX_13002426.html After running setup.exe, the application complains about missing dlls. I got it starting up by copying these files from win7 x64 directory C:\Windows\SysWOW64 to ~/.wine/drive_c/Program Files (x86)/Wisterer HX ab412429f1e5fb9708a8cdea07479099 COMDLG32.OCX 8bbc59ae8497d0bbee8d66b74c7db971 mfc40.dll ae47a8a5fe8193bb84ffcd338115d8ef MSCOMCT2.OCX e52859fcb7a827cacfce7963184c7d24 MSCOMCTL.OCX 4dc9752ba6418bbac12852bbcf0374cb MsgHoo32.OCX 9618e4752b19ce24efd729c662c8db1e msvbvm60.dll 045a16822822426c305ea7280270a3d6 Richtx32.ocx download zip with portable version: http://www.computerbild.de/download/Wisterer-HX-Portable-2775828.html 51f4e5042c7a71ace966d0b47c080eb0 portablewistererhx.zip This zip contains partly different versions of dlls above, but problem is the same. While with Wine 1.6.2 program crashed when clicking on "Anzeige -> Monatsanzeige Liste" (view full month), this is now fixed with latest version Wine 1.7.33 - thanks for that :) But one problem remains: go to "Kalender" -> "Neues Ereignis eingeben" (enter new event) then select the tab "monatlich" (monthly) find "Mittwoch" (wednesday) in the drop down menu. Only if "Sonntag" (sunday) is selected, the app freezes, 100% CPU. This action prepares an event to be scheduled every first sunday each month, so obviously some problem with day of week calculation. Same happens if an existing calendar file Kalender.wik is opened that contains sunday events. Thank you! -- 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 4

[Bug 32879] New: Legacy 5 does not appear in task bar
by wine-bugs＠winehq.org June 4, 2026

June 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=32879 Bug #: 32879 Summary: Legacy 5 does not appear in task bar Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lsts67(a)aganderson.me.uk Classification: Unclassified Legacy 5 does not appear in task bar at any time. Once its window appears on the desktop, this doesn't matter too much, but if all windows get closed, say to access the desktop, I know of no way to find it again. I'm using Linux Mint 14, but the problem pre-dates that by some way, just haven't had time to report it. -- 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 5

[Bug 59358] New: Exact Audio Copy 1.8 crashes on start in latest unstable WINE
by WineHQ Bugzilla June 4, 2026

June 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59358 Bug ID: 59358 Summary: Exact Audio Copy 1.8 crashes on start in latest unstable WINE Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: alex.v.galvin(a)gmail.com Distribution: --- Created attachment 80294 --> http://bugs.winehq.org/attachment.cgi?id=80294 Error displayed on startup. Program exits after hitting OK. wine-11.1-114-g648e636256a crashes when running Exact Audio Copy 1.8. Can be reproduced by downloading https://www.exactaudiocopy.de/eac-1.8.exe, running or extracting the installer, and running the installed EAC.exe via your freshly-compiled WINE. The crash occurs using Mono or native libraries, and does not occur under stable version 11.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.

1 2

[Bug 53965] New: Writing a new line after writing a full end element(WriteFullEndElement)
by WineHQ Bugzilla June 3, 2026

June 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=53965 Bug ID: 53965 Summary: Writing a new line after writing a full end element(WriteFullEndElement) Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xmllite Assignee: wine-bugs(a)winehq.org Reporter: k.kahurani(a)gmail.com Distribution: --- Created attachment 73553 --> https://bugs.winehq.org/attachment.cgi?id=73553 Test case It doesn't look possible to write a whitespace character after writing a full end element with WriteFullEndElement. It looks to me like this should be possible just like it is possible with WriteEndElement. I have also noticed that native xmllite sometimes breaks(not sure whether this is a feature or a bug) but at times native xmllite doesn't write new lines after writing the elements. I'm not sure how exactly this happens but the possible work-around in this is to manually write new lines(with WriteWhitespace) which means this issue could easily break working code. I'm not sure how to fix this right away so I am submitting a bug. As can be seen in the attached diff, wine doesn't pass the test but native does. -- 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 4