wine-bugs February 2019

wine-bugs@winehq.org

1 participants
7706 discussions

[Bug 45234] New: TIDAL updater hangs at
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=45234 Bug ID: 45234 Summary: TIDAL updater hangs at Product: Wine Version: 3.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 61464 --> https://bugs.winehq.org/attachment.cgi?id=61464 Wine log The updater downloads and starts the new setup, but that hangs at "Extracting files from archive" without finishing. -- 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 46557] New: Crashed when trying to run Chinese localized version of Blizzard Battle.net Client
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46557 Bug ID: 46557 Summary: Crashed when trying to run Chinese localized version of Blizzard Battle.net Client Product: Wine-staging Version: 4.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jiaxun.yang(a)flygoat.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63429 --> https://bugs.winehq.org/attachment.cgi?id=63429 Battlenet crash backtrace Crashed when trying to run Chinese localized version of Blizzard Battle.net Client. The binary can be obtained from this link. https://www.battlenet.com.cn/download/getInstaller?os=win&installer=Battle.… The backtrace is attached. Please take a look. Thanks -- 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 46642] New: Anno 1404 graphical glitch, 4.1 regression
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46642 Bug ID: 46642 Summary: Anno 1404 graphical glitch, 4.1 regression Product: Wine Version: 4.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: hnpohl(a)gmail.com Distribution: --- Created attachment 63560 --> https://bugs.winehq.org/attachment.cgi?id=63560 screenshot A screenshot of the glitch is attached. I did a "quick" bisect: commit 9a1d0797937f39ef2296e1d34b095b29ae848c20 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Mon Jan 28 23:09:15 2019 -0600 wined3d: Store render states in the wined3d_stateblock_state structure. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 46566] New: Unity games fail to start with wine 4.0
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46566 Bug ID: 46566 Summary: Unity games fail to start with wine 4.0 Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)protonmail.com Distribution: --- Unity games fail to start with wine 4.0-rc7 or Wine 4.0 stable, but they run with wine 3.21-staging without any problem. I use DXVK 0.96 BTW, but I don't think that this issue is related to DXVK, because not all the games that I tested are DX11, some of them are DX9. In addition, DX11 games that aren't unity games runs without any problem. The list of unity games that I tried: Cuphead Distance Life is Strange Ori and The Blind Forest - Definitive Edition The error that I get: 0009:err:vulkan:wine_vk_init Failed to load libvulkan.so.1. 0009:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan. 0009:err:module:find_forwarded_export module not found for forward 'winevulkan.wine_vkGetInstanceProcAddr' used by L"C:\\windows\\system32\\vulkan-1.dll" 0009:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan. 0009:err:module:find_forwarded_export module not found for forward 'winevulkan.wine_vkGetInstanceProcAddr' used by L"C:\\windows\\system32\\vulkan-1.dll" wine: Call from 0x7bc53259 to unimplemented function vulkan-1.dll.vkGetInstanceProcAddr, aborting -- 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 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 25 Feb '19

25 Feb '19

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 46556] New: FINAL FANTASY XI and FFXiPadConfig.exe utility no longer detect Logitech F710 via (emulated) DirectInput; under XInput, detects Axes 5 and 6 as buttons
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46556 Bug ID: 46556 Summary: FINAL FANTASY XI and FFXiPadConfig.exe utility no longer detect Logitech F710 via (emulated) DirectInput; under XInput, detects Axes 5 and 6 as buttons Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: emegas(a)vecanti.org Distribution: --- Created attachment 63427 --> https://bugs.winehq.org/attachment.cgi?id=63427 Backtrace When using a method to change areas that involves an NPC or non-player object, there is an high chance that FINAL FANTASY XI will crash directly after the menus load in the new area--always immediately after the "== Area: [name] ==" identifier is displayed in the log--before the player or NPCs have a chance to load into the map. (Restarting the game afterwards will always load the new area successfully.) Home Points, Survival Guides, the Mog Garden NPCs in front of the entrances to the Western Adoulin and Eastern Adoulin Rent-a-Rooms, Waypoints and Proto-Waypoints, and using a Warp Ring (thus opening up the likelihood that _any_ type of magical or item-triggered area change can cause it) all appear to cause the crash. On the other hand, changing areas via "zone lines" (walking between them), the "Button" in Ru'Lude Gardens and changing areas from within a Mog House do not _not_ seem to cause the crash. Probably the easiest way to repro this is to use a Home Point to change between different Home Points within the same city until the crash is seen (ex. Bastok Mines #1 -> Bastok Markets #1 -> Port Bastok #1 -> repeat). Tested and confirmed in both 4.0 release and wine-4.0-251-g7003ba44892 (vanilla and staging). The debug information attached is from wine-4.0-251-g7003ba44892 (vanilla). (Tested on Gentoo Linux kernel 4.20.5 with nvidia-drivers 415.27) -- 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 5

[Bug 46574] New: Drobo NAS controll software Only black windows opens and it crashes.
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46574 Bug ID: 46574 Summary: Drobo NAS controll software Only black windows opens and it crashes. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: edmundzed(a)gmail.com Distribution: --- Created attachment 63450 --> https://bugs.winehq.org/attachment.cgi?id=63450 Program error details https://www.drobo.com/drobo-downloads-2/ The control software needed for Drobo NAS crashed immediately. -- 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 46716] New: utherverse client : crash when loading and installing
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46716 Bug ID: 46716 Summary: utherverse client : crash when loading and installing Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: www.max87@yahoo.fr Distribution: --- Created attachment 63684 --> https://bugs.winehq.org/attachment.cgi?id=63684 report generate by wine on the crash When i lunch the application client Uhterverse i got a bug report from wine and the loading of the client is stopped I tryed a reinstall of the client and it done the same a bug appared but the installation finished -- 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 45570] New: League of Legends 8.12+ fails to start a game ( anticheat engine, incorrect implementation of LdrInitializeThunk)
by wine-bugs＠winehq.org 24 Feb '19

24 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=45570 Bug ID: 45570 Summary: League of Legends 8.12+ fails to start a game (anticheat engine, incorrect implementation of LdrInitializeThunk) Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Diagnosed by Andrew Wesie; partially split off from bug 45327. The game expects LdrInitialize thunk to be called whenever a new thread is created and that the first argument is the CONTEXT for the thread. Furthermore, it expects that %eax will contain the thread's entry point. -- 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 43393] New: Eagle 8 crash on startup
by wine-bugs＠winehq.org 24 Feb '19

24 Feb '19

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

Jump to page:

2025

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 February 2019