wine-bugs December 2019

wine-bugs@winehq.org

1 participants
7437 discussions

[Bug 37789] New: cmd.exe /c cannot handle "(" and ")" characters in a full script path name
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=37789 Bug ID: 37789 Summary: cmd.exe /c cannot handle "(" and ")" characters in a full script path name Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Created attachment 50334 --> https://bugs.winehq.org/attachment.cgi?id=50334 Various cmd executions discussed in the report using WINEDEBUG='+cmd'. Far Cry 4 (which requires at least a 64-bit Windows 7 prefix) fails to call a bash script on launch: Can't recognise 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat /silent' as an internal or external command, or batch script. Sure enough, calling it manually (even without the /silent argument) results in the same error: $ wine cmd.exe /c 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' Can't recognise 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' as an internal or external command, or batch script. Suspicious of the ( and ) characters in the URL, I tried copying the GEFirewall.bat to the path 'C:\Program Files\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\' (which doesn't normally exist but I manually created it). $ wine cmd.exe /c 'C:\Program Files\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' fixme:netsh:wmain stub: L"netsh" L"firewall" L"add" L"allowedprogram" L"C:\\Program Files\\Ubisoft\\Ubisoft Game Launcher\\games\\Far Cry 4\\Support\\Software\\..\\..\\bin\\FarCry4.exe" L"FarCry4" L"ENABLE" fixme:netsh:wmain stub: L"netsh" L"firewall" L"add" L"allowedprogram" L"C:\\Program Files\\Ubisoft\\Ubisoft Game Launcher\\games\\Far Cry 4\\Support\\Software\\..\\..\\bin\\IGE_WPF64.exe" L"FarCry4-IGE" L"ENABLE" The script ran perfectly. One more test to confirm my sanity: $ wine explorer.exe 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software' This opened the directory in explorer fine. Only cmd.exe /c ... seems to show this issue. -- 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 35561] New: Some MSYS2 commands generate a stackdump
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=35561 Bug ID: 35561 Summary: Some MSYS2 commands generate a stackdump Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irwin(a)beluga.phys.uvic.ca Classification: Unclassified Created attachment 47484 --> http://bugs.winehq.org/attachment.cgi?id=47484 strace log of execution of mintty The general problem is I cannot start MSYS2 (the successor to MSYS) using its msys2_shell.bat startup batch file (see directions at http://sourceforge.net/p/msys2/wiki/MSYS2 installation/ concerning how to start MSYS2). That batch file (which executes a number of different MSYS2 commands) exits almost immediately with a stack dump. Alexey Pavlov, the developer of MSYS2, suggested I narrow down the problem by attempting to execute the MSYS2 version of mintty.exe directly, and if that did not work (which was the case) then run that app via the MSYS2 strace.exe facility to help figure out what the exact problem is. MSYS2 strace.exe did appear to work and I attach its log (and also the associated stackdump for mintty.exe). Here are some additional details in case there are any difficulties replicating this issue. I have used 3 different versions of 32-bit Wine which I built myself on my Debian Wheezy system. Those are Unpatched Wine-1.6.1, patched Wine-1.6.1, and patched Wine-1.7.12. The patch used was "Hackish patch to fix APC problem" taken from http://bugs.winehq.org/show_bug.cgi?id=24018. The reason why that extremely small patch is relevant is MSYS2 is essentially a simplified modern Cygwin (as opposed to MSYS which is essentially a simplified ancient version of Cygwin). Because the patched versions give improved results (see below), apparently the modern bits of Cygwin that are still part of MSYS2 trigger at least the APC Wine bug for modern Cygwin that did not occur for older Cygwin versions. The version of MSYS2 I am using is msys2-base-i686-20140205.tar.xz. Unpacking that created a top-level directory name of msys32 which I have changed to MSYS2-20140205 to help keep better track of which version of MSYS2 I am trying. I ran the MSYS2 version of strace with the patched versions of Wine as follows: wine@raven> wineserver -k wine@raven> wineserver -p wine@raven> wineconsole --backend=curses cmd Microsoft Windows 5.1.2600 (1.7.12) Z:\home\wine\newstart>PATH=Z:\home\wine\newstart\MSYS2-20140205\bin;%PATH% Z:\home\wine\newstart>MSYS2-20140205\bin\strace.exe MSYS2-0140205\bin\mintty.exe > strace.log 1069046 [main] mintty 44 cygwin_exception::open_stackdumpfile: Dumping stack trace to mintty.exe.stackdump The mintty terminal momentarily appeared before the stackdump occurred. After that stack dump strace did not return (i.e., everything was hung), and the last line in strace.log at that point was 616 1255194 [main] mintty 44 pinfo::exit: Calling ExitProcess n 0x8B, exitcode 0x8B00 I exited the combination of mintty, strace, cmd, and wineconsole the brute-force way by typing "wineserver -k" in a different Linux xterm which added nothing else to strace.log. The strace and stackdump results for patched wine-1.6.1 and patched wine-1.7.12 were virtually identical (except for numerical data like PID numbers). I have attached the wine-1.7.12 versions. When initially investigating this issue I was using unpatched wine-1.6.1. The result of everything I tried was Wine error boxes concerning dll problems. Those error boxes reminded me very much of my troubles in trying to run modern Cygwin from Wine so I applied the APC-related patch, and sure enough, that got rid of the error boxes, and I could get a lot further before I ran into a different problem which is what I have described above. -- 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 21

