wine-bugs January 2025

wine-bugs@winehq.org

1 participants
1447 discussions

[Bug 56920] New: Family Tree Maker 2019 fails to start with unhandled exception
by WineHQ Bugzilla 24 Jun '25

24 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56920 Bug ID: 56920 Summary: Family Tree Maker 2019 fails to start with unhandled exception Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jwhite88(a)gmail.com Distribution: --- Created attachment 76741 --> https://bugs.winehq.org/attachment.cgi?id=76741 Terminal output when trying to run Family Tree Maker 2019 FTM 2019 successfully installs (it prompts to install Visual C++ Redistributable for Visual Studio 2017 as part of the process) but then fails to start. It produces an unhandled exception (see attached log) and then hangs in the terminal. -- 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 1

[Bug 44236] New: Poisson Superfish: Slow to write binary file.
by wine-bugs＠winehq.org 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=44236 Bug ID: 44236 Summary: Poisson Superfish: Slow to write binary file. Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: raphaelcervantes(a)protonmail.com Distribution: --- Discussion is in this forum. https://forum.winehq.org/viewtopic.php?f=2&t=29936 I am using Wine to run Poisson Superfish. This program essentially does some calculations and then writes the results into a binary file. This action is performed in less than a second in a Windows environment. Unfortunately, it takes about 10 seconds to write this binary file under Wine. Here is how to reproduce the error: 1. Install Poisson Superfish on linux using Wine. You have to scroll all the way down and click register. http://laacg.lanl.gov/laacg/services/download_sf.phtml 2. Once installed, open a unix terminal in this directory .../.wine/drive_c/LANL/Examples/RadioFrequency/Waveguides/ 3. Run wineconsole cmd. 4. In the new window, run RUNWG.BAT. 3. Several windows will pop up. The ones that stall for a bit are in the process of writing to a file named something.T35. The T35 refers to tape 35 (I guess that's how a sector of harddrive memory would be referred as back in the 80s). This is the binary file with the solution in it. It will finish eventually, but it is pretty slow. -- 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 8

[Bug 44066] New: mintty/msys2 doesn't work since wine 2.5.0 (named pipes)
by wine-bugs＠winehq.org 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=44066 Bug ID: 44066 Summary: mintty/msys2 doesn't work since wine 2.5.0 (named pipes) Product: Wine-staging Version: 2.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.gursky(a)e-mail.ua CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Hi! According to [1], I'm opening a new issue. msys2 (based on Cygwin up to 2.5.x) does work on wine-staging. Since 2.5.0 mintty starts but has no visible output. You can work only blindly (ctrl+d closes the session). Actually I've expected that since wine 2.5 msys2 will work not only on wine-staging but also on wine. Unfortunately the opposite has happened. Regards, Andrey [1] https://bugs.winehq.org/show_bug.cgi?id=17195#c189 -- 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 52646] New: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error.
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=52646 Bug ID: 52646 Summary: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error. Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: madeinclt26(a)gmail.com Distribution: --- Created attachment 71966 --> https://bugs.winehq.org/attachment.cgi?id=71966 After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. -- 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 13

[Bug 31212] New: Some VST instruments crash when reloaded in Mixcraft
by wine-bugs＠winehq.org 23 Jun '25

23 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=31212 Bug #: 31212 Summary: Some VST instruments crash when reloaded in Mixcraft Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: s_chriscollins(a)hotmail.com Classification: Unclassified In Mixcraft, some VST instruments crash when loaded a second time on a track. However, the same instruments work fine when loaded for the first time on a track. The following can be reproduced easily in Mixcraft: 1. Start Mixcraft and select "Build Virtual Instrument Tracks" from the "New Project" window. 2. Click on the keyboard icon next to the first track name, which will bring up the instrument selection window. 3. Select "<VSTi Instruments>" from the left pane and then "Messiah" from the right pane. This sets the track to use the Messiah VSTi synth. 4. Now select "Acoustica Instruments" from the right pane. 5. Once again, select "Messiah" from the right pane. Mixcraft will pop up an error box with the title "An instrument has crashed" containing the following text: "A crash has been detected in the instrument "Messiah." This plug-in has been muted. We recommend you save your project and re-start Mixcraft to avoid losing your work." Unfortunately, no helpful terminal output seems to be generated in relation to the plugin crash. I have provided more detailed notes on VST behavior in Mixcraft here: https://docs.google.com/document/d/1YEPh0mkd_ip1whAJXcRIl4HYny5D8LSeGo3qgzV… ** My System ** OS: Kubuntu 12.04 64-bit w/ KDE SC 4.8.4 Motherboard: ASRock X58 Extreme3 (Intel X58 chipset) CPU: Intel Core i7 (2.8 GHz quad-core) RAM: 12GB DDR3 Video: Dell NVIDIA GeForce 7800 GTX w/ 256 MB RAM (PCI Express) Sound Card #1: Sound Blaster Audigy 2 ZS Gold Sound Card #2: Echo Gina3G Linux Kernel: 3.2.0-26-generic NVIDIA video driver: 302.17 Screen Resolution: 1280 x 960 -- 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 15

