January 2017 - Wine-Bugs - list.winehq.org

[Bug 42014] New: wine refuses BOSE Soundtouch
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=42014 Bug ID: 42014 Summary: wine refuses BOSE Soundtouch Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Rainwine(a)orbitcomputer.de Distribution: Mint Created attachment 56459 --> https://bugs.winehq.org/attachment.cgi?id=56459 wine backtrace file BOSE -- 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 36

[Bug 42015] New: wine refuses to run BOSE Soundtouch
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=42015 Bug ID: 42015 Summary: wine refuses to run BOSE Soundtouch Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Rainwine(a)orbitcomputer.de Distribution: Mint BOSE Soundtouch does not run, because wine has problems with Qt? -- 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 5

[Bug 36169] New: valgrind shows a possible leak in programs/services/tests/services.c
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=36169 Bug ID: 36169 Summary: valgrind shows a possible leak in programs/services/tests/services.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==3856== 32 bytes in 1 blocks are possibly lost in loss record 32 of 104 ==3856== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==3856== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==3856== by 0x7BC39A6B: RtlInitializeCriticalSectionEx (critsection.c:326) ==3856== by 0x7B876AE5: InitializeCriticalSectionEx (sync.c:356) ==3856== by 0x7B876A64: InitializeCriticalSection (sync.c:313) ==3856== by 0x4A34B0E: test_runner (service.c:445) ==3856== by 0x4A34DAD: func_service (service.c:484) ==3856== by 0x4A35C5D: run_test (test.h:584) ==3856== by 0x4A3604B: main (test.h:654) ==3856== -- 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 2

[Bug 36570] New: valgrind shows a couple possible leaks in rpcrt4/tests/rpc_protseq.c
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=36570 Bug ID: 36570 Summary: valgrind shows a couple possible leaks in rpcrt4/tests/rpc_protseq.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==10120== 64 bytes in 1 blocks are possibly lost in loss record 122 of 242 ==10120== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==10120== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==10120== by 0x55FF1FF: rpcrt4_protseq_np_alloc (rpc_transport.c:642) ==10120== by 0x55FB2EA: alloc_serverprotoseq (rpc_server.c:927) ==10120== by 0x55FB594: RPCRT4_get_or_create_serverprotseq (rpc_server.c:977) ==10120== by 0x55FB89F: RpcServerUseProtseqA (rpc_server.c:1041) ==10120== by 0x4CB910E: test_RpcServerUseProtseq (rpc_protseq.c:64) ==10120== by 0x4CB9ABB: func_rpc_protseq (rpc_protseq.c:202) ==10120== by 0x4CE2071: run_test (test.h:584) ==10120== by 0x4CE2460: main (test.h:654) ==10120== ==10120== 68 bytes in 1 blocks are possibly lost in loss record 126 of 242 ==10120== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==10120== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==10120== by 0x560163E: rpcrt4_protseq_sock_alloc (rpc_transport.c:1554) ==10120== by 0x55FB2EA: alloc_serverprotoseq (rpc_server.c:927) ==10120== by 0x55FB594: RPCRT4_get_or_create_serverprotseq (rpc_server.c:977) ==10120== by 0x55FB89F: RpcServerUseProtseqA (rpc_server.c:1041) ==10120== by 0x4CB91A4: test_RpcServerUseProtseq (rpc_protseq.c:71) ==10120== by 0x4CB9ABB: func_rpc_protseq (rpc_protseq.c:202) ==10120== by 0x4CE2071: run_test (test.h:584) ==10120== by 0x4CE2460: main (test.h:654) ==10120== -- 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 5

