February 2019 - Wine-Bugs - list.winehq.org

[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 Feb. 24, 2019

Feb. 24, 2019

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 Feb. 24, 2019

Feb. 24, 2019

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 Feb. 24, 2019

Feb. 24, 2019

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(a)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 Feb. 24, 2019

Feb. 24, 2019

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

[Bug 30123] New: Mouse pointer is confined in a box lesser than the full screen
by wine-bugs＠winehq.org Feb. 23, 2019

Feb. 23, 2019

http://bugs.winehq.org/show_bug.cgi?id=30123 Bug #: 30123 Summary: Mouse pointer is confined in a box lesser than the full screen Product: Wine Version: 1.4-rc4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: kol(a)MV8660.spb.edu Classification: Unclassified Running TES5:Skyrim on the old system without Xinput2 support and on the modern Fedora 16 (but not on Ubuntu) under Wine 1.3.21 or later versions exhibits the "inertial mouse" bug described in http://appdb.winehq.org/objectManager.php?sClass=version&iId=24749 : after changing the direction of mouse movement the look continues to move in the old direction for some time. Since Wine 1.4-rc1 the old "inertial mouse" bug goes away but it is replaced by the new "clip" bug. The old bug appeared to be caused by the next strings in the dinput_mouse_hook() function in "dlls/dinput/mouse.c": if (This->clipped) pt = This->mapped_center; else GetCursorPos(&pt); which have been changed to GetCursorPos(&pt); in Wine 1.4-rc1. With new versions of Wine the mouse pointer is confined to some box lesser than the full screen. The behaviour of mouse depends on the "HKCU\Software\Wine\X11 Driver\GrabPointer" key. When it is set to "Y", the pointer is strictly confined to a box in game and in menus, when the key is set to "N", the pointer moves free in menus but mouse look in game is free within some limits and becomes very slow beyond these limits. It is similar to Bug#6971 but setting "MouseWarpOverride" to "force" does not change the mouse movement. I experimentally found a simple "patch" to workaround: in the function warp_check() in "dlls/dinput/mouse.c" file the last operator "This->clipped = ..." has to be commented out and "This->clipped = FALSE;" has to be inserted in place of. I do not know how it work but it makes the mouse look correct in Skyrim on my Fedora 10 system and, as far as I can see, does not break other games at least in fullscreen mode. -- 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 28

[Bug 43121] New: Game crashes during DLL load if sound is enabled
by wine-bugs＠winehq.org Feb. 23, 2019

Feb. 23, 2019

https://bugs.winehq.org/show_bug.cgi?id=43121 Bug ID: 43121 Summary: Game crashes during DLL load if sound is enabled Product: Wine Version: 2.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zaplo00(a)mailfence.com Distribution: --- Created attachment 58325 --> https://bugs.winehq.org/attachment.cgi?id=58325 Logs and winedump of DLL I have a game that uses DirectSound. It tries to load a DLL on new game and it succeeds if sound=disabled but with alsa or pulse program crashes in loader.c:tls_alloc_slot. The problem is that the .reloc information in DLL is corrupt. There are multiple entries for the same page, so what wine does is to "relocate twice". Game works with sound using a modified DLL where section size is changed to remove duplicates. Windows 7 and Windows 8.1 both work with original DLL and don't need compatibility mode. Attached are logs with and without sound and winedump output. -- 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 42488] New: Accordance main window contents does not display well
by wine-bugs＠winehq.org Feb. 23, 2019

Feb. 23, 2019

https://bugs.winehq.org/show_bug.cgi?id=42488 Bug ID: 42488 Summary: Accordance main window contents does not display well Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bronsonmathews(a)gmail.com Distribution: --- Created attachment 57354 --> https://bugs.winehq.org/attachment.cgi?id=57354 screenshot See attached screenshot, you can see in this image the contents of the main window is incomplete. It flickers around as i move the mouse around and click and drag making the application unusable. Original bug is here: https://bugs.winehq.org/show_bug.cgi?id=42466 -- 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 46696] New: Feature Request: Define PE CPU type for 64-bit PowerPC systems
by wine-bugs＠winehq.org Feb. 22, 2019

Feb. 22, 2019

https://bugs.winehq.org/show_bug.cgi?id=46696 Bug ID: 46696 Summary: Feature Request: Define PE CPU type for 64-bit PowerPC systems Product: Wine Version: 4.2 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: tpearson(a)raptorengineering.com Distribution: --- Existing PowerPC support in Wine revolves around legacy 32-bit big endian systems using PE CPU type number 20. 64-bit little endian systems should probably receive their own CPU type number to avoid crashes trying to run a 32-bit BE binary on 64-bit LE systems and vice versa. -- 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 1719] MDI child window minimize problem in Delphi VCL applications
by wine-bugs＠winehq.org Feb. 21, 2019

Feb. 21, 2019

https://bugs.winehq.org/show_bug.cgi?id=1719 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Fixed by SHA1| |73b50a24e79b43536364a81d7de | |263151068cfc1 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #35 from Zebediah Figura <z.figura12(a)gmail.com> --- Right, in as much as this bug is/became "minimized windows are 3.1-style icons instead of modern titlebars", this was fixed by the sequence of commits ending in <https://source.winehq.org/git/wine.git/commitdiff/73b50a24e79b43536364a81d7…>. -- 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 0