November 2022 - Wine-bugs - list.winehq.org

[Bug 49509] New: Cant send WM_CHAR to WineConsoleClass
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=49509 Bug ID: 49509 Summary: Cant send WM_CHAR to WineConsoleClass Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: adrianekaleksander(a)gmail.com Distribution: --- When I send messages via PostMessage() or SendMessage() to WineConsoleClass, they are not displayed. Video how it should look: https://www.youtube.com/watch?v=SByRm_ArR1c https://www.youtube.com/watch?v=SHJ8OOqR2sU And how it looks on Ubuntu : https://www.youtube.com/watch?v=461huP5MBAw But in other programs works ok: https://www.youtube.com/watch?v=wBil8KubIXo https://www.youtube.com/watch?v=R_jE8BSvDcI Program which I used: https://tools.stefankueng.com/SendMessage.html -- 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

[Bug 52484] New: ShaderGlass crashes on startup
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=52484 Bug ID: 52484 Summary: ShaderGlass crashes on startup Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffz(a)jeffz.name Distribution: --- $ wine ShaderGlass.exe 007c:fixme:imm:ImeSetActiveContext (0x3e020, 0): stub 007c:fixme:imm:ImmReleaseContext (0000000000010020, 000000000003E020): stub 002c:fixme:imm:ImeSetActiveContext (0x412a0, 1): stub 002c:fixme:imm:ImmReleaseContext (000000000001004A, 00000000000412A0): stub wine: configuration in L"/home/jeffz/.wine-shaderglass" has been updated. 0130:fixme:combase:RoGetActivationFactory (L"Windows.Foundation.Metadata.ApiInformation", {997439fe-f681-4a11-b416-c13a47e8ba36}, 000000000011F6F0): semi-stub 0130:err:combase:RoGetActivationFactory Failed to find library for L"Windows.Foundation.Metadata.ApiInformation" 0130:fixme:combase:RoOriginateLanguageException (80040154 L"" 0000000000000000) stub 0130:fixme:imm:ImeSetActiveContext (0x165ac0, 1): stub 0130:fixme:imm:ImmReleaseContext (0000000000050056, 0000000000165AC0): stub wine: Unhandled exception 0x80000003 in thread 130 at address 00000001700574C4 (thread 0130), starting debugger... 0138:fixme:imm:ImeSetActiveContext (0x34f00, 1): stub 0138:fixme:imm:ImmReleaseContext (0000000000060072, 0000000000034F00): stub RtlDefaultNpAcl () at Z:\usr\src\packages\BUILD\dlls\ntdll\sec.c:1731 0x00000001700574c4 ntdll+0x574c4 [Z:\usr\src\packages\BUILD\dlls\ntdll\sec.c:1731]: int $3 Unable to access file 'Z:\usr\src\packages\BUILD\dlls\ntdll\sec.c' System information: Wine build: wine-7.1 Platform: x86_64 Version: Windows 7 Host system: Linux Host version: 5.13.0-27-generic -- 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 7

