April 2024 - Wine-bugs - list.winehq.org

[Bug 52544] New: %__APPDIR__% and %__CD__% variables support
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=52544 Bug ID: 52544 Summary: %__APPDIR__% and %__CD__% variables support Product: Wine Version: 7.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fiendishx(a)gmail.com I'm not able to easily update to 7.2 because I'm on a mac and am largely dependent on https://github.com/Gcenx/homebrew-wine but I tested myself in Wine 6.0 and had a friend using Linux test in Wine 7.1, and it seems unlikely that this was fixed in the 7.2 update. It seems like the %__APPDIR__% and %__CD__% path variables don't work in Wine? See the "undocumented" section of https://ss64.com/nt/syntax-variables.html Example: wine cmd.exe echo %__APPDIR__% -> just prints "%__APPDIR__%" On my windows machine, "echo %__APPDIR__%" prints "C:\Windows\SysWOW64\" or "C:\Windows\system32\" depending on which version of cmd.exe (32/64 bit) was invoked. -- 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 50132] New: Command line: Incorrect behaviors in FOR () and IF () blocks
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=50132 Bug ID: 50132 Summary: Command line: Incorrect behaviors in FOR () and IF () blocks Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: Psycho-A(a)yandex.ru Distribution: --- The native CMD.exe contains many syntax and other errors related to the FOR and IF commands processing inside of ()-blocks. This is very importans for apps that require complex batch scripts on run. Let's begin. Case 1: ------- Different behavior when using brackets after "DO" :: Returns ")" error: for %%a in (*.txt) do if #==# ( echo File: "%%~a" ) :: Works normal: for %%a in (*.txt) do (if #==# ( echo File: "%%~a" )) :: Works normal: for %%a in (*.txt) do if #==# echo File: "%%~a" In Windows CMD all three results works the same (returns ECHO text). Case 2: ------- Reading empty lines of text file if EOL=# specified :: ECHO will return "" text here: for /f "usebackq eol=: tokens=1" %%a in ("File.txt") do ( echo "%%~a" ) Windows CMD skips empty lines anyway. Case 3: ------- Error behavior if an empty line with Space ot Tab is defined in body :: Will return ")" error: if #==# ( echo Some text ) :: Just will show ECHO text: if #==# ( echo Some text ) Case 4: ------- Not-expanding variables from parent cycle child one :: Will show "%~m" in child cycles: for %%f in (*.txt) do ( echo In parent cycle: "%%~f" for %%x in ("%%~f") do ( echo In child cycle: "%%~x" ) ) :: Will seek in "%~f" dir instead of "Folder1": for %%f in ("Folder1") do ( for /r "%%~f" %%x in (*.txt) do ( echo "%%~x" ) ) Windows CMD expands "%%f" in any child cycle's place. Case 5: ------- Error if no quotes in file/command condition :: Returns "DO is not an application" error: for /f %%a in (File.txt) do ( echo "%%~a" ) :: Reads strings of File.txt: for /f "usebackq" %%a in ("File.txt") do ( echo "%%~a" ) Windows CMD reads file in both cases ("usebackq" uses to use quotes around filename). This error appears only when target file not found. Case 6: ------- Using global ">" redirection after ()-body issue: :: Will show ECHO text and create empty Test.bug if #==# ( echo Text 1... echo Text 2... )> "Test.bug" :: Will write Test.bug with echo text (normal case) if #==# ( echo Text 1...> "Test.bug" echo Text 2...> "Test.bug" ) Windows CMD does the same as second in both cases. Case 7: ------- Incorrect IF() ELSE() processing if FOR() inside :: Returns "ELSE is not an application" error: if #==# ( echo IF condition. for %%m in (*.txt) do ( echo FOR cycle. ) ) else ( echo ELSE condition. ) :: Works normally: if #==# ( echo IF condition. ) else ( echo ELSE condition. ) Also ELSE works normal when IF condition is NOT equal. Case 8: ------- No processing file mask if it's quoted :: Returns txt files that found: for %%f in (*.txt) do ( echo "%%~f" ) :: Returns nothing for %%f in ("*.txt") do (echo "%%~f") for %%f in ("Dir\*.txt") do (echo "%%~f") The same is if FOR with /R key is used. For now that's all I found. Some of Wine 4.x bugs I knew seems to be fixed already. -- 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 6

[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 56389] New: 32bit Assassin's Creed game and assassin's creed revelations was unable to run under wow64
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56389 Bug ID: 56389 Summary: 32bit Assassin's Creed game and assassin's creed revelations 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: --- Created attachment 76138 --> https://bugs.winehq.org/attachment.cgi?id=76138 relay log With wow64 enable to run 32bit under 64bit wine Assassin's Creed is not able to show window, but it normally without wow64 support. -- 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 28

[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 55947] New: wine-8.10 to wine-8.21 opens COM1 and crashes
by WineHQ Bugzilla 29 Jun '24

