wine-bugs July 2014

wine-bugs@winehq.org

1 participants
9889 discussions

[Bug 35957] New: Neverwinter Nights 1.69 crashes on startup since 1.7.16
by wine-bugs＠winehq.org 29 May '15

29 May '15

http://bugs.winehq.org/show_bug.cgi?id=35957 Bug ID: 35957 Summary: Neverwinter Nights 1.69 crashes on startup since 1.7.16 Product: Wine Version: 1.7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: saif1988(a)gmail.com Created attachment 48041 --> http://bugs.winehq.org/attachment.cgi?id=48041 I usually launch .exe files from gnome gui (right click launch with wine) but ehre is the terminal output after running: wine '/ntfsdisk/NeverwinterNights/NWN/game.exe' > nwnwinelog.txt It worked properly in 1.7.15. -- 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 30974] New: No backtrace with Visual C++ 2010 .pdb files in large app; "Unsupported type 1404 in STRUCT field list"
by wine-bugs＠winehq.org 29 May '15

29 May '15

http://bugs.winehq.org/show_bug.cgi?id=30974 Bug #: 30974 Summary: No backtrace with Visual C++ 2010 .pdb files in large app; "Unsupported type 1404 in STRUCT field list" Product: Wine Version: 1.5.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified When trying to get a backtrace from a large proprietary app built with Visual C++ 2010, wine's backtracer issues the errors seen in bug 30973 along with a few more, e.g. fixme:dbghelp_msc:codeview_add_type_struct_field_list Unsupported type 1404 in STRUCT field list fixme:dbghelp_msc:codeview_fetch_type Cannot locate type 103 fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 103 fixme:dbghelp_msc:codeview_snarf S-Udt nullptr_t: couldn't find type 0x103 and fails to generate a useful backtrace. -- 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 5

[Bug 26321] New: Star Wars: Galactic Battlegrounds Clone Campaigns: 1.0x - Exit DataBank will crash game.
by wine-bugs＠winehq.org 29 May '15

29 May '15

http://bugs.winehq.org/show_bug.cgi?id=26321 Summary: Star Wars: Galactic Battlegrounds Clone Campaigns: 1.0x - Exit DataBank will crash game. Product: Wine Version: 1.3.15 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bug.me(a)comcast.net Created an attachment (id=33546) --> (http://bugs.winehq.org/attachment.cgi?id=33546) Log file with err:dplay When you exit DataBank back to the main game menu the game will crash. -- 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 8

[Bug 36379] New: valgrind shows several possible leaks in light tests in ddraw/tests/d3d.c
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36379 Bug ID: 36379 Summary: valgrind shows several possible leaks in light tests in ddraw/tests/d3d.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 ==5234== 164 bytes in 1 blocks are possibly lost in loss record 1,615 of 2,129 ==5234== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5234== by 0x54F90E0: wined3d_device_set_light (device.c:1445) ==5234== by 0x4ACD12B: d3d_device7_SetLight (device.c:5412) ==5234== by 0x4ACD169: d3d_device7_SetLight_FPUSetup (device.c:5420) ==5234== by 0x50D7C81: LightTest (d3d.c:229) ==5234== by 0x50DC309: func_d3d (d3d.c:3945) ==5234== by 0x50CC30B: main (test.h:584) ==5234== ==5234== 164 bytes in 1 blocks are possibly lost in loss record 1,616 of 2,129 ==5234== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==5234== by 0x54F90E0: wined3d_device_set_light (device.c:1445) ==5234== by 0x54F92C4: wined3d_device_set_light_enable (device.c:1596) ==5234== by 0x4AC9BDB: d3d_device7_LightEnable (device.c:6269) ==5234== by 0x4AC9C19: d3d_device7_LightEnable_FPUSetup (device.c:6277) ==5234== by 0x50D7E80: LightTest (d3d.c:260) ==5234== by 0x50DC309: func_d3d (d3d.c:3945) ==5234== by 0x50CC30B: main (test.h:584) ==5234== -- 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 3

