August 2019 - Wine-bugs - list.winehq.org

[Bug 47610] New: No Man' s Sky Crashes to Desktop after ~20 minutes starting with wine-4.11 ( Staging)
by wine-bugs＠winehq.org 31 Aug '19

31 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=47610 Bug ID: 47610 Summary: No Man's Sky Crashes to Desktop after ~20 minutes starting with wine-4.11 (Staging) Product: Wine Version: 4.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugz(a)kbrm.net Distribution: --- Created attachment 65037 --> https://bugs.winehq.org/attachment.cgi?id=65037 Winedbg failure dialog Affected Wine: 4.11-4.13 Staging WINEPREFIX: Windows 7 (64-bit) OpSys: Debian GNU/Linux 9.9 (stretch) Display: NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1) Video Driver: nvidia-driver 418.74-1~bpo9+1 DXVK: 1.3.2 OR uninstalled (does not seem to affect symptom) No Man's Sky [Steam X.XX] [NMS BildID: 3397908] crashes to desktop randomly anytime after 20-30 minutes of surface exploration or every time inter-planet flight is attempted. Winedbg does not catch or record crash. Uncertain what the trigger event is, but Traveling in Ship to any other in-system planet will always trigger the crash. But will also happen randomly in-game after the 20-minute mark. Absolutely reproducible for me by loading saved game - launching ship - fly towards closest planet. Game will crash just after launch, or mid-flight, or even as the pulse engines shut off pre-landing - but always - cannot get to surface of destination planet. Issue does not occur in 4.10 Staging - with that version installed I can play for multiple hours (2+ hrs on last run) without any issues. Debug steps so far: Used Steam verify game files function - no issues found Deleted contents of Shader Cache and forced game to re-update (known crash issue) Verified my CPU supports sse4_1 (known crash issue) Un-installed DXVK fron WINEPREFIX - no change in behavior in any version of wine after 4.10 staging [4.10 + DXVK = OK] Downgraded wine (Staging) in steps from 4.13 down to 4.10 - running "wineboot -u" each time before testing Problem goes away in 4.10 Staging - occurs in everything above that Cannot seem to get winedbg to capture output - followed the instructions here: https://wiki.winehq.org/Winedbg - Got winedbg attached to the NME.exe wpid and game was running, when it crashed "in flight" and all I got was: "Process of pid=011c has terminated" Wine-dbg>bt You must be attached to a process to run this command. Not sure what else to include since wine is not trapping this crash? Willing to try anything to test/resolve as downgrading to 4.10 breaks all of my Blizzard games. -- 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 16

[Bug 47684] New: Pressing CTRL+F in regedit & entering text will not enter anything in the input box
by wine-bugs＠winehq.org 31 Aug '19

31 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=47684 Bug ID: 47684 Summary: Pressing CTRL+F in regedit & entering text will not enter anything in the input box Product: Wine Version: 4.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: madebr(a)gmail.com Distribution: --- When wanting to find a string in the hive by pressing CTRL+F and start entering the text, nothing appears in the input box. I expect the entered text to appear in the input box. How to reproduce: 1. Start regedit (`wine regedit`) 2. Press CTRL+F 3. Enter your text This works: 1. Start regedit (`wine regedit`) 2. Press CTRL+F 3. Hover with your mouse inside (or outside) the find window 4. Enter your text So it appears some -- 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 1

[Bug 34830] New: rpcrt4:cstub fails and crashes on Windows 8
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

