http://bugs.winehq.org/show_bug.cgi?id=58709
Bug ID: 58709
Summary: upgrade to 10.15 results in garbled fullscreen in
Limelight Lemonade Jam
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 79308
--> http://bugs.winehq.org/attachment.cgi?id=79308
terminal output for 10.12–10.15
[Ubuntu 22.04, WINE packages from winehq.org repo]
I've been playing the trial version of Limelight Lemonade Jam, which is
available for free from
https://sample9.dmm.co.jp/digital/pcgame/yuzu_0012/yuzu_0012t.zip, using WINE
10.12. No issues.
Warning! The full game is NSFW, it's possible the trial has NSFW content as
well; but if so, it doesn't come up for quite a while.
WINE got upgraded to 10.15 just now, and the game doesn't launch correctly any
more, the display is messed up, see screenshot.
So I tested 10.12–10.15, each run with a fresh prefix, and it's reproducible:
- 10.12: OK
- 10.13: OK
- 10.14: OK
- 10.15: BROKEN
Full disclosure, I've set the game to fullscreen and enabled the suspend/resume
function, i.e. it'll bypass the main menu on launch and resume the game
directly. Judging by the sound, the game loads fine even on 10.15, AFAICT it
still reacts to keyboard input correctly, it's just the display that's messed
up.
It's likely that this affects other games using the KiriKiri engine as well.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58665
Bug ID: 58665
Summary: cmd incorrectly wraps text containing ANSI escape
sequences
Product: Wine
Version: 10.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: forestix(a)gaga.casa
Distribution: ---
Created attachment 79250
--> http://bugs.winehq.org/attachment.cgi?id=79250
reproducer: should print 3 lines; wine prints 4 lines
Wine's cmd.exe prematurely inserts line breaks when a program's output contains
non-printable ANSI escape sequences, such as those used to change colors.
It looks as though Wine is counting not only the printable characters in the
program's output, but also the non-printable ones, and using the total to
decide where to insert a line break. Text that fits entirely on one line in a
real Windows console is sometimes broken midway through the line, or followed
by a blank line that should not be there, when run in an xterm using Wine.
I am attaching a batch file that reproduces the problem. It should print 3
lines. The second line is identical to the others with the addition of some
non-printable escape sequences. These characters should either occupy no width
in the terminal (making the line length match the others) or be rendered as
visible placeholder characters (as older Windows versions do). To see Wine
handling it incorrectly, run it in an 80-column xterm or a similar terminal.
Ideally, the output should look like this, with the head of line 2 in red:
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
In wine, the output looks like this:
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_12
3456789
79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789
Bug 49780 is related, but IMHO does not excuse this behavior. Regardless of
whether virtual terminal sequences are supported, Wine should either print a
character or not count it toward the length of a line when deciding where to
wrap it.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58411
Bug ID: 58411
Summary: Audio tab in winecfg hasn't worked since Wine 10.6
Product: Wine
Version: 10.6
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mmdevapi
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 78821
--> http://bugs.winehq.org/attachment.cgi?id=78821
Screenshot
Since Wine 10.6, the Audio tab in winecfg says "Selected driver: (None)" at the
top, the only option in all of the drop-downs is "(System default)", and the
"Speaker configuration" section is empty. The "Test Sound" button still works
though. `git bisect` says:
a6aa0108f365b1465bc594a053af84116a28ce34 is the first bad commit
commit a6aa0108f365b1465bc594a053af84116a28ce34
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue Apr 15 12:57:37 2025 +0200
mmdevapi: Get rid of the Wine info device.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58527
Bug ID: 58527
Summary: autocad electrical 2026 error in wxwidgets
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: grandrodri3(a)gmail.com
Distribution: ---
Created attachment 79001
--> http://bugs.winehq.org/attachment.cgi?id=79001
autocad architecture error in wxwidgets
Hey, hello guys, how are you?
Well, I'm adding a new application to the Wine database. This is an AutoCAD
application developed by Autodesk, specifically for electrical plans
(specifically, electrical panel installations in homes). So, I'm reporting the
error the installer gives me to see if anything can be done. The error I'm
getting, by the way, was loaded with the following DLLs installed:
vcrun2012 vcrun2022 dotnetcore3 dotnet8
I get an error in the DLLs for the Windows implementation of wxwidgets. I've
tried installing wxwidgets from their official website, but nothing. AutoCAD
doesn't go beyond the terminal (that is, the installer doesn't display).
official download website:
https://www.autodesk.com/es/products/autocad/included-toolsets/autocad-elec…
I'll pass what I get in the terminal.
Could you please check it?
Best regards.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44252
Bug ID: 44252
Summary: Secret World Legends - ClientPatcher.exe crashes
Product: Wine
Version: 3.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Hello everyone,
I tried running the update mechanism for "Secret World Legends" today and got a
crash. It is not one of these "unrecoverable errors" with Windows but a Funcom
bug so you might file this as NOTOURBUG.
Could you please take a look at my console output I gathered when you are out
of code freeze?
Have a 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.
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.
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.
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.
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.
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.