[Bug 36145] New: valgrind shows several leaks in imm32/tests/imm32.c
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=36145 Bug ID: 36145 Summary: valgrind shows several leaks in imm32/tests/imm32.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: imm32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==32120== 180 bytes in 1 blocks are definitely lost in loss record 621 of 863 ==32120== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==32120== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==32120== by 0x5021822: create_window_handle (win.c:227) ==32120== by 0x5025308: WIN_CreateWindowEx (win.c:1450) ==32120== by 0x50261E8: CreateWindowExA (win.c:1719) ==32120== by 0x4A3468E: ImmGetContextThreadFunc (imm32.c:429) ==32120== by 0x7BC87017: ??? (signal_i386.c:2571) ==32120== by 0x7BC87060: call_thread_func (signal_i386.c:2630) ==32120== by 0x7BC86FF5: ??? (signal_i386.c:2571) ==32120== by 0x7BC8E43C: start_thread (thread.c:428) ==32120== by 0x4218F92: start_thread (pthread_create.c:309) ==32120== by 0x431D7ED: clone (clone.S:129) ==32120== 152 bytes in 1 blocks are definitely lost in loss record 609 of 863 ==32120== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==32120== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==32120== by 0x7B8457FF: HeapAlloc (heap.c:271) ==32120== by 0x7B845B34: GlobalAlloc (heap.c:388) ==32120== by 0x4F5C176: ImmCreateIMCC (imm.c:2738) ==32120== by 0x4F55986: ImmCreateContext (imm.c:682) ==32120== by 0x4F57F63: ImmGetContext (imm.c:1422) ==32120== by 0x4A346A4: ImmGetContextThreadFunc (imm32.c:433) ==32120== by 0x7BC87017: ??? (signal_i386.c:2571) ==32120== by 0x7BC87060: call_thread_func (signal_i386.c:2630) ==32120== by 0x7BC86FF5: ??? (signal_i386.c:2571) ==32120== by 0x7BC8E43C: start_thread (thread.c:428) ==32120== by 0x4218F92: start_thread (pthread_create.c:309) ==32120== by 0x431D7ED: clone (clone.S:129) ==32120== ==32448== 20 bytes in 1 blocks are definitely lost in loss record 198 of 861 ==32448== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==32448== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==32448== by 0x7B8457FF: HeapAlloc (heap.c:271) ==32448== by 0x7B846650: GlobalReAlloc (heap.c:693) ==32448== by 0x4F7C25A: ImmReSizeIMCC (imm.c:2778) ==32448== by 0x5BCEC73: GenerateIMEMessage (ime.c:474) ==32448== by 0x5BD06C2: ImeSetCompositionString (ime.c:899) ==32448== by 0x4F7AAC6: ImmSetCompositionStringW (imm.c:2293) ==32448== by 0x4F7A925: ImmSetCompositionStringA (imm.c:2255) ==32448== by 0x4E4D99D: test_ImmNotifyIME (imm32.c:257) ==32448== by 0x4E541EB: func_imm32 (imm32.c:1409) ==32448== by 0x4E5507D: run_test (test.h:584) ==32448== by 0x4E5546B: main (test.h:654) ==32448== -- 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 4

[Bug 36401] New: valgrind shows an unitialized variable in dxgi/factory.c (dxgi/tests/device.c)
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=36401 Bug ID: 36401 Summary: valgrind shows an unitialized variable in dxgi/factory.c (dxgi/tests/device.c) Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==21110== Conditional jump or move depends on uninitialised value(s) ==21110== at 0x5168715: wined3d_swapchain_decref (swapchain.c:75) ==21110== by 0x50E7568: wined3d_device_uninit_3d (device.c:1090) ==21110== by 0x5083655: dxgi_swapchain_Release (swapchain.c:82) ==21110== by 0x4A97019: func_device (dxgi.h:1733) ==21110== by 0x4A98EEA: run_test (test.h:584) ==21110== by 0x4A94C3E: main (test.h:654) ==21110== Uninitialised value was created by a stack allocation ==21110== at 0x507FF5C: dxgi_factory_CreateSwapChain (factory.c:186) ==21110== dxgi/tests/device.c -- 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 5

[Bug 28745] New: dsound/tests: uninitialized value used in enum_callback() in func_propset()
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

http://bugs.winehq.org/show_bug.cgi?id=28745 Bug #: 28745 Summary: dsound/tests: uninitialized value used in enum_callback() in func_propset() Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-dsound AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Running "make propset.ok" in dsound/tests, valgrind complains: Conditional jump or move depends on uninitialised value(s) at callback (propset.c:69) by DSPROPERTY_enumWtoA (propset.c:396) by enum_callback (propset.c:306) by enumerate_mmdevices (dsound_main.c:555) by DSPROPERTY_EnumerateW (propset.c:334) by IKsPrivatePropertySetImpl_Get (propset.c:419) by func_propset (propset.c:458) by run_test (test.h:556) by main (test.h:624) Uninitialised value was created by a stack allocation at enum_callback (propset.c:282) I haven't bisected, but lots of the related code is new, from: commit 8856ea79f3468d6f532f5f20e9b28c295d6e1db1 Author: Andrew Eikum <aeikum(a)codeweavers.com> Date: Tue Sep 27 08:51:33 2011 -0500 dsound: Reimplement PropertySet on mmdevapi. -- 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 4

[Bug 39956] New: dlls/urlmon/tests/uri.c fails a lot of tests
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=39956 Bug ID: 39956 Summary: dlls/urlmon/tests/uri.c fails a lot of tests Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: dev.anshuman73(a)gmail.com Hi, I was running the WineTests on Windows 10, Build 1511, November fix. Uri.c gives a lot of errors as described in this paste - http://pastebin.com/X7fR1Bvx I ran the winetest from http://test.winehq.org/ and downloaded the test as of 8 January (Version 4 Tests from build d7e4193df2f22a87031e44ce358a626a5f92b295) -- 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 4