[Bug 36592] New: valgrind shows several leaks in wbemprox/tests/query.c
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36592 Bug ID: 36592 Summary: valgrind shows several leaks in wbemprox/tests/query.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==9559== 0 bytes in 1 blocks are definitely lost in loss record 1 of 632 ==9559== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==9559== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==9559== by 0x63D86BA: heap_alloc_zero (wbemprox_private.h:243) ==9559== by 0x63DAC7E: create_signature_columns_and_data (class.c:739) ==9559== by 0x63DB061: create_signature_table (class.c:787) ==9559== by 0x63DB2A9: create_signature (class.c:842) ==9559== by 0x63DB3B9: class_object_GetMethod (class.c:864) ==9559== by 0x4CA354D: test_Win32_Process (wbemcli.h:1932) ==9559== by 0x4CA66E5: func_query (query.c:679) ==9559== by 0x4CA7FC8: run_test (test.h:584) ==9559== by 0x4CA83B7: main (test.h:654) ==9559== ==9559== 16 bytes in 1 blocks are definitely lost in loss record 115 of 632 ==9559== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==9559== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==9559== by 0x63D86BA: heap_alloc_zero (wbemprox_private.h:243) ==9559== by 0x63DAC7E: create_signature_columns_and_data (class.c:739) ==9559== by 0x63DB061: create_signature_table (class.c:787) ==9559== by 0x63DB2A9: create_signature (class.c:842) ==9559== by 0x63DB3B9: class_object_GetMethod (class.c:864) ==9559== by 0x4CA4311: test_StdRegProv (wbemcli.h:1932) ==9559== by 0x4CA66FB: func_query (query.c:681) ==9559== by 0x4CA7FC8: run_test (test.h:584) ==9559== by 0x4CA83B7: main (test.h:654) ==9559== -- 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 36246] New: valgrind shows several warnings in d3dx9_36/tests/xfile.c
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36246 Bug ID: 36246 Summary: valgrind shows several warnings in d3dx9_36/tests/xfile.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==27811== 28 bytes in 1 blocks are definitely lost in loss record 152 of 570 ==27811== at 0x7BC4C735: notify_alloc (heap.c:255) ==27811== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==27811== by 0x511866A: IDirectXFileDataImpl_Create (d3dxof.c:506) ==27811== by 0x511A1AD: IDirectXFileEnumObjectImpl_GetNextDataObject (d3dxof.c:1032) ==27811== by 0x49EAD9A: d3dx9_file_CreateEnumObject (xfile.c:591) ==27811== by 0x4CE674B: test_getname (xfile.c:202) ==27811== by 0x4CE74A3: func_xfile (xfile.c:386) ==27811== by 0x4CE82A0: run_test (test.h:584) ==27811== by 0x4CE868F: main (test.h:654) ==27811== ==27834== 28 bytes in 1 blocks are definitely lost in loss record 150 of 570 ==27834== at 0x7BC4C735: notify_alloc (heap.c:255) ==27834== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==27834== by 0x50F166A: IDirectXFileDataImpl_Create (d3dxof.c:506) ==27834== by 0x50F31AD: IDirectXFileEnumObjectImpl_GetNextDataObject (d3dxof.c:1032) ==27834== by 0x4FB3D9A: d3dx9_file_CreateEnumObject (xfile.c:591) ==27834== by 0x4CA6005: test_lock_unlock (xfile.c:134) ==27834== by 0x4CA749E: func_xfile (xfile.c:385) ==27834== by 0x4CA82A0: run_test (test.h:584) ==27834== by 0x4CA868F: main (test.h:654) ==27834== -- 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 3