[Bug 47890] New: Conqueror's Blade - Launcher won't launch the game
by WineHQ Bugzilla 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47890 Bug ID: 47890 Summary: Conqueror's Blade - Launcher won't launch the game Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: werifGX(a)gmail.com Distribution: --- Created attachment 65381 --> https://bugs.winehq.org/attachment.cgi?id=65381 aptli (list of installed packages) Game Conqueror's Blade (https://store.steampowered.com/app/905370 not present in winehq database 10/05/2019) using wine-4.17 and game installed using https://github.com/Winetricks/winetricks/pull/1360 If the "Play" button (https://imgur.com/a/IRdfcdz) is pressed wine with WINEDEBUG="fixme-all" outputs: wine: Call from 0x7104ea8d to unimplemented function ntoskrnl.exe.MmGetPhysicalAddress, aborting wine: Unimplemented function ntoskrnl.exe.MmGetPhysicalAddress called at address 000000007104EA8D (thread 0222), starting debugger... Assuming `ntoskrnl` related issue == system info == kreyren@dreamon --------------- OS: Debian GNU/Linux bullseye/sid x86_64 Host: Z68A-D3-B3 Kernel: 5.2.0-2-amd64 Uptime: 2 days, 38 mins Packages: 1465 (dpkg) Shell: bash 5.0.3 Resolution: 3840x2160 WM: Openbox WM Theme: Onyx Theme: Adwaita-dark [GTK2/3] Icons: oxygen [GTK2/3] Terminal: xfce4-terminal Terminal Font: Monospace 20 CPU: Intel i7-2600K (8) @ 3.800GHz GPU: AMD ATI Radeon HD 7870 GHz Edition Memory: 8683MiB / 16025MiB -- 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 9

[Bug 13863] New: Armed Assault (ArmA) doesn't render any 3D graphics
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=13863 Summary: Armed Assault (ArmA) doesn't render any 3D graphics Product: Wine Version: 1.0-rc4 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)atomnet.co.uk Created an attachment (id=13933) --> (http://bugs.winehq.org/attachment.cgi?id=13933) Entire log minus 40000 duplicate lines. The game fails to display any of the in-game graphics whether it's on the menu or inside the game itself. It still renders the HUD and Menu's themselves, but not the actual 3D game graphics. It spits out the errors (the ones which appear many times in the attached log) about 5000 times a second. -- 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 43

[Bug 34146] New: Wings of Prey demo background image in launcher is not shown
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=34146 Bug #: 34146 Summary: Wings of Prey demo background image in launcher is not shown Product: Wine Version: 1.6 Platform: x86 URL: http://www.fileplanet.com/208822/200000/fileinfo/Wings -of-Prey--Demo OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrey.goosev(a)gmail.com Classification: Unclassified Created attachment 45421 --> http://bugs.winehq.org/attachment.cgi?id=45421 launcher settings (wine) Launcher hasn't background image. -- 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 14

[Bug 47370] New: Regression: Civilization II MGE installer page faults immediately under wine-4.10
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47370 Bug ID: 47370 Summary: Regression: Civilization II MGE installer page faults immediately under wine-4.10 Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: drewwalton19216801(a)gmail.com Distribution: --- Created attachment 64705 --> https://bugs.winehq.org/attachment.cgi?id=64705 Page fault Civilization II MGE is unable to be installed under winehq-devel-4.10 due to the installer page faulting. This is a regression as the installer worked fine under winehq-devel-4.9, and also works under winehq-stable-4.0.1. I've attached the page fault error text, please inform me if anything else is needed. -- 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 4

