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

[Bug 43659] New: Jurassic Park: Operation Genesis does not launch unless winegstreamer is set to disabled
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=43659 Bug ID: 43659 Summary: Jurassic Park: Operation Genesis does not launch unless winegstreamer is set to disabled Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: arnfranke(a)yahoo.com Distribution: --- Created attachment 59097 --> https://bugs.winehq.org/attachment.cgi?id=59097 Win7 64-bit wineprefix crash Low priority as this bug has a work-around which is to disable winegstreamer. Reproducible on Xubuntu 16.04 64-bit, with AMD Radeon 6520G graphics, on both 32-bit and 64-bit wineprefixes, and set to WinXP and Win7 mode. I have attached crash reports for Win7 mode on a 64-bit prefix and WinXP/32bit. Interestingly enough, the game runs fine without any overrides when it is launched from POL. Interesting that POL would work when ~/.wine does not. https://www.reddit.com/r/wine_gaming/comments/6xwy7o/can_anyone_explain_why… https://appdb.winehq.org/objectManager.php?sClass=version&iId=6088 -- 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 37

[Bug 19777] New: Ad Astra game runs very slow glBlitFramebuffer
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=19777 Summary: Ad Astra game runs very slow glBlitFramebuffer Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P3 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: chrisyate+wine(a)gmail.com CC: chrisyate+wine(a)gmail.com Ad Astra is a free space flight sim available at www.a-astra.com. The game runs (as in starts) successfully, with a clean .wine prefix folder. However once it enters 3D mode the disk starts to grind, wine spits out lots of fixmes and the program runs slowly with fps around 3, max maybe 5. The following is output, over and over until you stop the game. <quote> fixme:d3d:stretch_rect_fbo >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION_EXT (0x506) from glBlitFramebuffer() @ device.c / 6532 fixme:d3d:state_ckeyblend Render state WINED3DRS_COLORKEYBLENDENABLE not implemented yet (repeated 6 times)... </quote> My System is Athlon XP2400+, a NVidia 6200 clone (the Zotac with 256Mb), 1.5Gb ram. Unfortunately I can't confirm whether it would work on my machine if I was running Windows natively. Any other info, please ask. -- 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 16

[Bug 21023] New: SetupDiOpenDevRegKey() returns wrong HKEY
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=21023 Summary: SetupDiOpenDevRegKey() returns wrong HKEY Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: mdealencar(a)gmail.com Created an attachment (id=25222) --> (http://bugs.winehq.org/attachment.cgi?id=25222) bug example In a Windows XP system SetupDiOpenDevRegKey() returns the "Device Parameters" HKEY under the device instance corresponding to the supplied (DeviceInfoSet, &DeviceInfoData) pair. Wine's SetupDiOpenDevRegKey() returns the device instance HKEY instead. The relevant registry keys are not created by Wine, so I had to import them from a Windows XP system Example: Windows HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1\Device Parameters Wine HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1 The attached registry patches and source code enable the reproduction of the bug. -- 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 12

[Bug 39932] New: bat-script with quotes cann't be called using CreateProcess
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=39932 Bug ID: 39932 Summary: bat-script with quotes cann't be called using CreateProcess Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: andrej.skvortzov(a)gmail.com Distribution: --- Created attachment 53340 --> https://bugs.winehq.org/attachment.cgi?id=53340 executable with source code to reproduce the problem This problem exists in software to configure HMI panels from OWEN and Xinje. http://www.owen.ru/catalog/graficheskaya_panel_operatora_s_sensornim_upravl… (Russian) To reproduce this problem easily minimal test program is created. See attached archive cmd_call_batch.tar.xz. Here are technical details of the problem. To appear following conditions need to be met: - bat-script is called using CreateProcess - name of bat-script is quoted - some parameters of bat-scrits are quoted. For example, "test2.bat" "param1" param2 wine runs bat-script using cmd. cmd /c "test2.bat" "param1" param2 On Windows cmd fails if name of bat-script and parameters both are quoted. To avoid this problem attached patch always removes quotes from bat-script's name before cmd is called. -- 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 32374] New: List box with LBS_NODATA set, has very low performance, depending on items count.
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=32374 Bug #: 32374 Summary: List box with LBS_NODATA set, has very low performance, depending on items count. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: johnfound(a)evrocom.net Classification: Unclassified Created attachment 42719 --> http://bugs.winehq.org/attachment.cgi?id=42719 Test application that illustrates the bug. Source code included. List box control, when has LBS_NODATA style set, needs very big time to process LB_SETCOUNT message (this message works only for list box with LBS_NODATA set). On Windows this message is handled for less than 1ms regardless of the count sent by LB_SETCOUNT (because the list box has nothing to allocate/reallocate when LBS_NODATA is set. It only need to set the scroll bar parameters). In WINE (every version but in v1.4 and v1.5 it is really slow) processing this message needs some amount of time, proportional to the item count set by LB_SETCOUNT. As long as this list box style is provided because of its speed, such a behavior can block the execution of the application for very long time. Small test application is attached which measures the time needed for LB_SETCOUNT to be executed on list box with LBS_NODATA set. Source code included. -- 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 43395] New: Wine intermittently crashes after any program terminates
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=43395 Bug ID: 43395 Summary: Wine intermittently crashes after any program terminates Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Every so often, I see one of the following two outputs appear after Wine closes: err:ntdll:RtlLeaveCriticalSection section 0x110940 is not acquired and wine: Unhandled page fault on write access to 0x695de019 at address 0x7bc4f41e (thread 0018), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 96") (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger In the first message the section 0x110940 is constant; in the second the address 0x7bc4f41e is constant but the written address varies. The critical section message appears because a critical section is deleted while owned. The critical section in question appears to be that of the database in services.exe. The crash address is in ntdll/heap.c:HEAP_CreateFreeBlock. It is probably being triggered by code in RtlLeaveCriticalSection(), although it may have a different source. -- 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 8