[Bug 47071] New: Nest or mixed "FOR" and "IF" command sometimes get different result in Wine and Windows.
by wine-bugs＠winehq.org 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=47071 Bug ID: 47071 Summary: Nest or mixed "FOR" and "IF" command sometimes get different result in Wine and Windows. Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: mzidbh(a)hotmail.com Distribution: --- Created attachment 64257 --> https://bugs.winehq.org/attachment.cgi?id=64257 batch files and snapshots of execution result The Wine's command interpreter seems to ... 1. could not pair "IF" and "ELSE" correctly. ( Case １４ ) 2. would ignore scripts after inner "ELSE". ( Case ２３ ) Case １ ======================================== @ECHO OFF ECHO FOR in IF 01 : IF 1 EQU 1 ( FOR %%A IN (1,1) DO ( ECHO A=%%A ) ) ELSE ( ECHO This line should NOT be executed. ) ECHO This line should be executed. EXIT /B ---------------------------------------- Result in WINE 3.0 ---------------------------------------- FOR in IF 01 : A=1 A=1 Can't recognize 'ELSE ' as an internal or external command, or batch script. This line should NOT be executed. This line should be executed. ---------------------------------------- Result in Windows 7 ---------------------------------------- FOR in IF 01 : A=1 A=1 This line should be executed. ======================================== Case ２ ======================================== @ECHO OFF ECHO IF in FOR 01 : FOR %%A IN (1,1) DO ( IF 1 EQU 1 ( ECHO This line should be executed. [No.1] ) ELSE ( ECHO This line should NOT be executed. ) ECHO This line should be executed. [No.2] ) EXIT /B ---------------------------------------- Result in WINE 3.0 ---------------------------------------- IF in FOR 01 : This line should be executed. [No.1] This line should be executed. [No.1] ---------------------------------------- Result in Windows 7 ---------------------------------------- IF in FOR 01 : This line should be executed. [No.1] This line should be executed. [No.2] This line should be executed. [No.1] This line should be executed. [No.2] ======================================== Case ３ ======================================== @ECHO OFF ECHO IF in IF 01 : IF 1 EQU 1 ( IF 1 EQU 1 ( ECHO This line should be executed. [No.1] ) ELSE ( ECHO This line should NOT be executed. [No.1] ) ECHO This line should be executed. [No.2] ) ELSE ( ECHO This line should NOT be executed. [No.2] ) EXIT /B ---------------------------------------- Result in WINE 3.0 ---------------------------------------- IF in IF 01 : This line should be executed. [No.1] ---------------------------------------- Result in Windows 7 ---------------------------------------- IF in IF 01 : This line should be executed. [No.1] This line should be executed. [No.2] ======================================== Case ４ ======================================== @ECHO OFF ECHO IF in IF 04 : IF 4 EQU 4 ( IF 4 EQU 5 CALL :Label1 ECHO This line should be executed. [No.1] ) ELSE ( ECHO This line should NOT be executed. [No.2] ) GOTO :Label2 :Label1 ECHO This line should NOT be executed. [No.1] GOTO :EOF :Label2 EXIT /B ---------------------------------------- Result in WINE 3.0 ---------------------------------------- IF in IF 04 : This line should NOT be executed. [No.2] ---------------------------------------- Result in Windows 7 ---------------------------------------- IF in IF 04 : This line should be executed. [No.1] ======================================== -- 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 5

[Bug 49993] New: CUERipper 2.1.6 and 2.1.7 do not run with wine-mono
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=49993 Bug ID: 49993 Summary: CUERipper 2.1.6 and 2.1.7 do not run with wine-mono Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: toadking(a)toadking.com Distribution: --- When trying to run CUERipper 2.1.7, wine fails with this error: Unhandled Exception: System.TypeLoadException: Could not resolve type with token 01000085 from typeref (expected class 'System.Deployment.Application.DeploymentException' in assembly 'System.Deployment, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') at CUERipper.Program.Main () [0x00035] in <5c4f365916584c81bcdf752cec08f1e3>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not resolve type with token 01000085 from typeref (expected class 'System.Deployment.Application.DeploymentException' in assembly 'System.Deployment, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') Version 2.1.6 fails with a similar error, only for dotnet 2.0 instead of 4.0 Unhandled Exception: System.TypeLoadException: Could not resolve type with token 01000116 from typeref (expected class 'System.Deployment.Application.DeploymentException' in assembly 'System.Deployment, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') at CUERipper.Program.Main () [0x0003a] in <6963147f6a904857af87d170dcff6c6e>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not resolve type with token 01000116 from typeref (expected class 'System.Deployment.Application.DeploymentException' in assembly 'System.Deployment, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') Installing dotnet40 or dotnet20 for their respective versions allows them to run. -- 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 19

[Bug 47798] New: Incorrect substring result using enableDelayedExpansion
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=47798 Bug ID: 47798 Summary: Incorrect substring result using enableDelayedExpansion Product: Wine Version: 4.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: lois.diqual(a)gmail.com Distribution: --- Created attachment 65289 --> https://bugs.winehq.org/attachment.cgi?id=65289 Test file Batch variable substring yields incorrect results when using enableDelayedExpansion. setlocal enableDelayedExpansion set foo=bar echo "!foo:~0,2!" endlocal Expected output: "ba" Actual output: - Wine cmd: "~0,2" - Windows cmd: "ba" -- 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 43337] New: Conditional command with parentheses not working.
by wine-bugs＠winehq.org 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=43337 Bug ID: 43337 Summary: Conditional command with parentheses not working. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: distjubo(a)gmail.com Distribution: --- If a conditional command contains parentheses, it fails to execute properly. Example 1: Command: echo C:\Program Files (x86)\ Output: C:\Program Files (x86)\ Example 2: Command: if ""=="" echo C:\Program Files (x86)\ Example 2 fails to execute. On Windows, the output of Example 1 and Example 2 are identical, but wine complains about not having found the command "x86". -- 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 7

