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

[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 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 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 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

[Bug 38941] New: Text colors are missing
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=38941 Bug ID: 38941 Summary: Text colors are missing Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arromdee(a)atnex.net Distribution: --- I am running the 64 bit Wine 1.7.30 that comes with Mageia Linux 5.0. I am running Wine on DOSCenter from http://nugnugnug.com/ . (This is a program that catalogs DOS games, but it is itself a Windows program). Download the build 035 or whatever one is on the page, then download the daily .DAT file. Unzip them. Also get a DOS game .zip file. I tested this using a legal Doom shareware at http://www.doomworld.com/pageofdoom/files/doom1_1.zip . Run the DOScenter.exe in Wine, and under Settings and Tools, load the .DAT file. Then in the main screen, select auto scan and scan the doom1_1.zip. The scan results show what files should be in the doom1_1.zip and what are missing. These should be labelled with different colors (indicating that the doom1_1.zip contains 6 correct files and one mismatched file), and so should the doom1_1.zip itself. When I actually run it, the files are shown in black and white. As color is the main way that DOScenter reports information, the program is essentially useless. This DOScenter.exe works fine in Windows 7. -- 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 39721] New: Listview custom draw in report mode uses wrong background color
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=39721 Bug ID: 39721 Summary: Listview custom draw in report mode uses wrong background color Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Created attachment 52969 --> https://bugs.winehq.org/attachment.cgi?id=52969 test application from bug 9491 In attached test application listview rows are not colored properly. Split from bug 9491. -- 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 43434] New: StarCraft: Brood War stopped running after 1.19 update
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43434 Bug ID: 43434 Summary: StarCraft: Brood War stopped running after 1.19 update Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iop_jr(a)yahoo.com Distribution: --- Created attachment 58800 --> https://bugs.winehq.org/attachment.cgi?id=58800 Log when trying to start StarCraft 1.19 After the recent update, there's a similar message to bug #42741. But even using staging ClientSdk.dll fails to initialize. So StarCraft is broken again. Full debug logs: http://www.filedropper.com/log_24 -- 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 39

[Bug 47315] New: Pixel Game Maker MV doesn't start.
by wine-bugs＠winehq.org 29 Jul '20

29 Jul '20

https://bugs.winehq.org/show_bug.cgi?id=47315 Bug ID: 47315 Summary: Pixel Game Maker MV doesn't start. Product: Wine-staging Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: takojagi(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- 000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 000b:fixme:winediag:start_process Wine Staging 4.9 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000f:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0012:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0014:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 001c:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0021:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 000f:fixme:service:scmdatabase_autostart_services Auto-start service L"gupdate" failed to start: 2 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:dwmapi:DwmIsCompositionEnabled 0x33fa70 0009:fixme:dwmapi:DwmEnableBlurBehindWindow 0x20078 0x33fa74 0009:fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform 0009:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported 0009:fixme:win:RegisterDeviceNotificationW (hwnd=0x10080, filter=0x33fda0,flags=0x00000000) returns a fake device notification handle! 0009:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:font:RemoveFontMemResourceEx (0x97078301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x97f0f301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x97af7301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x979bb301) stub 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0009:fixme:font:RemoveFontMemResourceEx (0x967c3301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x96576301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x96292301) stub 0009:fixme:font:RemoveFontMemResourceEx (0x9603e301) stub 0009:fixme:netapi32:NetShareEnum Stub (L"\\\\Game.pgmproject" 1 0x33a4a0 -1 0x33a4a8 0x33a498 0x33a49c) 0009:fixme:netapi32:NetShareEnum Stub (L"\\\\Game.pgmproject" 1 0x33a6a0 -1 0x33a6a8 0x33a698 0x33a69c) 0009:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0033F9D8 1 C) semi-stub 0009:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0033F7E8 1 C) semi-stub 0009:fixme:advapi:OpenEventLogW ((null),L"System") stub 0009:fixme:advapi:ReadEventLogA (0xcafe4242,0x00000009,0x00000000,0x7101860,0x00010000,0x33fba8,0x33fbac) stub 0009:fixme:advapi:CloseEventLog (0xcafe4242) stub 0034:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:font:RemoveFontMemResourceEx (0x8e929301) stub 0034:fixme:font:RemoveFontMemResourceEx (0x8d4f8301) stub 0034:fixme:font:RemoveFontMemResourceEx (0x8d3a0301) stub 0034:fixme:font:RemoveFontMemResourceEx (0x8df14301) stub 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:process:SetProcessDEPPolicy (3): stub 0034:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x11fffb0, 0x39c8158, 0x3a4f9c8) stub. 0034:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x32f748, (nil) 0x32f74c 0034:fixme:nls:get_dummy_preferred_ui_language (0x38 0x32f748 (nil) 0x32f74c) returning a dummy value (current locale) 0034:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x32f748, 0x5bddf60 0x32f74c 0034:fixme:nls:get_dummy_preferred_ui_language (0x38 0x32f748 0x5bddf60 0x32f74c) returning a dummy value (current locale) 0034:fixme:winsock:WSALookupServiceBeginW (0x32f444 0x00000ff0 0x32f484) Stub! 0034:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032F1B8 1 C) semi-stub 0034:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032EFC8 1 C) semi-stub 0034:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032ED18 1 C) semi-stub [51:52:0603/184400.268:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8 0034:fixme:iphlpapi:NotifyAddrChange (Handle 0x32f5c0, overlapped 0x5bde62c): stub 0034:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0045:fixme:file:FindFirstFileExW flags not implemented 0x00000002 0034:fixme:win:RegisterDeviceNotificationW (hwnd=0x100c8, filter=0x32f570,flags=0x00000000) returns a fake device notification handle! 0034:fixme:win:RegisterDeviceNotificationW (hwnd=0x100c8, filter=0x32f570,flags=0x00000000) returns a fake device notification handle! [psicopompo@ ~]$ 004f:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 004f:fixme:process:SetProcessDEPPolicy (3): stub 004f:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x106dffb0, 0x12ea8158, 0x12f2f9c8) stub. 004f:fixme:file:FindFirstFileExW flags not implemented 0x00000002 004f:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032FAB8 1 C) semi-stub 004f:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0032F8C8 1 C) semi-stub 004f:fixme:gdi:GdiInitializeLanguagePack stub 004f:fixme:ntdll:EtwEventUnregister (deadbeef) stub. -- 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 9

[Bug 45319] New: wine kindle for pc 1.11, some books picture is blank
by wine-bugs＠winehq.org 27 Jul '20

27 Jul '20

https://bugs.winehq.org/show_bug.cgi?id=45319 Bug ID: 45319 Summary: wine kindle for pc 1.11, some books picture is blank Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: widon1104(a)qq.com Distribution: --- I wine kindle for pc 1.11, almost perfect.But when I open my python book, all picture in it is blank. There are some error msgs print out（show below）. widon(a)widon-desktop:~/.wine/drive_c/Program Files (x86)/Amazon/Kindle$ wine Kindle.exe --- no context for glyph 67 --- no context for glyph 72 --- no context for glyph 65 --- no context for glyph 74 --- no context for glyph 5f --- no context for glyph 75 --- no context for glyph 73 --- no context for glyph 28 ...... The problem python book is: https://www.amazon.cn/dp/B0719GSVJB/ref=tmm_kin_swatch_0?_encoding=UTF8&qid… -- 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 47128] New: Heroes of the Storm: Unreasonable I/ O disk usage on leading to stuttering during game gameplay
by wine-bugs＠winehq.org 26 Jul '20

26 Jul '20

https://bugs.winehq.org/show_bug.cgi?id=47128 Bug ID: 47128 Summary: Heroes of the Storm: Unreasonable I/O disk usage on leading to stuttering during game gameplay Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukycrociato(a)gmail.com Distribution: --- This was experienced from me and a few people I play with on Linux + Wine Distribution: Ubuntu 19.04 Hardware: 19.04, the machine has an AMD Ryzen 5 1600 CPU, GTX NVIDIA 1060 3GB, 2x4GB dual channel DDR4 HyperX RAM, Crucial MX 500 SSD, MSI b350m mortar motherboard, nvidia driver 430.09 Wine version: Tested 4.6, and a couple of others leading pretty much the same results. What was tested: -Playing from an ntfs-3g partition on an HDD (Seagate 5200RPM) -Playing from an ntfs-3g partition on an SSD (Crucial MX500) -Playing from an ext4 partition on an SSD and HDD (the same as above) No matter what configuration, graphics driver, DXVK, wine d3d11 or not, using disk monitoring software like iotop clearly shows unreasonable I/O usage (close to 100%) when those stutters happen for small reads (less than 1 Megabyte) leading the game to be mostly unplayable thanks to those, which for example do not happen on other wine games with the same specs/config even more graphics-demanding. This happens during the normal gameplay, not during the loading. This is obviously worse when the game is run from an HDD, slightly better but still present on an SSD. Of course the I/O usage is different from the one Windows has in this game. I am obviously available for further testing if you tell me what to do to better diagnose that. -- 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