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

[Bug 15883] New: When the Linux version of SDL_mixer is installed, programs in Qb64 fail to compile (c++ compilation failed).
by wine-bugs＠winehq.org Feb. 18, 2019

Feb. 18, 2019

http://bugs.winehq.org/show_bug.cgi?id=15883 Summary: When the Linux version of SDL_mixer is installed, programs in Qb64 fail to compile (c++ compilation failed). Product: Wine Version: 1.1.7 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: samanddeanus(a)yahoo.com When the Linux version of SDL_mixer is installed, programs in Qb64 fail to compile (c++ compilation failed). -- 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 16

[Bug 37965] New: Dead Space 3 sometimes fails to load checkpoints that are not save points
by wine-bugs＠winehq.org Feb. 17, 2019

Feb. 17, 2019

https://bugs.winehq.org/show_bug.cgi?id=37965 Bug ID: 37965 Summary: Dead Space 3 sometimes fails to load checkpoints that are not save points Product: Wine Version: 1.7.35 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Dead Space 3 autosaves the game, and there is no manual save option. While checkpoints in the game are frequent, save points only occur every few checkpoints. In theory, this means your character can die at any time without major consequence. However quitting the game and loading it again may involve replaying maybe 10+ minutes depending specifically where the death occurred. Unfortunately, it seems that death in areas where the previous checkpoint was not a save point causes the checkpoint to fail loading properly - resulting in an instant death before the game even draws your character to the screen. This results in a death/respawn loop that only ends when you bring up the in-game main menu and select the option to exit the game, losing progress in the process. It is also noteworthy that the mouse cursor disappears from the game menu until the option to end the current game is selected - presumably another side-effect of the aforementioned bug. Re-loading the most recent save point gets the game running normally again (until the next time it is triggered). There is a video posted of this behaviour here: https://www.youtube.com/watch?v=KDWbnrcx4Gc While this behaviour was not reported in the Dead Space 3 AppDB entries, I suspect this is the sort of thing that can easily go unnoticed without a complete playthrough under Wine (which I just did) - particularly since I don't think I even died during the first half of the game. I first encountered this in Chapter 13, but it could be an issue in other chapters. I vaguely recall seeing it later in the game somewhere. The game was cracked to work around what I suspect is a variant of bug #34517 (only without an alternative work-around here). To rule out the crack being the issue causing this behaviour, I copied the entire game directory and my save game to a real Windows installation, where the bug could not be reproduced. Observed on 1.7.35 with 8e9e4a6 reverted due to it producing a regression (which I'll report separately momentarily). -- 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 34080] New: Half-life 2 : Ammo doesn't display when loading game
by wine-bugs＠winehq.org Feb. 17, 2019

Feb. 17, 2019

http://bugs.winehq.org/show_bug.cgi?id=34080 Bug #: 34080 Summary: Half-life 2 : Ammo doesn't display when loading game Product: Wine Version: 1.6-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: scrimekiler(a)yahoo.fr Classification: Unclassified Created attachment 45307 --> http://bugs.winehq.org/attachment.cgi?id=45307 loaded game showing the bug When I load a game, I can't see how much ammo is left on a weapon. A workaround : changing video mode fullscreen/windowed then going back to the previous one and then ammo display correctly. -- 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 6

