September 2025 - Wine-bugs - list.winehq.org

[Bug 32715] New: Running of Linux Live USB causes kernel32 to blow up
by wine-bugs＠winehq.org 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=32715 Bug #: 32715 Summary: Running of Linux Live USB causes kernel32 to blow up Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: raj(a)upadhyaya.com Classification: Unclassified Created attachment 43167 --> http://bugs.winehq.org/attachment.cgi?id=43167 Backtrace of blow up I began testing Linux Live USB creator on Linux. I am running wine version wine-1.5.18 installed via YUM on Fedora 18, using the linux kernel 3.8.0-rc3 compiled from source from www.kernel.org. What Linux Live USB does, is it creates a Live USB Linux USB thumb drive from an ISO. I keep a Windows XP partition around to run this program. My hope is to use Wine to run this program and create Linux thumb drives. Live Linux USB should task Wine, as it looks for new updates and other information from its web site. Back Trace attached... -- 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 9

[Bug 58550] New: Native host executable is run asynchronously
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58550 Bug ID: 58550 Summary: Native host executable is run asynchronously Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: Bjoern(a)Kautler.net Distribution: --- Some context to understand the use-case: I have a build that runs on CI agents running Linux. That build runs InnoSetup through wine to build an EXE installer. To sign the executable you can give InnoSetup a command to run (signing after building is not possible, because there is also an uninstaller built into the result that also needs signing. For the signing I use JSign which cross-platform can sign executables using a remote sign server. JSign is a Java program. I want to avoid provisioning a separate Windows Java Runtime just for that task. So I have a .bat file that translates the path of the signable file from wine path to Linux path. Now I need to call the host systems Java runtime with that path and wait for it to finish. I tried various things. I tried like the FAQ suggests to add . to PATHEXT and just call the Linux executable. This works from the commandline like wine /usr/lib/jvm/java-11-openjdk-amd64/bin/java but also does not wait for the process to finish, if you do wine /usr/lib/jvm/java-11-openjdk-amd64/bin/java; echo FOO you see the FOO before the Java output. Furthermore it does not work from inside the .bat file. I also tried with START /B /D . /WAIT /UNIX /usr/lib/jvm/java-11-openjdk-amd64/bin/java This even works without manipulating PATHEXT. But is also does not wait for the process to finish, despite the /WAIT. It immediately returns and then further processing fails as JSign sees the file is not signed yet after the process seemingly ended. So it seems wine never waits for the process to end, no matter what I use but immediately returns, making further processing impossible. -- 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 3

[Bug 58584] New: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58584 Bug ID: 58584 Summary: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: waser(a)waser.tech Distribution: --- This report details a consistent, immediate startup crash in `CONCRT140.dll` affecting modern S.T.A.L.K.E.R. engine forks. These engines are based on the open-source **Open X-Ray 1.6**, which itself works flawlessly under Wine. The crash only appears in these newer, more advanced forks which leverage the MSVC concurrency runtime for performance. This strongly indicates the issue lies within Wine's implementation of these APIs, not a bug in the engines themselves. This is effectively a regression, as the baseline engine works while the newer, concurrency-enabled versions do not. **Existing Related Bugs:** This issue appears to be a new, highly reproducible test case for known problems in Wine's concurrency support. We are filing this as a new report due to the unique test case and the specific failure point (constructor vs. destructor), but it is likely caused by the same underlying issues as: - **Bug 52899:** Notes that `CONCRT140.dll` requires `CreateEventExW` from `kernel32`. This is the most likely root cause. - **Bug 41749:** Shows a crash in the destructor for `Concurrency::details::_TaskCollection`. Our crash occurs in the *constructor* of this same object, demonstrating a different failing code path. Our report provides two clear methods to reproduce this crash, including one that is fully free and requires no commercial software. --- ### **Primary Reproduction Steps (IX-Ray on S.T.A.L.K.E.R.: Call of Pripyat)** *(Steps 1-5 as in previous draft)* 6. **Run the Game with Debug Logging:** Launch the game using its main executable with full debug channels enabled. ```bash WINEDEBUG=+all wine Stalker-COP.exe &> stalker_cop_crash_all.log WINEDEBUG=+seh,+loaddll wine Stalker-COP.exe &> stalker_cop_crash_seh.log ``` 7. **Result:** The process will crash immediately. The game's own crash log (in `_appdata_ixray_/logs`) and the attached Wine debug logs will show a fatal error in `CONCRT140.dll`. --- ### **Alternative Reproduction Steps (AOEngine on S.T.A.L.K.E.R. Anomaly)** This method is fully free and requires no commercial game assets. 1. **Download S.T.A.L.K.E.R. Anomaly:** Download the standalone game from its [ModDB page](https://www.moddb.com/mods/stalker-anomaly/downloads). 2. **Download AOEngine:** Download the latest AOEngine release from its [ModDB addons page](https://www.moddb.com/mods/stalker-anomaly/addons/aoengine). 3. **Install AOEngine:** Extract the contents into the Anomaly game's `bin` directory, overwriting `AnomalyDX11.exe`. 4. **Create a Clean Wine Prefix:** ```bash export WINEPREFIX=~/.wine_anomaly rm -rf $WINEPREFIX && wineboot -u ``` 5. **Install Runtimes:** ```bash winetricks -q vcrun2022 d3dcompiler_47 ``` 6. **Run the Game with Debug Logging:** Launch the game using the Anomaly launcher. ```bash WINEDEBUG=+all wine AnomalyLauncher.exe &> anomaly_crash_all.log WINEDEBUG=++seh,+loaddll wine AnomalyLauncher.exe &> anomaly_crash_seh.log ``` (Within the launcher, disable AVX, select DX11, disable the shader cache, and click Play). 7. **Result:** The exact same crash behavior as the IX-Ray method will be observed. The game's crash log will be in `_appdata_/logs` and the full Wine log will be `anomaly_crash_*.log`. --- **Expected Behavior:** The game launcher should appear, and the game should launch to the main menu successfully, as it does on Windows and as the baseline Open X-Ray 1.6 engine does under Wine. **Logs:** Three files will be attached for the primary reproduction case: 1. `stalker_cop_crash_seh.log`: A small log with `+seh,+loaddll` for quick initial review. 2. `stalker_cop_crash_all.log.bz2`: The complete `+all` debug log, compressed with bzip2 due to its large size. 3. `ixray-2025.08.10-02.37.21-waser.log`: The game's own crash log from its `_appdata_ixray_/logs` directory. **References:** - **IX-Ray GitHub (Open Source Engine):** https://github.com/ixray-team/ixray-1.6-stcop - **GE-Proton Issue #197 (Full History):** https://github.com/GloriousEggroll/proton-ge-custom/issues/197 -- 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 26

[Bug 56937] New: Alice madness return was unable to run under wow64
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=56937 Bug ID: 56937 Summary: Alice madness return was unable to run under wow64 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436.tw(a)gmail.com Distribution: --- Alice madness return will show AWC.dll load failed. But it normal under none wow build Environment ubuntu 20.04 wine version lastest master commit 797df8df394 -- 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 34516] New: Terragen fails to start
by wine-bugs＠winehq.org 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=34516 Bug #: 34516 Summary: Terragen fails to start Product: Wine Version: 1.7.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Classification: Unclassified Created attachment 45946 --> http://bugs.winehq.org/attachment.cgi?id=45946 Terminal output on Wine 1.7.2 Steps to reproduce: 1) remove ~/.wine 2) install Terragen 3) wine tgd.exe 4) click "Use free version" Behaviour: Wine error. Expected behaviour: No Wine error. -- 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 9