29 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=55947 Bug ID: 55947 Summary: wine-8.10 to wine-8.21 opens COM1 and crashes Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zmtong1988(a)gmail.com Distribution: --- Run the serial assistant using wine-8.9 and open COM1. Everything is normal. Run the serial assistant using wine-8.10 to wine-8.21 and open COM1. The program crashes directly. Crash location: get_irq_info-->ioctl(fd, TIOCGICOUNT, &einfo)-->{ irq_info->rx = einfo.rx; ...} Crash log: Backtrace: =>0 0xf7b3cb25 get_irq_info+0x35(fd=0xc, irq_info=0280FEF8) [/home/work/Build_Wine/build_wine_make/make-wine-8.11/wine-8.11/dlls/ntdll/unix/serial.c:851] in ntdll.so (0x0280ff48) 1 0xf7b3cf13 wait_for_event+0xf3(arg=7BA00900) [/home/work/Build_Wine/build_wine_make/make-wine-8.11/wine-8.11/dlls/ntdll/unix/serial.c:966] in ntdll.so (0x0280ff48) 2 0x7b829fb0 in kernel32 (+0x29fb0) (0x0280ff48) 3 0x7bc5ac87 in ntdll (+0x5ac87) (0x0280ff5c) 4 0x7bc5b4dd in ntdll (+0x5b4dd) (0x0280ffec) 0xf7b3cb25 get_irq_info+0x35 [/home/work/Build_Wine/build_wine_make/make-wine-8.11/wine-8.11/dlls/ntdll/unix/serial.c:851] in ntdll.so: movdqa 0x20(%esp), %xmm0 851 irq_info->rx = einfo.rx; May I ask where the upgrade caused the program to crash. Thank you. -- 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 17

[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 56189] New: quartz:vmr7 - test_default_presenter_allocate() fails on Windows 7
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=56189 Bug ID: 56189 Summary: quartz:vmr7 - test_default_presenter_allocate() fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:vmr7 - test_default_presenter_allocate() fails on Windows 7: vmr7.c:3232: Test failed: Compression 0, depth 32: Got caps 0x870. vmr7.c:3266: Test failed: Compression 0, depth 32: Got caps 0x854. vmr7.c:3279: Test failed: Compression 0, depth 32: Got caps 0x850. vmr7.c:3284: Test failed: Compression 0, depth 32: Got hr 0x887600ff. See https://test.winehq.org/data/patterns.html#quartz:vmr7 These failures first happened on 2023-12-07 which is the day they were introduced in the commit below: commit 9be491e80fc97058402ee74140d7ce90a45a956b Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Dec 7 13:30:43 2023 -0600 quartz: Implement sample allocation in the VMR7 presenter. -- 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 54935] New: Rewrite (VN): black screen videos with WMP backend and gstreamer
by WineHQ Bugzilla 28 Jun '24

28 Jun '24

https://bugs.winehq.org/show_bug.cgi?id=54935 Bug ID: 54935 Summary: Rewrite (VN): black screen videos with WMP backend and gstreamer Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: timoninvlad(a)yandex.ru Distribution: --- Created attachment 74457 --> https://bugs.winehq.org/attachment.cgi?id=74457 Wine logs with WINEDEBUG=quartz Game has 2 options for video playback, MCI and Windows Media Player (WMP). When using gstreamer, MCI backend works fine, but WMP floods the terminal with `err:quartz:send_buffer Failed to get a sample, hr 0x80040211.` while showing a black screen, then audio starts playing. Curiously, if you install `lavfilters` from `winetricks` so that gstreamer isn't used, then WMP plays the video back properly. The black screen started to show up since ed2c300d02acefa2aedd4333ff4a982137c1d4fe (after 7.6). Wine logs with `WINEDEBUG=quartz` are attached in the archive. Before the regression (6f1b3cf9), with first bad commit (ed2c300d) and current master (8.8, 5662d85e). Trial version of the game can be downloaded from Download section here: https://key.visualarts.gr.jp/rewrite/index2.html Game can be extracted directly from `RewriteTE_Ver200/StartData/GameData` in the archive. To set it up you'll need: - `LANG=ja_JP.UTF8` and `TZ=Japan` environment variables, game refuses to start otherwise - `winetricks wmp9` for WMP backend to work, game crashes otherwise when it's used, installer might say "It was not possible to complete Setup" which is fine - MPEG-1 codec from `lib32-gst-plugins-bad` for the opening video When starting up the game, hold Ctrl to get to the main menu faster. Video backend can be configured in Config - ムービー設定 (https://user-images.githubusercontent.com/20689137/126137253-0fe05ddc-2187-…) should be WMP by default. To exit Config, right click or click on 戻る in bottom-right corner. Click Start on the main menu, then hold Ctrl to skip until the opening video. -- 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 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