[Bug 36382] New: valgrind shows a possible leak in in ddraw/tests/ddraw7.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36382 Bug ID: 36382 Summary: valgrind shows a possible leak in in ddraw/tests/ddraw7.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 ==5480== 28 bytes in 1 blocks are possibly lost in loss record 259 of 953 ==5480== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5480== by 0x61B3BE8: apartment_getclassobject (compobj.c:526) ==5480== by 0x61B6FF6: get_inproc_class_object (compobj.c:2894) ==5480== by 0x61B9D5F: CoGetClassObject (compobj.c:3032) ==5480== by 0x61BA4E7: CoCreateInstance (compobj.c:3197) ==5480== by 0x515764C: func_ddraw7 (ddraw7.c:2911) ==5480== by 0x50CC30B: main (test.h:584) ==5480== -- 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 36381] New: valgrind shows a couple possible leaks in in ddraw/tests/ddraw2.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36381 Bug ID: 36381 Summary: valgrind shows a couple possible leaks 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 ==5342== 28 bytes in 1 blocks are possibly lost in loss record 255 of 1,003 ==5342== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5342== by 0x6288BE8: apartment_getclassobject (compobj.c:526) ==5342== by 0x628BFF6: get_inproc_class_object (compobj.c:2894) ==5342== by 0x628ED5F: CoGetClassObject (compobj.c:3032) ==5342== by 0x628F4E7: CoCreateInstance (compobj.c:3197) ==5342== by 0x51134ED: func_ddraw2 (ddraw2.c:3061) ==5342== by 0x50CC30B: main (test.h:584) ==5342== ==5342== 92 bytes in 1 blocks are possibly lost in loss record 515 of 1,003 ==5342== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5342== by 0x4ABE069: d3d3_CreateViewport (ddraw.c:3941) ==5342== by 0x4ABE1EE: d3d2_CreateViewport (ddraw.c:3962) ==5342== by 0x510969B: create_viewport.constprop.3 (ddraw2.c:268) ==5342== by 0x510B50F: test_lighting_interface_versions (ddraw2.c:3407) ==5342== by 0x5113DEB: func_ddraw2 (ddraw2.c:6421) ==5342== by 0x50CC30B: main (test.h:584) ==5342== -- 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 36349] New: valgrind shows a few leaks in d3d9/tests/stateblock.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36349 Bug ID: 36349 Summary: valgrind shows a few leaks in d3d9/tests/stateblock.c Product: Wine Version: 1.7.17 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 ==4967== 148 bytes in 1 blocks are possibly lost in loss record 548 of 819 ==4967== at 0x40087BA: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==4967== by 0x72216AF: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==4967== by 0x721C294: drm_intel_bo_alloc (in /usr/lib/libdrm_intel.so.1.0.0) ==4967== by 0x6F2A251: ??? (in /usr/lib/dri/i965_dri.so) ==4967== by 0x6F2A84B: ??? (in /usr/lib/dri/i965_dri.so) ==4967== by 0x6F5F6DB: ??? (in /usr/lib/dri/i965_dri.so) ==4967== by 0x6EEE9B4: ??? (in /usr/lib/dri/i965_dri.so) ==4967== by 0x6918B9B: ??? (in /usr/lib/libGL.so.1.2.0) ==4967== by 0x68E82F4: ??? (in /usr/lib/libGL.so.1.2.0) ==4967== by 0x6034DF2: create_glxcontext.isra.0 (opengl.c:1254) ==4967== by 0x6035127: X11DRV_wglCreateContextAttribsARB (opengl.c:2071) ==4967== by 0x5459C29: wglCreateContextAttribsARB (wgl.c:268) ==4967== by 0x4FB39D8: context_create (context.c:1543) ==4967== by 0x5049866: wined3d_swapchain_create (swapchain.c:914) ==4967== by 0x4F58F1F: d3d9_swapchain_create (swapchain.c:333) ==4967== by 0x4F53348: d3d9_device_CreateAdditionalSwapChain (device.c:504) ==4967== by 0x4A878DC: switch_render_target (stateblock.c:187) ==4967== by 0x4A89C94: execute_test_chain (stateblock.c:141) ==4967== by 0x4A8A9BE: test_state_management (stateblock.c:457) ==4967== by 0x4ADCD4C: run_test (test.h:584) ==4967== -- 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 38021] New: ntdll:load_dll doesn't check for correct dll ARCH
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=38021 Bug ID: 38021 Summary: ntdll:load_dll doesn't check for correct dll ARCH Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: patrick1804(a)web.de Distribution: --- Problem 1: ntdll:load_dll doesn't check if the found DLL has the wrong arch. For example: 64bit application want's to load xinput1_3.dll. There's a 32bit xinput1_3.dll in the same folder. Expected behavior: It should ignore this dll, instead of trying to open it. Problem 2: ntdll:load_dll doesn't check other locations for this DLL once a matching one has been found, even when it has the wrong arch and couldn't be loaded. For example: 64bit application want's to load xinput1_3.dll. There's a 32bit xinput1_3.dll in the same folder. It tries to open the file and fails. It doesn't check other folders like System32. The application doesn't start. Expected behavior: load_dll looks for 64bit xinput1_3.dll in system32 and starts. -- 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 18