[Bug 54975] New: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=54975 Bug ID: 54975 Summary: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- win32u:win32u exits prematurely, leaves child process behind: win32u:win32u start dlls/win32u/tests/win32u.c [...] win32u.c:1037: Test marked todo: res = 4 win32u.c:1040: Test marked todo: buf[1] = 0 win32u:win32u:09f0 done (0) in 0s 1295B win32u.c:1045: Test failed: res = 0 win32u.c:1046: Test failed: buf = d win32u.c:1049: Test failed: res = 0 win32u.c:1059: Test failed: res = 0 09e0:win32u: 14 tests executed (2 marked as todo, 0 as flaky, 4 failures), 0 skipped. See https://test.winehq.org/data/patterns.html#win32u:win32u There are two things to notice in the above log: * The main win32u:win32u process is 09e0 but it did not issue a 'tests executed' summary. This means it exited prematurely. * 09e0 is a child process that continues running and printing messages which interferes with the next test, specifically windows.globalization:globalization. Also on the TestBot one can find the corresponding Wine log which contains these lines that seem strongly correlated to this issue: 0480:err:seh:KiUserCallbackDispatcher ignoring exception 0480:err:seh:KiUserCallbackDispatcher ignoring exception wine client error:480: partial write 57344 Running: win32u:win32u (694 of 774) Running tests - 6 failures This issue only happens on Linux and happens systematically but only on three configurations: fg-deb64-t32 but not for the wow32 and wow64 builds on the same machine fgtb-debian11-wow64 but not for the wow32 build on the same machine debian11b-wow64 but but not for the wow32 build on the same machine (and none of the 32-bit builds on debian11 is impacted) And I have been unable to reproduce this failure on my machine (fg-deb64-t32). So it's unclear what causes this failure but it clearly started on 2023-05-15 so it's probably some commit on that day. -- 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 55143] New: unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566)
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55143 Bug ID: 55143 Summary: unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566) Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: zeroredgrave(a)gmail.com Distribution: --- Created attachment 74705 --> https://bugs.winehq.org/attachment.cgi?id=74705 Cannot Launch the App probably the introduction of the game( before main menu) cannot create a video decoder i think Max Payne 2 Cannot Launch due an unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566) -- 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 37

[Bug 50577] New: Saya no Uta: hangs on RtlpWaitForCriticalSection
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=50577 Bug ID: 50577 Summary: Saya no Uta: hangs on RtlpWaitForCriticalSection Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 69251 --> https://bugs.winehq.org/attachment.cgi?id=69251 terminal output at default settings Note: This is about the Japanese "Windows 10 compatible" release, not an English localised one. There is no demo version, I'm afraid. The game runs fine--until it hangs at: 012c:err:ntdll:RtlpWaitForCriticalSection section 103971A4 "?" wait timed out in thread 012c, blocked by 0024, retrying (60 sec) The hang may happen, after as little as 1 min, sometimes it's 10 min, and I might have made it 20 min once. When it happens, it does not recover, the message just repeats every once in a while. I'm using the Ubuntu packages from the official winehq repo. Originally I tried with wine-staging 6.0, then I went backwards version by version through (wine-staging) 5.18, and finally now I'm on (wine-devel) 6.0 for this bug report. No discernable difference either way. The run in the attached log happened in a clean prefix (though I admit I may have forgotten to wipe the prefix between some downgrades). -- 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 12

[Bug 50484] New: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=50484 Bug ID: 50484 Summary: Far Manager 3 crashes when Shift+Enter Execute in separate window pressed Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: lanthruster(a)gmail.com Distribution: --- Far Manager 3 crashes when executing a file association. 1. Download and extract farmanager3 https://www.farmanager.com/download.php?l=en (zip archive) 2. Create a text file with no or arbitrary content test.txt 3. Select test.txt and press Shift + Enter Wine will crash. That bug was there for years, including Wine 2.3 and earlier releases. -- 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 9

[Bug 44253] New: Access violation in multiple cases
by wine-bugs＠winehq.org 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=44253 Bug ID: 44253 Summary: Access violation in multiple cases Product: Wine Version: 3.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ihormcd+wine(a)gmail.com Distribution: --- Created attachment 60052 --> https://bugs.winehq.org/attachment.cgi?id=60052 crash Access violation exception due to access by 0x0000 address in multiple use cases while using Far3. >From Far app try to: 1) on lunch of EXE file (Far.exe, WinMergeU.exe, others) 2) switch drive for the pane (Alt+F1/F2) 3) switch to Quick view mode for a file (Ctrl+Q) *) few other cases App: Far Manager 3.0 build 5100 x64 Wine details: wine-3.0-rc3, the app runs using wineconsole -- 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 17

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2025