http://bugs.winehq.org/show_bug.cgi?id=34830 Bug #: 34830 Summary: rpcrt4:cstub fails and crashes on Windows 8 Product: Wine Version: 1.7.5 Platform: x86 OS/Version: Windows Status: NEW Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified The rpcrt4:cstub conformance test has a number of test failures and crashes on Windows 8: cstub.c:519: Test failed: QueryInterfacevtbl 1 not updated 776C2F4B 76085EBB cstub.c:520: Test failed: AddRefvtbl 1 not updated 776BF425 76085ECE cstub.c:524: Test failed: Invokevtbl 1 not updated 776BF839 7607CC41 cstub.c:525: Test failed: IsIIDSupportedvtbl 1 not updated 776CF314 76102697 cstub.c:527: Test failed: DebugServerQueryInterfacevtbl 1 not updated 776CF2ED 76102671 cstub.c:528: Test failed: DebugServerReleasevtbl 1 not updated 776C767F 76102684 cstub.c:530: Test failed: QueryInterfacevtbl 2 not updated 776C2F4B 76085EBB cstub.c:531: Test failed: AddRefvtbl 2 not updated 776BF425 76085ECE cstub.c:533: Test failed: Connectvtbl 2 not updated 776CF28C 7610264B cstub.c:534: Test failed: Disconnectvtbl 2 not updated 776BF0D3 7607CC1B cstub.c:535: Test failed: Invokevtbl 2 not updated 776BF839 7607CC41 cstub.c:536: Test failed: IsIIDSupportedvtbl 2 not updated 776CF314 76102697 cstub.c:537: Test failed: CountRefsvtbl 2 not updated 776CF2D2 7610265E cstub.c:538: Test failed: DebugServerQueryInterfacevtbl 2 not updated 776CF2ED 76102671 cstub.c:539: Test failed: DebugServerReleasevtbl 2 not updated 776C767F 76102684 cstub.c:541: Test failed: QueryInterfacevtbl 3 not updated 776C2F4B 76085EBB cstub.c:542: Test failed: AddRefvtbl 3 not updated 776BF425 76085ECE cstub.c:546: Test failed: Invokevtbl 3 not updated 776BF839 7607CC41 cstub.c:547: Test failed: IsIIDSupportedvtbl 3 not updated 776CF314 76102697 cstub.c:549: Test failed: DebugServerQueryInterfacevtbl 3 not updated 776CF2ED 76102671 cstub.c:550: Test failed: DebugServerReleasevtbl 3 not updated 776C767F 76102684 cstub.c:564: Test failed: wrong proxy 1 func 0 776BF1AA/76080EFB cstub.c:565: Test failed: wrong proxy 1 func 1 776BF4CB/7607CC2E cstub.c:566: Test failed: wrong proxy 1 func 2 776BF16A/7607CBF5 cstub.c:584: Test failed: wrong proxy 3 func 0 776BF1AA/76080EFB cstub.c:585: Test failed: wrong proxy 3 func 1 776BF4CB/7607CC2E cstub.c:586: Test failed: wrong proxy 3 func 2 776BF16A/7607CBF5 cstub.c:755: this is the last test seen before the exception cstub: unhandled exception c0000005 at 775CB76F The crash happens in this call of create_proxy_test(): create_proxy_test( ppsf, &IID_if2, if2_proxy_vtbl.Vtbl ); -- 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.

1 9

[Bug 47050] New: typedef'd anonymous structs typedef' d names are not used in interface methods
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=47050 Bug ID: 47050 Summary: typedef'd anonymous structs typedef'd names are not used in interface methods Product: Wine Version: 4.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: richard(a)torproject.org Distribution: --- The widl (and midl) tool generate a unique name for anonymous structs, but midl also includes the typedef'd name and uses it for interface methods. With the following struct definition: typedef struct { long data; } Bar; widl function signatures like this: void _stdcall doBaz([in] __WIDL_TypedefBug_generated_name_00000000* b); while midl generates this: void _stdcall doBaz([in] Bar* b); min-repro: https://github.com/pospeselr/mingw-widl-bug/tree/typedef_bug Includes tlb generated by widl 4.5 and midl 8.01.0622 -- 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 43387] New: valgrind shows several definite leaks in dlls/ windowscodecs/tests/metadata.c
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=43387 Bug ID: 43387 Summary: valgrind shows several definite leaks in dlls/windowscodecs/tests/metadata.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: windowscodecs Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ==2263== 16 bytes in 1 blocks are definitely lost in loss record 116 of 603 ==2263== at 0x7BC51061: notify_alloc (heap.c:254) ==2263== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2263== by 0x4BBB1B1: MetadataQueryReader_CreateInstance (metadataquery.c:624) ==2263== by 0x4BBAE68: mqr_GetMetadataByName (metadataquery.c:540) ==2263== by 0x4A3A786: IWICMetadataQueryReader_GetMetadataByName (wincodec.h:1605) ==2263== by 0x4A3A786: test_metadata_gif (???:0) ==2263== by 0x4A40077: func_metadata (metadata.c:3077) ==2263== by 0x4A51AF9: run_test (test.h:603) ==2263== by 0x4A51F58: main (test.h:687) ==2263== ==2263== 64 bytes in 4 blocks are definitely lost in loss record 300 of 603 ==2263== at 0x7BC51061: notify_alloc (heap.c:254) ==2263== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2263== by 0x4BBB1B1: MetadataQueryReader_CreateInstance (metadataquery.c:624) ==2263== by 0x4BBAE68: mqr_GetMetadataByName (metadataquery.c:540) ==2263== by 0x4A3F47F: IWICMetadataQueryReader_GetMetadataByName (wincodec.h:1605) ==2263== by 0x4A3F47F: test_queryreader (???:0) ==2263== by 0x4A4003B: func_metadata (metadata.c:3065) ==2263== by 0x4A51AF9: run_test (test.h:603) ==2263== by 0x4A51F58: main (test.h:687) ==2263== ==2263== 212 bytes in 1 blocks are definitely lost in loss record 446 of 603 ==2263== at 0x7BC51061: notify_alloc (heap.c:254) ==2263== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2263== by 0x7B44A252: HeapAlloc (heap.c:271) ==2263== by 0x7B44A53F: GlobalAlloc (heap.c:389) ==2263== by 0x4A3040D: create_stream (metadata.c:208) ==2263== by 0x4A3768B: test_metadata_gif (metadata.c:1340) ==2263== by 0x4A40077: func_metadata (metadata.c:3077) ==2263== by 0x4A51AF9: run_test (test.h:603) ==2263== by 0x4A51F58: main (test.h:687) ==2263== -- 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 22383] New: Dragon Age: Origins - massive flickering when StrictDrawOrdering is disabled
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

