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

[Bug 49562] New: Regression - Godot Engine have broken shadows and doesn't read properly settings file
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=49562 Bug ID: 49562 Summary: Regression - Godot Engine have broken shadows and doesn't read properly settings file Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Created attachment 67701 --> https://bugs.winehq.org/attachment.cgi?id=67701 Broken shader log Hi, When I run Godot Engine in Wine-devel 5.12 or Wine-staging 5.12, then main viewport doesn't show any arrows which before shows directions. Also console log is spammed by shadow compilation error. Also when opening project manager, Godot is unable to read settings from file. It works fine without errors with Wine 5.0.1 stable. -- 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 49604] New: TES4:Oblivion hang on filter_graph.cs on Wine 5.13
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=49604 Bug ID: 49604 Summary: TES4:Oblivion hang on filter_graph.cs on Wine 5.13 Product: Wine Version: 5.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Regression SHA1: 99851ca4c2edd4b921c91327540d69dec77c5df7 Distribution: ArchLinux Running Oblivion under wine 5.13 cause the game to hang indefinetly on filter_graph.cs critical section with the following message. 01dc:err:ntdll:RtlpWaitForCriticalSection section 012E4E54 "filtergraph.c: filter_graph.cs" wait timed out in thread 01dc, blocked by 0188, retrying (60 sec) The game was running fine with 5.12 Bisecting gave the first bad commit: 99851ca4c2edd4b921c91327540d69dec77c5df7 is the first bad commit commit 99851ca4c2edd4b921c91327540d69dec77c5df7 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Jul 15 10:23:00 2020 +0200 ntdll: Initialize the thread signal stack in the common code. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> the commit isn't cleanly reverted. the previous commit ( quartz: Run the graph asynchronously if necessary.) run pefectly 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 47501] New: Toontown Rewritten on Wine 4.12: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 ( thread 0064)
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=47501 Bug ID: 47501 Summary: Toontown Rewritten on Wine 4.12: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 (thread 0064) Product: Wine Version: 4.12 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neel(a)neelc.org Created attachment 64889 --> https://bugs.winehq.org/attachment.cgi?id=64889 Backtrace from TTREngine.exe on Wine While the TTR launcher works and I am able to log in, after logging in when TTR attempts to launch the game, I get this error: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 (thread 0064). My computer is a HP Slimline 290-p0014 with an Intel Core i7-8700, 24GB RAM, an nVidia GT 1030 (Zotac), and 64-bit FreeBSD 12.0. I had this issue on other version of Wine on FreeBSD and Linux, both with nVidia and Intel graphics. I am running a 32-bit version of Wine I compiled with the instructions here: https://wiki.winehq.org/FreeBSD -- 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 19775] New: Largo Winch: crash with hardware vertex shader
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=19775 Summary: Largo Winch: crash with hardware vertex shader Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Created an attachment (id=23166) --> (http://bugs.winehq.org/attachment.cgi?id=23166) Full log +all,-several, stripped from GetTick line noise. With default settings in winecfg, the application crashes immediately before displaying the logos, upon return from d3d8 CreateVertexShader. Disabling the hardware vertex shader in winecfg allows the game to start (but see bug #19773). This is the first application I faced where I had to do this -- can I expect 3D applications to generally work well without hardware VS? The full log (attached) shows a NULL pointer access by the application immediately following return from IDirect3DDevice8Impl_CreateVertexShader. fixme:d3d8:ValidateVertexShader (0x102d278 (nil) (nil) 1 0x33ef20): stub [2x] 0009:trace:d3d8:parse_token 0x40010007 REG(D3DVSDE_TEXCOORD0, D3DVSDT_FLOAT2) 0009:trace:d3d8:IDirect3DDevice8Impl_CreateVertexShader (0x15e4e0) : returning 0x10426f0 (handle 0xf0000021) 0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0x48b24d ip=0048b24d tid=0009 wine: Unhandled page fault on read access to 0x00000000 at address 0x48b24d (thread 001c) =>0 0x0048b24d in largowinch (+0x8b24d) (0x7ee2b010) I'm not aware of a demo of this application. Running Ubuntu Intrepid with Intel i915, but the crash also occurs on MacOS with NVidia 9400M. -- 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 12

[Bug 49474] New: Chaos Legion does not work with wine quartz.
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=49474 Bug ID: 49474 Summary: Chaos Legion does not work with wine quartz. Product: Wine Version: 5.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: SolisX007(a)yahoo.com Distribution: --- Chaos Legion does not work with wine quartz. -- 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 11

[Bug 10106] New: Cannot disable cursor blinking in the wine GUI
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=10106 Summary: Cannot disable cursor blinking in the wine GUI Product: Wine Version: 0.9.36. Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: test AssignedTo: wine-bugs(a)winehq.org ReportedBy: zhoujiafan(a)gmail.com I have updated the wine to wine-0.9.36 in my Linux Fedora Core5. Currently the cursor is always blinking. For example, the editplus running in wine. I tried to edit the wine registry as follows: HKEY_CURRENT_USER -> CONTROL PANEL -> Desktop -> CursorBlinkRate = -1 And this does not stop the blinking cursor!!! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 24

[Bug 48856] New: Renegade Ops needs D3DX10GetImageInfoFromMemory implementation
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=48856 Bug ID: 48856 Summary: Renegade Ops needs D3DX10GetImageInfoFromMemory implementation Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Stucks with: fixme:d3dx:D3DX10GetImageInfoFromMemory src_data 6BDE19B8, src_data_size 16512, pump 00000000, img_info 0032F624, hresult 00000000. err:seh:setup_exception_record stack overflow 676 bytes in thread 015c eip 00000000 esp 0023108c stack 0x230000-0x231000-0x330000 -- 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 43949] New: WINEDEBUG=+relay does not work on armv7l (and/ or when CWD is a symlink)
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43949 Bug ID: 43949 Summary: WINEDEBUG=+relay does not work on armv7l (and/or when CWD is a symlink) Product: Wine Version: 2.19 Hardware: arm OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- While getting logs for bug 43945, I Noticed that WINEDEBUG=relay does not work (+tid,+seh were fine): ../../../tools/runtest -q -P wine -T ../../.. -M d3dx9_36.dll -p d3dx9_36_test.exe.so mesh && touch mesh.ok 0047:trace:relay:load_list L"RelayExclude" = L"ntdll.RtlEnterCriticalSection;ntdll.RtlTryEnterCriticalSection;ntdll.RtlLeaveCriticalSection;kernel32.48;kernel32.49;kernel32.94;kernel32.95;kernel32.96;kernel32.97;kernel32.98;kernel32.TlsGetValue;kernel32.TlsSetValue;kernel32.FlsGetValue;kernel32.FlsSetValue;kernel32.SetLastError" 0047:trace:relay:load_list L"RelayFromExclude" = L"winex11.drv;winemac.drv;user32;gdi32;advapi32;kernel32" 0047:Call KERNEL32.__wine_kernel_init() ret=af0ff758 Warning: could not find DOS drive for current working directory '/var/host/media/removable/SD Card/wine-git/dlls/d3dx9_36/tests', starting in the Windows directory. wine client error:47: write: Invalid argument Makefile:369: recipe for target 'mesh.ok' failed make: *** [mesh.ok] Error 1 If I remove +relay, it's fine. Possibly relevant, CWD is $HOME/wine-git/dlls/d3dx9_36/tests, while $HOME/wine-git is a symlink to /var/host/media/removable/SD Card/. -- 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 49581] New: wine's KERNEL32.DLL missing code
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=49581 Bug ID: 49581 Summary: wine's KERNEL32.DLL missing code Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: rne1(a)protonmail.com Distribution: --- when attempting to run hard drive duplication software 'disk genius'(https://www.diskgenius.com/) the error shown in this forum link is displayed: https://forum.winehq.org/viewtopic.php?f=8&t=34144 -- 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 4