[Bug 52344] New: Can't substitute variables as a command
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=52344 Bug ID: 52344 Summary: Can't substitute variables as a command Product: Wine Version: 6.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: EmilySeville7cf(a)gmail.com Distribution: --- Created attachment 71511 --> https://bugs.winehq.org/attachment.cgi?id=71511 Bug screenshot In Windows environment (10.0.19043.1415) everything 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.

1 7

[Bug 53190] New: cmd.exe incorrectly parses a line with nested if commands
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=53190 Bug ID: 53190 Summary: cmd.exe incorrectly parses a line with nested if commands Product: Wine Version: 7.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 72628 --> https://bugs.winehq.org/attachment.cgi?id=72628 example_batch_file.cmd The attached batch file shows on windows the lines A B. But wine gives this output: ---- $ LANG=C wine64 example_batch_file.cmd C:\>if 0 == 0 echo A& (if 0 == 0 (echo B) else (echo C)) A B C Can't recognize ')' as an internal or external command, or batch script. ---- This isse was found during investigation to bug #53155, which leads to an endless loop in this batch file: https://github.com/msys2/MSYS2-packages/blob/fb3dffb7c4583f9b172fb67ba6df58… -- 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 5

[Bug 50723] New: Can't recognize ... as an internal or external command, or batch script
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=50723 Bug ID: 50723 Summary: Can't recognize ... as an internal or external command, or batch script Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- Created attachment 69476 --> https://bugs.winehq.org/attachment.cgi?id=69476 Linux shell As I had trouble starting the icedtea-web in the wine git version, I asked for help from the icedtea-web staff and some guy sent me a command to perform to determine what it was all about. The original command is: "d:\jdk-10-oracle\bin\java -splash: d:\icedtea-web-image-1.8.4.win\share/icedtea-web\javaws_splash.png @d:\icedtea-web-image-1.8.4.win\bin\itw-modularjdk.args --patch-module=jdk.jsobject=d:\icedtea-web-image-1.8.4.win\share/icedtea-web\jsobject.jar -Xbootclasspath /a:d:\icedtea-web-image-1.8.4.win\share/icedtea-web\javaws.jar;d:\icedtea-web-image-1.8.4.win\share/icedtea-web\plugin.jar;d:\icedtea-web-image-1.8.4.win\share /icedtea-web\jsobject.jar;d:\icedtea-web-image-1.8.4.win\win-deps-runtime\js.jar;d:\icedtea-web-image-1.8.4.win\win-deps-runtime\tagsoup.jar;d:\icedtea-web-image-1.8.4.win\win-deps-runtime\mslinks.jar;d:\jdk-10-oracle\lib\ext\nashorn.jar; -classpath d:\jdk-10-oracle\lib\rt.jar;d:\jdk-10-oracle\lib\ext\jfxrt.jar; -Dicedtea-web.bin.name=itweb-settings.exe -Dicedtea-web.bin.location=d:\icedtea-web-image-1.8.4.win\bin\itweb-settings.exe net.sourceforge.jnlp.controlpanel.CommandLine -verbose" Based on it, I created a linux script to determine if that command works or not. However, although in my opinion the script command is correct, wine reports that it is incorrect. Vladimir Koković, DP senior(70), Serbia, Belgrade, 25.February 2021 -- 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 19

[Bug 44063] New: Parentheses cause cmd.exe failing to recognize '2>&1'
by wine-bugs＠winehq.org 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=44063 Bug ID: 44063 Summary: Parentheses cause cmd.exe failing to recognize '2>&1' Product: Wine Version: 2.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhasse(a)gmail.com Distribution: --- On Windows cmd.exe /C "(echo foo) 2>&1" works (only outputs "foo"), while on wine it results in: foo Can't recognize '2' as an internal or external command, or batch script. and a non-zero exit code. Removing the parenthesis would work: wine cmd.exe /C "echo foo 2>&1" I need them though, since I want to do stuff like this: wine cmd.exe /C "(echo foo && echo bar) 2>&1" Maybe related: https://bugs.winehq.org/show_bug.cgi?id=43337 -- 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 3