[Bug 36244] New: valgrind shows several warnings in d3dx9_36/tests/surface.c
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36244 Bug ID: 36244 Summary: valgrind shows several warnings in d3dx9_36/tests/surface.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==27327== Invalid read of size 4 ==27327== at 0x4FB898B: point_filter_argb_pixels (surface.c:1655) ==27327== by 0x4FB9301: D3DXLoadSurfaceFromMemory (surface.c:1846) ==27327== by 0x4FB73A4: D3DXLoadSurfaceFromFileInMemory (surface.c:1179) ==27327== by 0x4FB7A4A: D3DXLoadSurfaceFromResourceA (surface.c:1290) ==27327== by 0x4C9EC72: test_D3DXLoadSurface (surface.c:668) ==27327== by 0x4CA46AF: func_surface (surface.c:1328) ==27327== by 0x4CB42A0: run_test (test.h:584) ==27327== by 0x4CB468F: main (test.h:654) ==27327== Address 0x4723c60 is 0 bytes inside a recently re-allocated block of size 3 alloc'd ==27327== at 0x7BC4C735: notify_alloc (heap.c:255) ==27327== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==27327== by 0x4FB6FF4: D3DXLoadSurfaceFromFileInMemory (surface.c:1136) ==27327== by 0x4FB7A4A: D3DXLoadSurfaceFromResourceA (surface.c:1290) ==27327== by 0x4C9EC72: test_D3DXLoadSurface (surface.c:668) ==27327== by 0x4CA46AF: func_surface (surface.c:1328) ==27327== by 0x4CB42A0: run_test (test.h:584) ==27327== by 0x4CB468F: main (test.h:654) ==27327== ==27327== 148 bytes in 1 blocks are possibly lost in loss record 564 of 850 ==27327== at 0x40087BA: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==27327== by 0x7ABA6AF: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==27327== by 0x7AB5294: drm_intel_bo_alloc (in /usr/lib/libdrm_intel.so.1.0.0) ==27327== by 0x75C6078: ??? (in /usr/lib/dri/i965_dri.so) ==27327== by 0x75C64E1: ??? (in /usr/lib/dri/i965_dri.so) ==27327== by 0x73422FA: ??? (in /usr/lib/dri/i965_dri.so) ==27327== by 0x70EBBFD: shared_dispatch_stub_462 (in /usr/lib/libglapi.so.0.0.0) ==27327== by 0x5DC9265: surface_prepare_buffer (surface.c:563) ==27327== by 0x5DC9759: surface_prepare_map_memory (surface.c:608) ==27327== by 0x5DD23A9: wined3d_surface_map (surface.c:3049) ==27327== by 0x5CB2B15: d3d9_surface_LockRect (surface.c:269) ==27327== by 0x4FB91B5: D3DXLoadSurfaceFromMemory (surface.c:1831) ==27327== by 0x4FB73A4: D3DXLoadSurfaceFromFileInMemory (surface.c:1179) ==27327== by 0x4FB788A: D3DXLoadSurfaceFromFileW (surface.c:1259) ==27327== by 0x4FB770D: D3DXLoadSurfaceFromFileA (surface.c:1233) ==27327== by 0x4C9E94F: test_D3DXLoadSurface (surface.c:648) ==27327== by 0x4CA46AF: func_surface (surface.c:1328) ==27327== by 0x4CB42A0: run_test (test.h:584) ==27327== by 0x4CB468F: main (test.h:654) ==27327== ==27405== 327,680 bytes in 1 blocks are definitely lost in loss record 848 of 850 ==27405== at 0x7AAA6F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0) ==27405== by 0x7AA6378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0) ==27405== by 0x75B7114: ??? (in /usr/lib/dri/i965_dri.so) ==27405== by 0x7333D3E: ??? (in /usr/lib/dri/i965_dri.so) ==27405== by 0x70EBFAD: shared_dispatch_stub_477 (in /usr/lib/libglapi.so.0.0.0) ==27405== by 0x5DD257F: wined3d_surface_map (surface.c:3086) ==27405== by 0x5CB2B15: d3d9_surface_LockRect (surface.c:269) ==27405== by 0x4FA91B5: D3DXLoadSurfaceFromMemory (surface.c:1831) ==27405== by 0x4FA73A4: D3DXLoadSurfaceFromFileInMemory (surface.c:1179) ==27405== by 0x4FA788A: D3DXLoadSurfaceFromFileW (surface.c:1259) ==27405== by 0x4FA770D: D3DXLoadSurfaceFromFileA (surface.c:1233) ==27405== by 0x4C9294F: test_D3DXLoadSurface (surface.c:648) ==27405== by 0x4C986AF: func_surface (surface.c:1328) ==27405== by 0x4CA82A0: run_test (test.h:584) ==27405== by 0x4CA868F: main (test.h:654) ==27405== -- 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 3

[Bug 11607] New: Blood 2: The Chosen keyboard repeat problem
by wine-bugs＠winehq.org 29 May '15

29 May '15