[Bug 44129] New: Bayonetta: much slower than Windows
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44129 Bug ID: 44129 Summary: Bayonetta: much slower than Windows Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: tod.jackson(a)gmail.com Distribution: --- Created attachment 59870 --> https://bugs.winehq.org/attachment.cgi?id=59870 brief fixme I got a chance to test Bayonetta in Window 7 and realized it's much slower in Wine (about half the fps) than Windows, whereas I previously was underestimating my hardware. I recall reading that such a high discrepancy should probably be reported. The game is already difficult to play under Wine because it it requires one of the async read/write patches in bug 42982 to make headway. Also note the game requires CSMT for coherent visuals. Can this fixme cause a major performance problem? fixme:d3d:state_zenable Unrecognized depth buffer type 0xffffffff. The game seems unusual in that it ties all actions to vblank/vsync, if that makes any sense. In Wine terms I guess that means it relies on this function, though as I'm not a developer I'm likely wrong: fixme:d3d9:d3d9_device_SetMaximumFrameLatency iface 0x1574b0, max_latency 1 stub! https://msdn.microsoft.com/en-us/library/windows/desktop/ff471334(v=vs.85).… Anyway, the game already requires a native d3dcompiler_43 to avoid HLSL parsing failure, but any tips/patches/suggestions to improve performance would be much welcomed. I tested a recent Mesa git version that has a GLSL cache but it didn't really help. I understand that I'm already running an Intel potato, but based on my recent Windows experience I think we could get the game to native speed one day. Also, I bet that all of Platinum Games' ports suffer the same engine (for example Nier Automata), though I'm not sure. Full fixmes attached for completeness, also tried a native xinput and d3dx9_43 with no change. -- 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 18