http://bugs.winehq.org/show_bug.cgi?id=22383 Summary: Dragon Age: Origins - massive flickering when StrictDrawOrdering is disabled Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: NEW Keywords: regression Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: hverbeet(a)gmail.com Using wine-1.1.42-390-g4fc6512 + the patch from bug 22202, there is massive flickering of vertical black lines across the intro video. Disabling StrictDrawOrdering fixes it. Can't seem to get a screenshot, but if you really need one, let me know. -- 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.

1 33

[Bug 42681] New: Regression: Graphics/ Texture no longer render correctly in Reflex Arena
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=42681 Bug ID: 42681 Summary: Regression: Graphics/Texture no longer render correctly in Reflex Arena Product: Wine Version: 2.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: firestarw(a)gmail.com Distribution: --- Game is Reflex Arena (https://www.reflexarena.com/) a DX10 game that that requires steam to run When in game in a map, in wine versions 2.0 and 2.1, the game renders ok (not fully normal compared to windows but playable) Screenshot (map is aerowalk): https://cdn.discordapp.com/attachments/266419049372581889/29354471255035084… >From wine version 2.2 onwards, the graphics render as black Screenshot from wine 2.4 (map is aerowalk): https://cdn.discordapp.com/attachments/266419049372581889/29354470385988403… -- 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 10

[Bug 46315] New: Vypress Chat 2.1.9 MSI installer crashes without native jscript
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=46315 Bug ID: 46315 Summary: Vypress Chat 2.1.9 MSI installer crashes without native jscript Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- The installer crashes with a "fatal error", unless native jscript is used. See the linked ReactOS ticket for a download. winetricks wsh57 fixes the issue. Part of the log: > 002d:fixme:msi:AutomationObject_GetIDsOfNames Unknown member L"e", clsid {000c109e-0000-0000-c000-000000000046} > 002d:fixme:jscript:JSGlobal_Enumerator > 0027:err:msi:ITERATE_Actions Execution halted, action L"VypressUpgradeEx" returned 1603 -- 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 45420] New: Titanfall 2 Multiplayer mode stuck on Attempting Connection
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=45420 Bug ID: 45420 Summary: Titanfall 2 Multiplayer mode stuck on Attempting Connection Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: alex.skatingcassano(a)gmail.com Distribution: --- Created attachment 61738 --> https://bugs.winehq.org/attachment.cgi?id=61738 Console log with and without WINEDEBUG=+bcrypt In Titanfall 2, after clicking "Multiplayer" in the menu, the game gets stuck on "Attempting Connection". Console output with and without WINEDEBUG=+bcrypt in attachment. Tested with WineD3D and DXVK, both leading to the same result. -- 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 47494] New: SuperTux: Fullscreen mode not working on MacOSX ( Invalid monitor handle)
by wine-bugs＠winehq.org 30 Aug '19

30 Aug '19

https://bugs.winehq.org/show_bug.cgi?id=47494 Bug ID: 47494 Summary: SuperTux: Fullscreen mode not working on MacOSX (Invalid monitor handle) Product: Wine Version: 4.12.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com When I try to run SuperTux in fullscreen mode, on OS X, the window gets hidden. $ wine --version wine-4.12.1 $ openssl sha256 SuperTux-v0.6.0-win32.msi SHA256(SuperTux-v0.6.0-win32.msi)= d81ac0ad043a17019d9c71fcaec4839620efd445feedc4b35f3379f8cb3c2069 Steps to reproduce: 1. Install SuperTux 0.6.0 from https://github.com/SuperTux/supertux/releases/download/v0.6.0/SuperTux-v0.6… 2. Start the game, go to Settings, put a check mark next to "Full screen". Result: Window is hidden, music plays. Expected: Window is shown. Console displays the following: 002d:err:display:macdrv_GetMonitorInfo invalid monitor handle -- 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 10