[Bug 42370] New: Sniper Elite 3 stuck at "Completing Installation 1%"
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=42370 Bug ID: 42370 Summary: Sniper Elite 3 stuck at "Completing Installation 1%" Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: noonetinone(a)gmail.com Distribution: --- This is basically a repeat of the close bug reported by 'acescopezz'. Bug #41493 describes what is happening with the title SE V2. What is different about SE3 is this game includes its own copy of dllcheck.exe. 'acescopezz' posted screen grabs which relevant here. -- 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 35207] New: Rendering issues in Outlast
by wine-bugs＠winehq.org Feb. 27, 2019

Feb. 27, 2019

http://bugs.winehq.org/show_bug.cgi?id=35207 Bug ID: 35207 Summary: Rendering issues in Outlast Product: Wine Version: 1.7.9 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: minor Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: stefan(a)codeweavers.com Classification: Unclassified Regression SHA1: 667f4225b5cc25c5e4f2f725d55a7c011e12c388 Created attachment 46958 --> http://bugs.winehq.org/attachment.cgi?id=46958 terminal output In certain areas like the opening scene some of the textures are missing (replaced by empty white rectangles). The problem exists when effects quality in the video options menu set anything but <very low>. The game uses Unreal Engine 3, no demo has been released. Installing native d3dx9 libraries doesn't solve the problem, but 'winetricks glsl-disable' is a workaround. The problem is present since 667f4225b5cc25c5e4f2f725d55a7c011e12c388 is the first bad commit commit 667f4225b5cc25c5e4f2f725d55a7c011e12c388 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Apr 2 14:54:01 2013 +0200 wined3d: Put local constants into the shader code again. This is essentially a revert of cd7825c89374fb9dd4c20aef2dbfd258713efe6a, with proper precision. :040000 040000 f34c4237fad97c7435396d2fe4644e6a4dd94046 a4cf4d8af7ce2b467dff61ad7e5825884c8fcb36 M dlls Let me know if you need further tests or debug logs. Fedora 19 Nvidia binary drivers 325.15 -- 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 38

[Bug 44395] New: Nvidia 384.111 page fault on write access to 0x7c002fd4 in 32-bit code Beyond Good and Evil (others?)
by wine-bugs＠winehq.org Feb. 24, 2019

Feb. 24, 2019