http://bugs.winehq.org/show_bug.cgi?id=11607 Summary: Blood 2: The Chosen keyboard repeat problem Product: Wine Version: 0.9.55. Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquid.acid(a)gmx.net Hi there, I'm filing another Blood 2 bug. This one is input related, more precisely about keyboard input. I know that the Blood 2 informations on the net mentioned the support for DirectInput devices, but I'm not sure this is a dinput bug. So I'm leaving this to unknown for now. To the problem: I installed Blood 2 through wine and did no patching (version is still 1.0). Also the copy protection was not removed, the executable should be clean. Starting the game and entering the configuration menu I noticed it was very hard to setup the keys I wanted to use in the game (like moving forward, backward, etc.) When running Blood 2 natively you select a action in the menu you want to map. You press ENTER and the game engine waits for you to press another key, which it uses for mapping. Now when running wine I had to be REALLY quick when pressing the mapkey. Like some milliseconds later, it was really no fun to config the game. When I wasn't quick enough for an action the ENTER key itself is mapped. Now the interesting part. When not releasing the ENTER key after pressing it, and then pressing the mapkey, the process works. I suspect that the ENTER key generates two events for the game. Pressing and releasing, and the game interprets both events as seperate key presses, so ENTER gots mapped to everything (because the engine thinks it's pressed twice). So either this is X related or a bug in the wine's keyb implementation. Thanks, Tobias -- 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 30

[Bug 36659] New: valgrind shows a definite leak in ddraw/tests/d3d.c:CapsTest()
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36659 Bug ID: 36659 Summary: valgrind shows a definite leak in ddraw/tests/d3d.c:CapsTest() Product: Wine Version: 1.7.19 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 ==9737== 160 bytes in 1 blocks are definitely lost in loss record 1,563 of 2,082 ==9737== at 0x7BC4C6EB: notify_alloc (heap.c:255) ==9737== by 0x7BC50F2F: RtlAllocateHeap (heap.c:1716) ==9737== by 0x4DF6181: DDRAW_Create (main.c:267) ==9737== by 0x4DF6403: DirectDrawCreate (main.c:309) ==9737== by 0x4CA7528: CapsTest (d3d.c:810) ==9737== by 0x4CB7D2D: func_d3d (d3d.c:3953) ==9737== by 0x4D720F8: run_test (test.h:584) ==9737== by 0x4D724E7: main (test.h:654) ==9737== -- 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 36352] New: valgrind shows a ton of leaks in d3dcompiler_43/tests/hlsl.c
by wine-bugs＠winehq.org 29 May '15

29 May '15

https://bugs.winehq.org/show_bug.cgi?id=36352 Bug ID: 36352 Summary: valgrind shows a ton of leaks in d3dcompiler_43/tests/hlsl.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48415 --> https://bugs.winehq.org/attachment.cgi?id=48415 valgrind log ==5735== 2,722,848 bytes in 1 blocks are possibly lost in loss record 1,795 of 1,796 ==5735== at 0x4008B6E: memalign (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==5735== by 0x4008C55: posix_memalign (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==5735== by 0x6E2A809: ??? (in /usr/lib/dri/i965_dri.so) ==5735== by 0x6EF75EA: ??? (in /usr/lib/dri/i965_dri.so) ==5735== by 0x6F562E1: ??? (in /usr/lib/dri/i965_dri.so) ==5735== by 0x70880A0: ??? (in /usr/lib/dri/i965_dri.so) ==5735== by 0x70179B4: ??? (in /usr/lib/dri/i965_dri.so) ==5735== by 0x6A4AB9B: ??? (in /usr/lib/libGL.so.1.2.0) ==5735== by 0x6A1A2F4: ??? (in /usr/lib/libGL.so.1.2.0) ==5735== by 0x66A7DF2: create_glxcontext.isra.0 (opengl.c:1254) ==5735== by 0x66A8127: X11DRV_wglCreateContextAttribsARB (opengl.c:2071) ==5735== by 0x5451C29: wglCreateContextAttribsARB (wgl.c:268) ==5735== by 0x4FA39D8: context_create (context.c:1543) ==5735== by 0x5039866: wined3d_swapchain_create (swapchain.c:914) ==5735== by 0x4F38F1F: d3d9_swapchain_create (swapchain.c:333) ==5735== by 0x4F29669: device_parent_create_swapchain (device.c:3515) ==5735== by 0x4FB7A8B: wined3d_device_init_3d (device.c:896) ==5735== by 0x4F335B5: device_init (device.c:3632) ==5735== by 0x4F33E63: d3d9_CreateDevice (directx.c:465) ==5735== by 0x4A5D7D9: func_hlsl (hlsl.c:108) ==5735== etc. -- 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 3

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