[Bug 58591] New: Brother P-Touch Editor crashes
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58591 Bug ID: 58591 Summary: Brother P-Touch Editor crashes Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: air.lightz(a)gmail.com Distribution: --- Created attachment 79121 --> http://bugs.winehq.org/attachment.cgi?id=79121 description? is this a joke? Tried to use Brother P-Touch Editor software to create shipping labels for work, and it fails catastrophically when trying to open it I am using Linux Mint and installed wine with a simple 'apt install -y wine' And I am a novice user, so no clue where to go from here Also, this website is way too difficult to report bugs on, terrible UX and way to many hoops to jump through. The epitome of why people hate linux. Good 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 12

[Bug 58594] New: Teraterm 5.4.1 / Serial communication not functional
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58594 Bug ID: 58594 Summary: Teraterm 5.4.1 / Serial communication not functional Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janne.kekkonen(a)gmail.com Distribution: --- Tested with Wine 10.12 on Ubuntu 22.04 running on VMware. When data is sent to serial port teraterm GUI become sluggish/unusable. Menu's do not work and data sent to serial port is not shown. When data sending is stopped GUI starts to work normally and data is shown on terminal. Functionality is pretty much the same as in bug-58142 Tests steps: - Connect USB-serial port to system. - Open serial port with teraterm & set settings(baud,stop bits...) - Start sending data to serial port. - Try to open menus. Not sure is this possible to reproduce with virtual serialport(s) Download link: https://github.com/TeraTermProject/teraterm/releases/download/v5.4.1/terate… -- 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 58561] New: Guildwars 2 Trading post is crashing
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58561 Bug ID: 58561 Summary: Guildwars 2 Trading post is crashing Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emethorst(a)gmail.com Distribution: --- Created attachment 79068 --> http://bugs.winehq.org/attachment.cgi?id=79068 Trading Post backlog The problem is application specific and it local to Guildwars 2. I can run the game just fine, but when opening the Trading Post (this is where players sell their loot) it crashed. This means after a while of playing all your inventory is full and you can't sell it anymore. This is kind of an issue. I am running on the latest (freshly installed) kubuntu uname -a gives: Linux [My machine name] 6.14.0-27-generic #27~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 17:38:49 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I have installed the i386 architecture since following instructions in this thread: https://askubuntu.com/questions/454253/how-to-run-32-bit-app-in-ubuntu-64-b… The only probrem being that on the 'sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386' it gave an error that "E: Package 'libncurses5:i386' has no installation candidate" Would be nice if this could be fixed -- 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 50471] New: Kindle for PC 1.16.0 can't connect
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

