August 2016 - Wine-Bugs - list.winehq.org

[Bug 41084] New: Unimplemented function msvcp140.dll.__crtCreateSemaphoreExW needed by Battle.net
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=41084 Bug ID: 41084 Summary: Unimplemented function msvcp140.dll.__crtCreateSemaphoreExW needed by Battle.net Product: Wine Version: 1.9.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: audiger(a)live.fr Distribution: --- With the new version of Battle.net which needed msvcp140, there is a function not implemented and this caused an error during the launching: wine: Call from 0x7b43bfac to unimplemented function msvcp140.dll.__crtCreateSemaphoreExW, aborting wine: Unimplemented function msvcp140.dll.__crtCreateSemaphoreExW called at address 0x7b43bfac (thread 00c2), starting debugger... -- 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 38726] New: valgrind shows uninitialized memory in qcap/tests/smartteefilter.c
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=38726 Bug ID: 38726 Summary: valgrind shows uninitialized memory in qcap/tests/smartteefilter.c Product: Wine Version: 1.7.44 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Fedora ==2035== Conditional jump or move depends on uninitialised value(s) ==2035== at 0x5FEF54F: QualityControlRender_DoQOS (qualitycontrol.c:214) ==2035== by 0x5FE6F18: BaseRendererImpl_Receive (renderer.c:411) ==2035== by 0x5FE670E: BaseRenderer_Receive (renderer.c:222) ==2035== by 0x5FE280C: MemInputPin_Receive (pin.c:1122) ==2035== by 0x5FE28DE: IMemInputPin_Receive (strmif.h:3395) ==2035== by 0x5FE28DE: MemInputPin_ReceiveMultiple (???:0) ==2035== by 0x47A39D0: IMemInputPin_ReceiveMultiple (strmif.h:3398) ==2035== by 0x47A39D0: SinkMemInputPin_ReceiveMultiple (???:0) ==2035== by 0x47A3856: IMemInputPin_ReceiveMultiple (strmif.h:3398) ==2035== by 0x47A3856: SinkMemInputPin_Receive (???:0) ==2035== by 0x5F10141: IMemInputPin_Receive (strmif.h:3395) ==2035== by 0x5F10141: BaseOutputPinImpl_Deliver (???:0) ==2035== by 0x5F05B6A: SmartTeeFilterInput_Receive (smartteefilter.c:436) ==2035== by 0x5F11A8F: MemInputPin_Receive (pin.c:1122) ==2035== by 0x47A4224: IMemInputPin_Receive (strmif.h:3395) ==2035== by 0x47A4224: media_thread (???:0) ==2035== by 0x7BC81BB7: ??? (signal_i386.c:2682) ==2035== by 0x7BC81BFE: call_thread_func (signal_i386.c:2741) ==2035== by 0x7BC81B95: ??? (signal_i386.c:2682) ==2035== by 0x7BC88D78: start_thread (thread.c:443) ==2035== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so) ==2035== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so) ==2035== Uninitialised value was created by a client request ==2035== at 0x7BC4A7FD: mark_block_uninitialized (heap.c:208) ==2035== by 0x7BC4A952: initialize_block (heap.c:239) ==2035== by 0x7BC4ECB4: RtlAllocateHeap (heap.c:1716) ==2035== by 0x5FEEA65: QualityControlImpl_Create (qualitycontrol.c:41) ==2035== by 0x5FE68AC: BaseRenderer_Init (renderer.c:271) ==2035== by 0x5F7CE5B: NullRenderer_create (nullrenderer.c:243) ==2035== by 0x5F767F4: DSCF_CreateInstance (main.c:133) ==2035== by 0x4C707E4: IClassFactory_CreateInstance (unknwn.h:226) ==2035== by 0x4C707E4: CoCreateInstance (???:0) ==2035== by 0x47A3ACA: create_SinkFilter (smartteefilter.c:578) ==2035== by 0x47A64D4: test_smart_tee_filter_in_graph (smartteefilter.c:1555) ==2035== by 0x47A808B: test_smart_tee_filter (smartteefilter.c:1786) ==2035== by 0x47A9097: func_smartteefilter (smartteefilter.c:2028) ==2035== by 0x47A9EC5: run_test (test.h:584) ==2035== by 0x47AA30D: main (test.h:666) ==2035== -- 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 37847] New: Shantae - Risky's Revenge has glitchy graphics
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=37847 Bug ID: 37847 Summary: Shantae - Risky's Revenge has glitchy graphics Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: emailofchris(a)gmail.com Distribution: --- Created attachment 50406 --> https://bugs.winehq.org/attachment.cgi?id=50406 Terminal output while playing Shantae - Risky's Revenge for a short time. Sprites and other graphics are often glitchy in Shantae - Risky's Revenge. Here are pictures: http://imgur.com/a/jD6FC I've attached the terminal output, which mostly consists of one error repeated a few thousand times, interspersed with a few others. -- 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 40385] New: usp10:usp10 regression caused by new cross-compiler
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=40385 Bug ID: 40385 Summary: usp10:usp10 regression caused by new cross-compiler Product: Wine Version: 1.9.6 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The WineHQ upgrade changed the cross-compiler used to generate the reference WineTest executables. Since the upgrade the usp10:usp10 64 bit test has this failure on Windows Vista to Windows 10: usp10.c:3087: Test failed: ScriptStringCPtoX should return E_INVALIDARG not 00000000 See: https://test.winehq.org/data/tests/usp10:usp10.html https://www.winehq.org/pipermail/wine-devel/2016-March/112371.html I can reproduce the problem with this compiler: $ i686-w64-mingw32-gcc --version i686-w64-mingw32-gcc (GCC) 5.3.1 20160205 But if I recompile the tests with -O0 the failures go away which points to a compiler bug. We need to either: * Switch to a non buggy compiler to build the reference WineTest executables. (which might involve reporting the bug in the first place) * Add 'CFLAGS = -g -O0' to the test's Makefile.in as a workaround. (preferably once we can point to a relevant compiler bug) * Find some other nicer workaround in the C file. -- 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 30844] New: VirtualDJ Home Free do not work and hangs sometimes.
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