https://bugs.winehq.org/show_bug.cgi?id=44395 Bug ID: 44395 Summary: Nvidia 384.111 page fault on write access to 0x7c002fd4 in 32-bit code Beyond Good and Evil (others?) Product: Wine Version: 3.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: noabody(a)yahoo.com Distribution: --- Created attachment 60313 --> https://bugs.winehq.org/attachment.cgi?id=60313 Wine 3.0rc6 Geforce GT620 AMD 9950BE Beyond Good and Evil 32-bit prefix Unhandled exception: page fault on write access to 0x7c002fd4 in 32-bit code. Reproducible on multiple CPU/GPU architectures using Nvidia 384.111 Proprietary drivers. No crash with Nouveau on same hardware. Logs naming convention e.g.: w3rc6_gtx1060m_i7-7700hq_bgeubi32 Wine version_gpu_cpu_game/provider/wine prefix Wine 3.0rc6 on GeForce GTX 1060 mobile, Intel i7-7700hq, Beyond Good and Evil from Ubisoft, 32 bit wine prefix. Tested on Wine Stable 3.0, Wine Devel 3.0rc6 from WineHQ Ubuntu Artful for 17.10 64-bit, with clean wine prefix (both 32 and 64 bit) on four computers. Computers using open-source Nouveau (default) work 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 72

[Bug 43393] New: Eagle 8 crash on startup
by wine-bugs＠winehq.org Feb. 24, 2019

Feb. 24, 2019

https://bugs.winehq.org/show_bug.cgi?id=43393 Bug ID: 43393 Summary: Eagle 8 crash on startup Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hildogjr(a)gmail.com Distribution: --- Eagle 8.2.2 by Auto desk (found in https://www.autodesk.com/products/eagle/free-download) crash on startup with the error: "The programa eagle.exe has encoutered a serious problem and needs to close. We are sorry for the inconvenience. This can be cause by a problem in the program or a deficiency in Wine. You may want to check the Application Database for tips about running this application." The Wine log is: fixme:vcruntime:__telemetry_main_invoke_trigger (0x67000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x180000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x65000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x64000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x240000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x61000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x66000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x2a0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x39d0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x3cd0000) 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. fixme:vcruntime:__telemetry_main_invoke_trigger (0x2d0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x3d10000) fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4390000) fixme:win:EnumDisplayDevicesW ((null),0,0x23eb10,0x00000000), stub! fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4510000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x44f0000) fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4670000) fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0xf9f630, 0x34d97a0, 0x35ada48) stub. fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1. fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f470, (nil) 0x23f4a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f470 (nil) 0x23f4a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f470, 0x4051f90 0x23f4a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f470 0x4051f90 0x23f4a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x23f070 0x00000ff0 0x23f068) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x23f370, overlapped 0x4053040): stub fixme:msvcrt:MSVCRT__set_FMA3_enable (0) stub fixme:win:RegisterDeviceNotificationW (hwnd=0x10074, filter=0x23f310,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x10074, filter=0x23f310,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x23ebe0,0x00000000), stub! fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ntdll:EtwRegisterTraceGuidsW (0xfcf3c0, 0x35ae7c8, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x34d9838, (null), (null), 0x35ae7e0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} fixme:file:SetFileCompletionNotificationModes 0x240 1 - stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aad3e0 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aace60 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aacfa0 1 C) semi-stub [0719/123943:FATAL:raw_channel_win.cc(589)] Check failed: g_vista_or_higher_functions.Get().SetFileCompletionNotificationModes( handle_.get().handle, FILE_SKIP_COMPLETION_PORT_ON_SUCCESS). wine: Unhandled exception 0x80000003 in thread 3f at address 0xfc03aa (thread 003f), starting debugger... fixme:vcruntime:__telemetry_main_invoke_trigger (0x67000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x64000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x66000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x540000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x240000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb30000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb60000) 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. fixme:vcruntime:__telemetry_main_invoke_trigger (0x180000000) fixme:vcruntime:__telemetry_main_invoke_trigger ((nil)) fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x180ccf630, 0x1832097a0, 0x1832dda48) stub. fixme:ntdll:EtwRegisterTraceGuidsW (0x180cff3c0, 0x1832de7c8, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x183209838, (null), (null), 0x1832de7e0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:gdi:GdiInitializeLanguagePack stub fixme:msvcrt:MSVCRT__set_FMA3_enable (0) 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.

1 10