https://bugs.winehq.org/show_bug.cgi?id=50471 Bug ID: 50471 Summary: Kindle for PC 1.16.0 can't connect Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ameniutaeba1978(a)gmail.com Distribution: --- Created attachment 69103 --> https://bugs.winehq.org/attachment.cgi?id=69103 Kindle error I installed Kindle for PC ver 1.16.0 from winetricks on my Manjaro Linux. When I start Kindle, Kindle says "Unable to connect. Please check your network setting and proxy configuration. Network settings can be found under Tools > Options > Network" I tested on wine-5.22 and wine-6.0-rc6 on Manajaro Linux but same result. I also tested wine-5.0 on Feren OS but the problem didn't occurred. So the problem is on wine 5.22 or later, or on Manjaro Linux. I've also posted the problem on Manjaro Forum but no good reply. https://forum.manjaro.org/t/is-there-anyone-who-use-amazon-kindle-for-pc-vi… I attach the STDOUT and STDERR. Thanks in advance. -- 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 22

[Bug 58739] New: Game (Geometry Dash) crashed in wine 10.0
by WineHQ Bugzilla 02 Oct '25

02 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=58739 Bug ID: 58739 Summary: Game (Geometry Dash) crashed in wine 10.0 Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chinatty0326(a)outlook.com Distribution: --- Created attachment 79365 --> http://bugs.winehq.org/attachment.cgi?id=79365 backtrace I met this bug the instant I run Geometry Dash in wine 10.0(precompiled) The backtrace was shown before the game window popped up. But in wine 6.0 and wine 10.14 it is OK to run. Anyone can help? -- 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