[Bug 28216] New: shell32/shlfolder.c test always fails on ubuntu 10.04?
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

http://bugs.winehq.org/show_bug.cgi?id=28216 Summary: shell32/shlfolder.c test always fails on ubuntu 10.04? Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com (Not quite the same as bug 27729.) shell32/shlfolder.ok succeeds for me on my ubuntu 11.04 boxes, but always fails for me on my one ubuntu 10.04 box, even after I do 'apt-get install gettext' to get past non bug 28208. Log shows: ../../../tools/runtest -q -P wine -M shell32.dll -T ../../.. -p shell32_test.exe.so shlfolder.c && touch shlfolder.ok fixme:shdocvw:IEParseDisplayNameWithBCW stub: 0x0 L"http:\\yyy" (nil) 0x32fc78 fixme:shdocvw:IEParseDisplayNameWithBCW stub: 0x0 L"xx:yyy" (nil) 0x32fc78 err:shell:HCR_GetFolderAttributes should be called for simple PIDL's only! shlfolder.c:2386: Test failed: SHCreateItemFromParsingName returned 0 The test creates the file c:/users/dank/Desktop/testfile, then looks for it with some arcane shell folder API, and is unhappy when it actually finds the file. +shell,+file trace attached. The test function in question is test_SHCreateShellItem(). I can make the test succeed by inserting the line SetCurrentDirectoryA("c:\\"); at the top of the function, or by editing test_ITEMIDLIST_format() and inserting a return before it calls SetCurrentDirectoryW(). So there seems to be something fragile in the shlfolder tests with respect to the current directory. No idea why this only shows up on ubuntu 10.04 (on my i7 test box). -- 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 4

[Bug 36654] New: valgrind shows invalid read/write in d3d8/tests/device.c
by wine-bugs＠winehq.org July 5, 2021

July 5, 2021

https://bugs.winehq.org/show_bug.cgi?id=36654 Bug ID: 36654 Summary: valgrind shows invalid read/write in d3d8/tests/device.c Product: Wine Version: 1.3.30 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==6361== Invalid read of size 4 ==6361== at 0x5E0EB00: ??? (in /tmp/.glZDO9Wy (deleted)) ==6361== by 0x5160AE4: fixup_extensions (directx.c:1542) ==6361== by 0x5166F86: wined3d_adapter_init_gl_caps (directx.c:3131) ==6361== by 0x516C459: wined3d_adapter_init (directx.c:5180) ==6361== by 0x516C9B2: wined3d_init (directx.c:5272) ==6361== by 0x5215953: wined3d_create (wined3d_main.c:105) ==6361== by 0x50E0716: d3d8_init (directx.c:413) ==6361== by 0x50D47D2: Direct3DCreate8 (d3d8_main.c:47) ==6361== by 0x4F6AD2A: test_device_window_reset (device.c:2982) ==6361== by 0x4F7D127: func_device (device.c:6224) ==6361== by 0x4F9EC1E: run_test (test.h:584) ==6361== by 0x4F9F00D: main (test.h:654) ==6361== Address 0xe92a7c0 is on thread 1's stack ==6361== ==6361== Invalid write of size 4 ==6361== at 0x5E0EB0D: ??? (in /tmp/.glZDO9Wy (deleted)) ==6361== by 0x5160AE4: fixup_extensions (directx.c:1542) ==6361== by 0x5166F86: wined3d_adapter_init_gl_caps (directx.c:3131) ==6361== by 0x516C459: wined3d_adapter_init (directx.c:5180) ==6361== by 0x516C9B2: wined3d_init (directx.c:5272) ==6361== by 0x5215953: wined3d_create (wined3d_main.c:105) ==6361== by 0x50E0716: d3d8_init (directx.c:413) ==6361== by 0x50D47D2: Direct3DCreate8 (d3d8_main.c:47) ==6361== by 0x4F6AD2A: test_device_window_reset (device.c:2982) ==6361== by 0x4F7D127: func_device (device.c:6224) ==6361== by 0x4F9EC1E: run_test (test.h:584) ==6361== by 0x4F9F00D: main (test.h:654) ==6361== Address 0xaaaaaaaa is on thread 1's stack ==6361== OpenGL renderer string: GeForce GTX 460/PCIe/SSE2 OpenGL core profile version string: 4.3.0 NVIDIA 337.25 -- 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 3