wine-bugs February 2019

wine-bugs@winehq.org

1 participants
7599 discussions

[Bug 46208] New: Elite Dangerous is unstable in wine-devel
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46208 Bug ID: 46208 Summary: Elite Dangerous is unstable in wine-devel Product: Wine Version: 3.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: brendan(a)redmandi.com Distribution: --- When using wine-devel v3.21, Elite Dangerous is unstable and will usually freeze before finishing the opening video (but will sometimes get as far as shader compilation). When attaching a debugger, it looks like all processes are waiting for an event. The program needs to be killed with a 'kill -9'. The workaround is to run Elite with 'taskset -c 0', but it also appears to progress further if you run with 'WINEDEBUG=+relay'. This leads me to believe the issue is one of timing (as opposed to multi-threading). When using wine-staging v3.21, Elite has no such problems and runs perfectly. A git bi-sect led me to find that the reason for this was a single patch: https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-fute… Applying just this patch to wine-devel v3.21 results in the game running 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 21

[Bug 46618] New: Far Cry v1.40 locks up when changing screen resolution or anti-aliasing level
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46618 Bug ID: 46618 Summary: Far Cry v1.40 locks up when changing screen resolution or anti-aliasing level Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: cc88fb0b691efd771cf43045dccbe9c5b7bc9993 Distribution: --- Created attachment 63520 --> https://bugs.winehq.org/attachment.cgi?id=63520 plain terminal output Just like with bug #46617, I tested this bug with the GOG.com version. Unable to reproduce with the demo version. The game freezes with high CPU usage when I'm trying to change screen resolution or anti-aliasing level in the Video Options menu. According to my testing this was caused by commit cc88fb0b691efd771cf43045dccbe9c5b7bc9993 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Wed Feb 6 19:38:25 2019 -0600 wined3d: Store the index buffer in the wined3d_stateblock_state structure. The patch can't be reverted cleanly, but the problem doesn't exist with the previous commit. wine-4.1-108-gf7b3120991 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 415.22.05 -- 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 36201] New: valgrind shows a definite leak under crypt32/tests/store.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36201 Bug ID: 36201 Summary: valgrind shows a definite leak under crypt32/tests/store.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48322 --> https://bugs.winehq.org/attachment.cgi?id=48322 valgrind log ==18714== 48 bytes in 1 blocks are definitely lost in loss record 215 of 443 ==18714== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==18714== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==18714== by 0x514398B: CryptMemAlloc (main.c:124) ==18714== by 0x511E5A6: Context_CreateLinkContext (context.c:60) ==18714== by 0x510AB00: Cert_clone (cert.c:127) ==18714== by 0x511D199: CRYPT_CollectionCreateContextFromChild (collectionstore.c:85) ==18714== by 0x511D5C9: Collection_addCert (collectionstore.c:215) ==18714== by 0x510B119: add_cert_to_store (cert.c:263) ==18714== by 0x510B27F: CertAddCertificateContextToStore (cert.c:287) ==18714== by 0x510A852: CertAddEncodedCertificateToStore (cert.c:65) ==18714== by 0x4EA953F: testCollectionStore (store.c:670) ==18714== by 0x4EB2BF4: func_store (store.c:2790) ==18714== by 0x4EB7F67: run_test (test.h:584) ==18714== by 0x4EB8356: main (test.h:654) ==18714== and several potential leaks, e.g.,: ==18714== 20 bytes in 1 blocks are possibly lost in loss record 53 of 443 ==18714== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==18714== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==18714== by 0x514398B: CryptMemAlloc (main.c:124) ==18714== by 0x511E0A9: CertAddStoreToCollection (collectionstore.c:519) ==18714== by 0x5164B4B: CRYPT_SysOpenStoreW (store.c:592) ==18714== by 0x5164D74: CRYPT_SysOpenStoreA (store.c:644) ==18714== by 0x5165ADF: CertOpenStore (store.c:907) ==18714== by 0x5165B53: CertOpenSystemStoreA (store.c:919) ==18714== by 0x4EA9419: testCollectionStore (store.c:658) ==18714== by 0x4EB2BF4: func_store (store.c:2790) ==18714== by 0x4EB7F67: run_test (test.h:584) ==18714== by 0x4EB8356: main (test.h:654) ==18714== full log attached -- 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 17913] New: Port royale: black hole instead ocean
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=17913 Summary: Port royale: black hole instead ocean Product: Wine Version: 1.1.18 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: puciek(a)gmail.com Created an attachment (id=20239) --> (http://bugs.winehq.org/attachment.cgi?id=20239) Here should be ocean While playing port royale, and enter "global" mode, instead ocean there is only black color. -- 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 32

[Bug 45524] New: Add a futex-based implementation of condition variables
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=45524 Bug ID: 45524 Summary: Add a futex-based implementation of condition variables 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: --- Created attachment 61910 --> https://bugs.winehq.org/attachment.cgi?id=61910 [PATCH] ntdll: Add a futex-based condition variable implementation. Titanfall 2 has reportedly high wineserver overhead, and this seems to help with that. -- 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 36631] New: valgrind shows a definite leak in in ddraw/tests/ddraw2.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36631 Bug ID: 36631 Summary: valgrind shows a definite leak in in ddraw/tests/ddraw2.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==8554== 4,096 bytes in 1 blocks are definitely lost in loss record 931 of 958 ==8554== at 0x70746F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==8554== by 0x7070378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==8554== by 0x6C84DC2: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C86594: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C8CCCD: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6ABB411: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6C8F89E: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6AA4339: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x6AA89E9: ??? (in /usr/lib/dri/i965_dri.so) ==8554== by 0x656BC95: glTexSubImage2D (in /usr/lib/libGL.so.1.2.0) ==8554== by 0x4F3FE80: surface_upload_data (surface.c:1641) ==8554== by 0x4F4D054: surface_load_texture (surface.c:4861) ==8554== by 0x4F4D52E: surface_load_location (surface.c:4954) ==8554== by 0x4F41C25: surface_load (surface.c:2150) ==8554== by 0x4F594DA: texture2d_sub_resource_load (texture.c:730) ==8554== by 0x4F58AE8: wined3d_texture_load (texture.c:539) ==8554== by 0x4E9CEFE: context_apply_blit_state (context.c:2246) ==8554== by 0x4E858D9: arbfp_blit_surface (arb_program_shader.c:7655) ==8554== by 0x4F51910: wined3d_surface_blt (surface.c:6060) ==8554== by 0x4BB146C: ddraw_surface_blt_clipped (surface.c:1387) ==8554== -- 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 36623] New: valgrind shows some leaks in ddraw/tests/ddraw7.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=36623 Bug ID: 36623 Summary: valgrind shows some leaks in ddraw/tests/ddraw7.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com All of the form: ==31752== 20 bytes in 1 blocks are definitely lost in loss record 194 of 1,726 ==31752== at 0x7BC4C75D: notify_alloc (heap.c:255) ==31752== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==31752== by 0x4A75A4B: DirectDrawCreateClipper (ddraw.c:3274) ==31752== by 0x4A75C0D: ddraw7_CreateClipper (ddraw.c:3309) ==31752== by 0x4DA2139: test_clipper_blt (ddraw7.c:710) ==31752== by 0x4DC439D: func_ddraw7 (ddraw7.c:7183) ==31752== by 0x4DF1F84: run_test (test.h:584) ==31752== by 0x4DF2373: main (test.h:654) ==31752== There's a similar issue in ddraw4 in bug 36343. -- 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 35889] New: wine1.6 display fuzzy chinese ttf fonts, but dialog fonts display normal
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=35889 Bug ID: 35889 Summary: wine1.6 display fuzzy chinese ttf fonts, but dialog fonts display normal Product: Wine Version: 1.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gamiljydcome(a)gmail.com Created attachment 47925 --> http://bugs.winehq.org/attachment.cgi?id=47925 fuzzy chinese ttf fonts i am running wine to use tdxw.exe (stock software) for a long time. i installed simsun.ttf to show chinese fonts, before wine 1.5.18 this app disaplay fonts very clearly. but using wine 1.6.x\1.7.x this app display fonts very fuzzy, dialog fonts display normal. my os box is debian7. i have tried disable fontconfig anti-aliasing and wine anti-aliasing, replaced many other ttf fonts, nothing changed. see blow sample photo. how to fix it? -- 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 23

[Bug 46252] New: StarCitizen has bad performance since bugfix on bug #46099
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=46252 Bug ID: 46252 Summary: StarCitizen has bad performance since bugfix on bug #46099 Product: Wine Version: 3.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rawfox(a)freenet.de Distribution: --- Since bug 46099 is fixed, the game has bad performance, fps is 3-5. https://bugs.winehq.org/show_bug.cgi?id=46099 To make the game perform normal, we need these two other patches applied to wine: https://bugs.winehq.org/attachment.cgi?id=62897 and https://bugs.winehq.org/attachment.cgi?id=62902 I dont know mutch about WaitOnAddress and the futex thing in wine, but the game works definitly like a charm with those patches applied. -- 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 23

[Bug 38685] New: valgrind shows an invalid read in d3d9/tests/d3d9ex.c
by wine-bugs＠winehq.org 15 Feb '19

15 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=38685 Bug ID: 38685 Summary: valgrind shows an invalid read in d3d9/tests/d3d9ex.c Product: Wine Version: 1.7.44 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok ==28064== Invalid read of size 2 ==28064== at 0x4F67EB5: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== ==28064== Invalid read of size 2 ==28064== at 0x4F67ECB: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== ==28064== Invalid read of size 2 ==28064== at 0x4F67F45: check_gamma_ramps (dc.c:1340) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Address 0x4720000 is 392 bytes inside a block of size 1,712 alloc'd ==28064== at 0x7BC4A9F1: notify_alloc (heap.c:254) ==28064== by 0x7BC4EC94: RtlAllocateHeap (heap.c:1715) ==28064== by 0x4AC1763: wined3d_swapchain_create (swapchain.c:1064) ==28064== by 0x49AA370: swapchain_init (swapchain.c:337) ==28064== by 0x49AA44D: d3d9_swapchain_create (swapchain.c:362) ==28064== by 0x49A3DA1: device_parent_create_swapchain (device.c:3578) ==28064== by 0x4A17107: wined3d_device_init_3d (device.c:911) ==28064== by 0x49A41D0: device_init (device.c:3696) ==28064== by 0x49A609F: d3d9_CreateDeviceEx (directx.c:573) ==28064== by 0x479AE2A: create_device (d3d9ex.c:183) ==28064== by 0x47A13F5: test_user_memory_getdc (d3d9ex.c:1373) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) ==28064== Potentially causing a valgrind crash: Memcheck: mc_main.c:1000 (get_sec_vbits8): Assertion 'n' failed. Memcheck: get_sec_vbits8: no node for address 0x4720000 (0x472000D) host stacktrace: ==28064== at 0x38030875: show_sched_status_wrk (m_libcassert.c:341) ==28064== by 0x38030981: report_and_quit (m_libcassert.c:413) ==28064== by 0x38030A63: vgPlain_assert_fail (m_libcassert.c:479) ==28064== by 0x3800AF24: get_sec_vbits8 (mc_main.c:1000) ==28064== by 0x3800B2FE: get_vbits8 (mc_main.c:812) ==28064== by 0x3800B2FE: mc_LOADVn_slow (mc_main.c:1368) ==28064== by 0x3800D9FF: mc_LOADV16 (mc_main.c:4601) ==28064== by 0x3800D9FF: vgMemCheck_helperc_LOADV16le (mc_main.c:4634) ==28064== by 0xBB643E1: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 28064) ==28064== at 0x4F67EB5: check_gamma_ramps (dc.c:1335) ==28064== by 0x4F6831B: SetDeviceGammaRamp (dc.c:1405) ==28064== by 0x4ABEE02: wined3d_swapchain_set_gamma_ramp (swapchain.c:255) ==28064== by 0x4ABE091: swapchain_cleanup (swapchain.c:37) ==28064== by 0x4ABE4DB: wined3d_swapchain_decref (swapchain.c:108) ==28064== by 0x4A17BB7: wined3d_device_uninit_3d (device.c:1135) ==28064== by 0x499A3F0: d3d9_device_Release (device.c:307) ==28064== by 0x47A167F: test_user_memory_getdc (d3d9ex.c:1398) ==28064== by 0x47A7338: func_d3d9ex (d3d9ex.c:2927) ==28064== by 0x4833E19: run_test (test.h:584) ==28064== by 0x4834261: main (test.h:666) -- 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

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