[Bug 36267] New: valgrind shows an invalid read in ddraw/tests/ddraw4.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36267 Bug ID: 36267 Summary: valgrind shows an invalid read in ddraw/tests/ddraw4.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 ==4973== Invalid read of size 4 ==4973== at 0x50CE7C7: update_heap_entry (glsl_shader.c:905) ==4973== by 0x50CE900: shader_glsl_update_float_vertex_constants (glsl_shader.c:939) ==4973== by 0x50AAEEE: wined3d_device_set_vs_consts_f (device.c:2297) ==4973== by 0x5137052: wined3d_stateblock_apply (stateblock.c:957) ==4973== by 0x498F1ED: ddraw_set_cooperative_level (ddraw.c:951) ==4973== by 0x498F69F: ddraw4_SetCooperativeLevel (ddraw.c:1019) ==4973== by 0x4CA8A97: test_coop_level_create_device_window (ddraw4.c:678) ==4973== by 0x4CCC1E5: func_ddraw4 (ddraw4.c:7300) ==4973== by 0x4D1E890: run_test (test.h:584) ==4973== by 0x4D1EC7F: main (test.h:654) ==4973== Address 0xb458000 is 42,896 bytes inside a block of size 65,544 alloc'd ==4973== at 0x7BC4C735: notify_alloc (heap.c:255) ==4973== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==4973== by 0x50DF534: constant_heap_init (glsl_shader.c:6409) ==4973== by 0x50DF8FB: shader_glsl_alloc (glsl_shader.c:6478) ==4973== by 0x50A5691: wined3d_device_init_3d (device.c:882) ==4973== by 0x498E381: ddraw_attach_d3d_device (ddraw.c:591) ==4973== by 0x498E5B9: ddraw_create_swapchain (ddraw.c:634) ==4973== by 0x498F124: ddraw_set_cooperative_level (ddraw.c:934) ==4973== by 0x498F69F: ddraw4_SetCooperativeLevel (ddraw.c:1019) ==4973== by 0x4CA8A97: test_coop_level_create_device_window (ddraw4.c:678) ==4973== by 0x4CCC1E5: func_ddraw4 (ddraw4.c:7300) ==4973== by 0x4D1E890: run_test (test.h:584) ==4973== by 0x4D1EC7F: main (test.h:654) ==4973== -- 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 36261] New: valgrind shows a use after free in ddraw/tests/ddraw4.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36261 Bug ID: 36261 Summary: valgrind shows a use after free in ddraw/tests/ddraw4.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 ==29500== Invalid write of size 4 ==29500== at 0x498B288: d3d_device_inner_Release (device.c:319) ==29500== by 0x498B45B: d3d_device3_Release (device.c:345) ==29500== by 0x4C6844D: test_process_vertices (ddraw4.c:624) ==29500== by 0x4C8C1E0: func_ddraw4 (ddraw4.c:7299) ==29500== by 0x4CDE890: run_test (test.h:584) ==29500== by 0x4CDEC7F: main (test.h:654) ==29500== Address 0x47a4dc8 is 112 bytes inside a block of size 160 free'd ==29500== at 0x7BC4C782: notify_free (heap.c:263) ==29500== by 0x7BC510C7: RtlFreeHeap (heap.c:1762) ==29500== by 0x497D9F9: ddraw_destroy (ddraw.c:441) ==29500== by 0x497DC0C: ddraw4_Release (ddraw.c:472) ==29500== by 0x49A3B99: ddraw_surface_release_iface (surface.c:552) ==29500== by 0x49A3D41: ddraw_surface4_Release (surface.c:611) ==29500== by 0x498B229: d3d_device_inner_Release (device.c:316) ==29500== by 0x498B45B: d3d_device3_Release (device.c:345) ==29500== by 0x4C6844D: test_process_vertices (ddraw4.c:624) ==29500== by 0x4C8C1E0: func_ddraw4 (ddraw4.c:7299) ==29500== by 0x4CDE890: run_test (test.h:584) ==29500== by 0x4CDEC7F: main (test.h:654) ==29500== -- 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 36348] New: valgrind shows a couple leaks in d3d9/tests/d3d9ex.c
by wine-bugs＠winehq.org Feb. 15, 2019

Feb. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=36348 Bug ID: 36348 Summary: valgrind shows a couple leaks in d3d9/tests/d3d9ex.c Product: Wine Version: 1.7.17 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 ==3976== 16 bytes in 1 blocks are definitely lost in loss record 396 of 1,973 ==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==3976== by 0x4F58C13: Direct3DCreate9Ex (d3d9_main.c:63) ==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59) ==3976== by 0x4A55992: test_reset (d3d9ex.c:684) ==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218) ==3976== by 0x4ADCD4C: run_test (test.h:584) ==3976== by 0x4ADD13B: main (test.h:654) ==3976== ==3976== 12,068 bytes in 1 blocks are definitely lost in loss record 1,915 of 1,973 ==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==3976== by 0x506F901: wined3d_create (wined3d_main.c:95) ==3976== by 0x4F654AE: d3d9_init (directx.c:647) ==3976== by 0x4F58C30: Direct3DCreate9Ex (d3d9_main.c:66) ==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59) ==3976== by 0x4A55992: test_reset (d3d9ex.c:684) ==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218) ==3976== by 0x4ADCD4C: run_test (test.h:584) ==3976== by 0x4ADD13B: main (test.h:654) ==3976== -- 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