March 2022 - Wine-Bugs - list.winehq.org

[Bug 52755] New: Visual Novel "A Clockwork Ley-Line" hangs with blackscreen
by WineHQ Bugzilla June 30, 2024

June 30, 2024

https://bugs.winehq.org/show_bug.cgi?id=52755 Bug ID: 52755 Summary: Visual Novel "A Clockwork Ley-Line" hangs with blackscreen Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- For the Launcher issue see bug 44397. You need to run LeyLine.exe directly. Using the standalone (non-steam) version. The game starts, shows its splashscreen, but then hangs indefinitely with a blackscreen instead of going into the main menu. Bisected to commit f15c23df4a281a93087b5c0d2ca421463c7b9e4a Author: Jactry Zeng <jzeng(a)codeweavers.com> Date: Mon Apr 6 11:54:07 2020 -0500 qasf: Implement IFileSourceFilter_Load() for WM ASF reader. Signed-off-by: Jactry Zeng <jzeng(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Not sure what component that is though... Would you mind talking a look, please? -- 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 44397] New: Visual Novel "A Clockwork Ley-Line" - Running launcher crashes
by wine-bugs＠winehq.org June 30, 2024

June 30, 2024

https://bugs.winehq.org/show_bug.cgi?id=44397 Bug ID: 44397 Summary: Visual Novel "A Clockwork Ley-Line" - Running launcher crashes Product: Wine Version: 3.0-rc6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 60320 --> https://bugs.winehq.org/attachment.cgi?id=60320 Error log and message Since bug 44379 is fixed, the launcher now starts the locale-emulator, that then seems to crash. It shows a messagebox (message in attachment) and doesn't start the game. Note that the launcher is a 64bit .NET binary, and I didn't get native .NET to work properly in a 64bit prefix yet. As workaround you still can start the game directly (run LeyLine.exe). -- 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 8

[Bug 38289] New: cmd replacement is unable to display a bat file script correctly.
by wine-bugs＠winehq.org June 30, 2024

June 30, 2024

https://bugs.winehq.org/show_bug.cgi?id=38289 Bug ID: 38289 Summary: cmd replacement is unable to display a bat file script correctly. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: njls.yoshi2(a)gmail.com Distribution: --- Created attachment 51122 --> https://bugs.winehq.org/attachment.cgi?id=51122 Example batch The amended Wine cmd.exe (version 6.1.7601 [1.6.2]) is unable to display a batch script to emulate written text to a command line (script attached). The script runs true in sequence if perused, however, the line where the text should be displayed, yields the characters, "a~0,1", which is a defined argument (expressed in attached script), but not the correct output. -- 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 15

[Bug 32449] New: QGIS err:module:import
by wine-bugs＠winehq.org June 29, 2024

June 29, 2024

http://bugs.winehq.org/show_bug.cgi?id=32449 Bug #: 32449 Summary: QGIS err:module:import Product: Wine Version: 1.5.19 Platform: x86 URL: http://hub.qgis.org/projects/quantum-gis/wiki/Download OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: guy.roussin(a)teledetection.fr Classification: Unclassified Created attachment 42810 --> http://bugs.winehq.org/attachment.cgi?id=42810 Error log when launching qgis 1.8.0-1 on wine 1.5.19 Hi, QuantumGIS is an open source software which run very fine on linux. Today, i try the windows version on a quantal 32 bits chroot on my debian sid amd64. http://qgis.org/downloads/QGIS-OSGeo4W-1.8.0-1-Setup.exe I get this error when launching qgis : (see attachment) I get the same error with PlayOnLinux ... Thank you, Guy -- 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.

2 15

[Bug 52544] New: %__APPDIR__% and %__CD__% variables support
by WineHQ Bugzilla June 29, 2024

June 29, 2024

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 June 29, 2024

June 29, 2024

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 June 29, 2024

June 29, 2024

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 June 29, 2024

June 29, 2024

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 June 28, 2024

June 28, 2024

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 June 28, 2024

June 28, 2024

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