http://bugs.winehq.org/show_bug.cgi?id=30844 Bug #: 30844 Summary: VirtualDJ Home Free do not work and hangs sometimes. Product: Wine Version: 1.5.5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mayanksuman(a)live.com Classification: Unclassified Created attachment 40392 --> http://bugs.winehq.org/attachment.cgi?id=40392 Crash report when VirtualDJ Home is left undisturbed for a while VirtualDJ Home Free sometimes fail after being idle for a while. In Browser window VirtualDJ show + sign before Music folder even if it does not hold anything. Clicking on + crashes the program. The playback quality is also bad. -- May be due to bad buffer setting. -- 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 10

[Bug 41089] New: Regression bug: E-Sword Search now showing a black dialog.
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=41089 Bug ID: 41089 Summary: Regression bug: E-Sword Search now showing a black dialog. Product: Wine Version: 1.9.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maznoe(a)yahoo.com Distribution: --- This is a regression bug between 1.9.14 and 1.9.15. The search dialog now displays with the entire dialog displaying all black. I am unable to close the dialog without closing the entire application. This was working with previous versions of wine. E-sword is a free download from: http://www.e-sword.net Steps to reproduce: * Open the application * Click Bible->Search from the main menu. Expected behavior: * The dialog displays properly with the ability to enter search terms. Actual behavior: * The dialog is displayed with a black box covering all of the contents of the window. -- 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 2

[Bug 41072] New: GOG Galaxy fails to start without setting ucrtbase to ( native, builtin)
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=41072 Bug ID: 41072 Summary: GOG Galaxy fails to start without setting ucrtbase to (native, builtin) Product: Wine Version: 1.9.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jaimerave(a)gmail.com Distribution: --- Trying to start GOG Galaxy without any overwrite fails if ucrtbase is not set to (native, builtin). This is on wine-1.9.15-272-g0b49495 and macOS Sierra. This is what the log shows: fixme:heap:RtlSetHeapInformation 0x110000 0 0x32fbe0 4 stub fixme:vcruntime:__telemetry_main_invoke_trigger (0x3c0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb10000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb80000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x980000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x7e0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xba0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x330000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xc00000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xd10000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xf50000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xee0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x1080000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x11c0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x1050000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x1000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x67000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x1210000) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x32f8b8, 0x32f8c8 0x32f8bc fixme:nls:get_dummy_preferred_ui_language (0x38 0x32f8b8 0x32f8c8 0x32f8bc) returning a dummy value (current locale) err:msvcrt:MSVCRT__invalid_parameter (null):0 (null): (null) 0 fixme:vcruntime:__telemetry_main_return_trigger (0x1210000) err:module:attach_process_dlls "mfc140u.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\GalaxyClient\\GalaxyClient.exe" failed, status c0000417 -- 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 36850] New: Fury 3 does not recognize Gamepad/Joystick
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=36850 Bug ID: 36850 Summary: Fury 3 does not recognize Gamepad/Joystick Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: schmatzler(a)googlemail.com I tried running the demo of Fury 3 which runs fine, but it doesn't recognize any gamepads. I have an old Xbox 1 gamepad which works pretty well. When I plug it in, I get /dev/input/js0 and a /dev/input/event device. I can also see the gamepad in "wine control" and it works in other games. A full debug log is here (too big to attach): http://schmatzler.de/debuglog.tar.bz2 In the log I went into the options and chose to calibrate a Joystick where it asks me to press a button on the controller, but doesn't recognize it. A demo of the game can be found here: ftp://ftp.microsoft.com/deskapps/games/public/Fury3/FURY3X.ZIP -- 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 41074] New: Unimplemented function msvcp140.dll.__crtInitializeCriticalSectionEx needed by Battle.net
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=41074 Bug ID: 41074 Summary: Unimplemented function msvcp140.dll.__crtInitializeCriticalSectionEx needed by Battle.net Product: Wine Version: 1.9.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: audiger(a)live.fr Distribution: --- Tested after applying 4 patches on master: https://source.winehq.org/patches/data/125205 https://source.winehq.org/patches/data/125206 https://source.winehq.org/patches/data/125204 https://source.winehq.org/patches/data/125209 When Battle.net is installing crashed with this issue: wine: Call from 0x7b43bfac to unimplemented function msvcp140.dll.__crtInitializeCriticalSectionEx, aborting wine: Unimplemented function msvcp140.dll.__crtInitializeCriticalSectionEx called at address 0x7b43bfac (thread 00c6), starting debugger... -- 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 41140] New: gcc6: comctl32 build warnings
by wine-bugs＠winehq.org Aug. 19, 2016

Aug. 19, 2016

https://bugs.winehq.org/show_bug.cgi?id=41140 Bug ID: 41140 Summary: gcc6: comctl32 build warnings Product: Wine Version: 1.9.16 Hardware: x86 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: wylda(a)volny.cz Distribution: --- Created attachment 55346 --> https://bugs.winehq.org/attachment.cgi?id=55346 comctl32/listview.c log With Debian's gcc update, new warnings appeared. -- 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 2