[Bug 48227] New: Acrobat XI Pro page fault on read access to 0x63696c61 in 32-bit code
by WineHQ Bugzilla 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48227 Bug ID: 48227 Summary: Acrobat XI Pro page fault on read access to 0x63696c61 in 32-bit code Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpb_9876(a)mail.com Distribution: --- Created attachment 65871 --> https://bugs.winehq.org/attachment.cgi?id=65871 Backtrace from Acrobat Adobe Acrobat XI Professional, with almost native-level functionality crashes on Wine 4.19 and later. Rolling back to Wine 4.18 or earlier restores normal operation. Tested on multiple machines running Arch and OpenSUSE Tumbleweed. Backtrace from Acrobat attached. Console output as follows (using Wine 4.21): ` [jpb@No3 ~]$ env WINEPREFIX="/home/omar/.win8" wine start "C://Program Files//Adobe//Acrobat 11.0//Acrobat//Acrobat.exe" ` ` [jpb@No3 ~]$ 002b:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub ` ` [jpb@No3 ~]$ 002b:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub ` ` 002b:fixme:process:SetProcessDEPPolicy (1): stub ` ` 002b:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub ` ` 002b:fixme:heap:RtlSetHeapInformation 0x530000 0 0x32fb4c 4 stub ` ` 002b:fixme:heap:RtlSetHeapInformation 0x110000 0 0x32fb4c 4 stub ` ` 002c:fixme:wer:WerRegisterMemoryBlock (0x5368b8 72) stub ` ` 002b:fixme:ntdll:NtQuerySystemInformation info_class ` ` SYSTEM_PERFORMANCE_INFORMATION ` ` wine: Unhandled page fault on read access to 00000000 at address 7E30410A ` `(thread 002b), starting debugger... ` -- 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 15

[Bug 33476] New: fxc, the Microsoft Effect Compile, to work due to d3d
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=33476 Bug #: 33476 Summary: fxc, the Microsoft Effect Compile, to work due to d3d Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: titan.costa(a)gmail.com Classification: Unclassified Created attachment 44310 --> http://bugs.winehq.org/attachment.cgi?id=44310 fxc log Hi, I can't get the fxc, the Microsoft Effect Compile, to work. Something goes wrong with d3d. The command line is: wine fxc.exe /T fx_2_0 BasicHLSL.fx Both fxc.exe and BasicHLSL.fx come from the DXSDK. d3dcompiler_43.dll must be set as native. Here is the output: NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. fixme:win:EnumDisplayDevicesW ((null),0,0x32f6e8,0x00000000), stub! err:d3d:context_create Failed to set pixel format 1 on device context 0x80026. err:d3d:context_choose_pixel_format Can't find a suitable iPixelFormat err:d3d:context_create Failed to set pixel format 1 on device context 0x6002b. fixme:d3d:wined3d_get_format Can't find format WINED3DFMT_R24_UNORM_X8_TYPELESS (0x49) in the format lookup table fixme:d3d:getDepthStencilBits Unsupported depth/stencil format WINED3DFMT_UNKNOWN. err:d3d:context_create Failed to set pixel format 25 on device context 0x10033. err:d3d:context_create Failed to set pixel format 13 on device context 0x10035. err:d3d:context_choose_pixel_format Can't find a suitable iPixelFormat err:d3d:context_create Failed to set pixel format 1 on device context 0x10037. Failed to create D3D device Please check your SDK installation. disassembly failed; no disassembly produced -- 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 46910] New: ABBYY_FineReader_14_Enterprise crashes during installation
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=46910 Bug ID: 46910 Summary: ABBYY_FineReader_14_Enterprise crashes during installation Product: Wine Version: 4.4 Hardware: x86-64 URL: https://www.abbyy.com/en-us/download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)protonmail.com Distribution: ArchLinux ABBYY_FineReader_14_Enterprise crashes during installation with Wine_4.4 (64bit). The terminal output is in the attachments. You can download the trial version of this application from this URL: https://www.abbyy.com/en-us/download -- 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 47153] New: Arturia Organ B3-V2 crashes after using the drawbars
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47153 Bug ID: 47153 Summary: Arturia Organ B3-V2 crashes after using the drawbars Product: Wine-staging Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blubz(a)gmx.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64381 --> https://bugs.winehq.org/attachment.cgi?id=64381 Error Log after crash Arturia Organ B3-V2, Standalone Demo Version crashes after using one of the drawbars. Used as VST plugin, the program crashes equally. Download: https://www.arturia.com/products/analog-classics/b-3-v/overview -- 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2019