https://bugs.winehq.org/show_bug.cgi?id=56381
Bug ID: 56381
Summary: "type" does not support binary files
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: dan(a)coneharvesters.com
Distribution: ---
"type" truncates binary files when redirecting the output to stdout. For
example:
c:\>type c:\windows\winhelp.exe >foo
c:\>dir c:\windows\winhelp.exe foo
Volume in drive c has no label.
Volume Serial Number is 0000-0000
Directory of c:\windows
28/02/2022 5:32 PM 257 winhelp.exe
1 file 257 bytes
0 directories
Directory of c:
29/02/2024 1:21 PM 2 foo
1 file 2 bytes
0 directories 19,394,506,752 bytes free
The file is truncated after the second byte (byte 3 is NUL). Windows 10 and
Windows XP copy the entire file in this case. However, Windows 95 truncates the
file.
This is causing real-world compatibility issues, as the z88dk compiler suite
inexplicably uses "type" to copy binary files like this on Windows.
--
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=16214
Summary: Copy command does not work as expected
Product: Wine
Version: 1.0.1
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
>From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/272921
In Windows, the COPY command run in a command prompt allows users to
concatenate files by using a plus ("+") operator, for example:
copy file1+file2 outfile
In wine's cmd.exe, it seems to read file1+file2 as a single path and therefore
outputs a "Path Not Found". Also, it does not recognize the "con" keyword used
to represent stdout/stdin. Therefore another method of concatenating files:
copy file1 outfile
copy file2 con >> outfile
does not work either.
My Ubuntu version is 8.04, AMD64 architecture, though I have seen the same
issue on the x86 version as well.
--
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=58657
Bug ID: 58657
Summary: Reference to swapchain not removed when swapchain is
destroyed
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gingyu02(a)gmail.com
Distribution: ---
While using OpenGL renderer,when a swapchain is removed,some references to it
(such as surfaces,contexts) are not removed,resulting in a null pointer error
when calling related fuctions.
--
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=58656
Bug ID: 58656
Summary: Fatal error running Enterprise Architect
Product: Wine
Version: 10.14
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: modstrcil(a)herrera.unt.edu.ar
Distribution: ---
Created attachment 79235
--> http://bugs.winehq.org/attachment.cgi?id=79235
Output error file
I run Sparx System Enterprise Architect 6.5.801 and when I open a Diagram, It
crashes with the messagge below:
Unhandled exception: page fault on write access to 0x829f4000 in wow64 32-bit
code (0x05ec18a5).
I did not have problems until the last S.O update.
There is more information in the attached file.
Thanks.
--
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=58604
Bug ID: 58604
Summary: Unable to handle Ctrl+C signal
correctly,02c0:fixme:console:default_ctrl_handler
Terminating process e0 on event 0
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 1514704742(a)qq.com
Distribution: ---
Unable to handle Ctrl+C signal correctly
--
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=58652
Bug ID: 58652
Summary: UWAMP httpd.exe serious error
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wsgo0sookosssc8ko4cowkcgc48k4wws(a)ai.notifier.in
Distribution: ---
Created attachment 79227
--> http://bugs.winehq.org/attachment.cgi?id=79227
httpd
It works fine on Windows - until I move them to Linux & tried with Wine.
There were 2 issues:
1. "Launcher Server" GUI no longer collect CLI windows (you know what I mean if
you compare the behavior on Windows)
2. And this error pops up.
Steps to reproduce:
1. Download & Extract "RELEASE SRV4.rar" from
https://drive.google.com/drive/folders/1r4cXG1NfE-KEZYIN9ns3_V7mGzPO7EaK
2. run "wine explorer", navigate to server directory (where RAR files
extracted)
3. start "Pangya Server Launcher.exe"
4. start "@WebServer\UwAmp.exe", it should start
5. press "START" on Server Launcher
Result:
httpd.exe encountered srious problem.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58619
Bug ID: 58619
Summary: Steam fails to launch
Product: Wine
Version: 10.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: 5b7b76432dffa453e75c6336d76fdb856ab8d0c7
Distribution: ---
wineserver: ../wine/server/request.c:159: set_reply_data_size: Assertion `size
<= get_reply_max_size()' failed.
--
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=58655
Bug ID: 58655
Summary: Wine only works on seat0 of multi seat setup in Xorg
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: jamaggs(a)gmail.com
Distribution: ---
Created attachment 79234
--> http://bugs.winehq.org/attachment.cgi?id=79234
Output of WINEDEBUG=+x11drv,+x11settings wine notepad.exe &> wine.log before
and after registory import of "UseXRandR"="N"
I have a multi-seat setup.
Wine works fine on seat0 but not on seat1. On seat1 whatever program I try to
open it just kind of hands and never shows any window.
This seemed to start with wine version 6 so until recently I just stuck with 5
but I'm now trying to sort this.
With the help of AI, I discovered that this is probably an issue with the use
of randr. Specifically, if I import this into my registry then I can get Wine
to work with seat1 too, though this does lead to some other issues (I don't
think Wine can then change the resolution so I have to do it manually before
starting any games).
REGEDIT4
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"UseXRandR"="N"
I am attaching the output of this before and after adding the above line:
WINEDEBUG=+x11drv,+x11settings wine notepad.exe &> wine.log
Many thanks for your 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.
http://bugs.winehq.org/show_bug.cgi?id=58654
Bug ID: 58654
Summary: Crash when running Kontakt 8 standalone binary
Product: Wine
Version: 10.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 31core(a)tutanota.com
Distribution: ---
Created attachment 79232
--> http://bugs.winehq.org/attachment.cgi?id=79232
Console stdout and stderr output
Crash when running Kontakt 8 standalone binary using wine 10.14
--
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.