https://bugs.winehq.org/show_bug.cgi?id=57855
Bug ID: 57855
Summary: msiexec crashes while installing .net48 (regression)
Product: Wine
Version: 10.1
Hardware: x86-64
URL: https://download.visualstudio.microsoft.com/download/p
r/7afca223-55d2-470a-8edc-6a1739ae3252/abd170b4b0ec15a
d0222a809b761a036/ndp48-x86-x64-allos-enu.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: e7ac2e718feebd56064ed52aae0158861284af1c
Distribution: Debian
Unfortunately commit e7ac2e718feebd56064ed52aae0158861284af1c breaks installer
of .net48
Easiest way to reproduce is:
- wget
https://download.visualstudio.microsoft.com/download/pr/7afca223-55d2-470a-…
-7z x ndp48-x86-x64-allos-enu.exe
- wine netfx_Full_x64.msi
I couldn't get a backtrace, the crashdialog just hang.
e7ac2e718feebd56064ed52aae0158861284af1c is the first bad commit
commit e7ac2e718feebd56064ed52aae0158861284af1c
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri Feb 21 11:49:18 2025 +0100
ntdll: Support an arbitrary number of PE sections.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57850
dlls/ntdll/loader.c | 35 ++++++++++++++++++++++++-----------
dlls/ntdll/unix/virtual.c | 39 ++++++++++++++++++++++++++-------------
2 files changed, 50 insertions(+), 24 deletions(-)
--
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=57876
Bug ID: 57876
Summary: 10.2 Update wine-devel-amd64
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kieran1188(a)gmail.com
Distribution: ---
Created attachment 78097
--> https://bugs.winehq.org/attachment.cgi?id=78097
DPKG-debug-log
Just updated to 10.2 and coming up with errors trying to update
wine-devel-amd64
--
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=57879
Bug ID: 57879
Summary: 10.2~bookworm-2 update failed
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaronaz(a)protonmail.com
Distribution: ---
Created attachment 78101
--> https://bugs.winehq.org/attachment.cgi?id=78101
output
As title, latest update failed:
"trying to overwrite '/opt/wine-staging/bin/wine', which is also in package
wine-staging-i386:i386 10.2~b
ookworm-2"
My WINE install is still broken.
--
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=57861
Bug ID: 57861
Summary: All wine runs fail with "failed to start wineboot"
Product: Wine
Version: 10.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
After upgrade to Wine 10.2 in Debian testing (using packages from Wine debian
repo), any usage of that package wine (both regular and staging) fail with such
error:
wine winecfg
wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135
0024:err:environ:run_wineboot failed to start wineboot c0000135
wine: could not load kernel32.dll, status c0000135
If I build Wine myself (new wow64 build), it works fine.
--
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=57571
Bug ID: 57571
Summary: Zafehouse: Diaries garbage/black screen
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rencer(a)euromail.hu
Distribution: ---
I have this game installed on my computer with it's own wineprefix.
Never used that prefix for anything else, just to play this one game.
Originally I created that wineprefix and installed the game inside that back at
2014.
Also I tried to run the game with this wineprefix on the exact same computer as
back then.
It required lot of manual trickering to make it work. At that time nobody
managed to run the game with sound on Linux, but I figured out and posted a
how-to on the game's forum.
Later even the developers shared that how-to on the Steam page of the game. See
here:
https://steamcommunity.com/app/249360/discussions/0/846963711048254058/#c61…
Sadly that forum page doesn't exist anymore; possibly because the game is old
and no longer supported.
It doesn't really matter anyway, because it is no longer possible to make the
game install and setup a wineprefix that way.
Back then it was possible to install all the requirements manually because
wine/winetricks wasn't blocking us to install them. (such as full DirectX9,
.NET 3.5 SP1, etc.)
As years passed, once in a while I played the game, everything was fine.
But today, even that I try to run the game in that exact same wineprefix on the
exact same computer, it doesn't work anymore.
When I run the game it is starts loading; you can see as the game writes it on
the bottom right corner. When the loading process finishes the game supposed to
show the menu screen.
There is the problem.
I hear the music but the screen is just a mess. It somehow shows the content of
whatever is in the background of the game; like any other window or the desktop
itself.
But it is all garbage; it looks like whatever is in the background is turned
into a puzzle, shuffled and randomly put back on the screen.
The reason I kept the wine version 'unspecified' because I also tried to run
the game under different wine prefixes that uses different wine versions. Also
tried to make fresh wineprefix with the current latest wine in my Manjaro XFCE,
which is version 9.20. Creating a new one is impossible because of
winetricks/wine.
I have many winprefixes, so I find one or two that works.(One is version 9.20)
With these different working prefixes the result is always the same as with the
original old prefix; messed up screen.
--
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=57809
Bug ID: 57809
Summary: cmd: Incorrect substring expansion of last character
(e.g. `!MY_STR:~1!`)
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: Dominik-Home(a)gmx.de
Distribution: ---
Call the following script and observe the different output on Windows and Wine.
Substring expansion seems to work in general except the last character,
therefore MY_STR is set to 1 character to trigger the issue immediately.
Note that I've focused on the issue at hand and haven't tried out other
variations of substring-expansion.
issue_substring_expansion.bat
```cmd
@echo off
setlocal enableextensions enabledelayedexpansion
set MY_STR=R
echo "!MY_STR:~1!"
REM Prints "" on Windows
REM Prints "R" on Wine
```
This issue is blocking to get PlanAhead (part of Xilinx ISE 14.7) to work.
Multiple batch scripts set-up the environment before starting the GUI. Because
of this issue, they end up in an endless loop while iterating over all
characters in a variable similar to PATH.
My version:
```console
$ wine --version
wine-10.0 (Staging)
```
--
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=57804
Bug ID: 57804
Summary: cmd: CALL instruction freezes
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: Dominik-Home(a)gmx.de
Distribution: ---
Executing the 'CALL'-instruction on a *.bat file may causes freezes when using
e.g. '@echo off' in the called script.
```console
$ wine --version
wine-10.0 (Staging)
```
I inserted two minimal reproducers below that are used in the following
examples. Note that I marked the output of the scripts as comment with the REM
command as well as my own descriptions.
```cmd
C:\>C:\working.bat
REM C:\>echo Test
REM Test
REM Command returns immediately. No issue here
C:\>C:\issue.bat
REM Test
REM Command returns immediately. No issue here
C:\>CALL C:\working.bat
REM C:\>echo Test
REM Test
REM Command returns immediately. No issue here
C:\>CALL C:\issue.bat
REM Test
REM ISSUE: Command freezes here and never returns
```
working.bat:
```cmd
@echo on
echo Test
```
issue.bat:
```cmd
@echo off
echo Test
```
This issue was encountered while trying out PlanAhead, a tool included in the
Xilinx ISE design package. They use multiple batch scripts to configure the
environment before starting the GUI application. Because the batch files do not
work properly the GUI does not start at all. I.e. the application (PlanAhead)
is completely unusable.
--
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=18959
Summary: MetaTrader 4 installer hangs at the very end of file
extraction
Product: Wine
Version: 1.1.23
Platform: PC
URL: http://www.metatrader4.com/files/mt4setup.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
CC: julliard(a)winehq.org
With today's Git (wine-1.1.23-221-gafce86b), the MetaTrader installer hangs at
the very end of file extraction at "C:\Program Files\MetaTrader
4\mailbox\1190736044.english" with sufficient responsiveness to handle the
Cancel button being pressed, which merely hides the installer window until a
Ctrl+C interrupt is sent to the installer. The installer worked properly in
1.0.1, and the regression test revealed:
1c91d54503f9b2afa513dc4dd79bf19bc9bad51a is first bad commit
commit 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Feb 18 14:44:17 2009 +0100
msvcrt: Don't try to duplicate invalid handles. Don't reset std handles if
we didn't set them.
:040000 040000 2abf5f9a82de1d29b1fccadc658fc3a956388ac4
86464380dfe4aca4c5c11ea2a539a1fc5def03b8 M dlls
Reverting the commit in HEAD allows the installer to start.
--
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.