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

[Bug 40046] New: Banished needs ID3D11Device CheckFormatSupport to be implemented
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=40046 Bug ID: 40046 Summary: Banished needs ID3D11Device CheckFormatSupport to be implemented Product: Wine Version: 1.9.2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- You have the option to use DirectX11 from within the Options once the game starts. It will not change since ID3D11Device CheckFormatSupport isn't implemented. Once CheckFormatSupport is changed to return valid flags, it attempts to use DirectX11 but then fails for other reason. -- 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 39

[Bug 40901] New: Factorio crashes with a stack overflow
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=40901 Bug ID: 40901 Summary: Factorio crashes with a stack overflow Product: Wine Version: 1.9.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 54995 --> https://bugs.winehq.org/attachment.cgi?id=54995 +relay,+tid,+seh limited to the thread that crashed. Running the experiential build of Factorio a causes a stack overflow occurs on startup. This doesn't happen with the Factorio Demo or stable build. -- 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 41463] New: Undefined symbols: _DisableThreadLibraryCalls _RaiseException
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=41463 Bug ID: 41463 Summary: Undefined symbols: _DisableThreadLibraryCalls _RaiseException Product: Wine Version: 1.8.5 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine-2016(a)ryandesign.com wine 1.8.5 fails to build on Mac OS X 10.6 Snow Leopard: Undefined symbols: "_DisableThreadLibraryCalls", referenced from: _DllMain in main.o "_RaiseException", referenced from: ___wine_spec_unimplemented_stub in libwinecrt0.a(stub.o) ld: symbol(s) not found collect2: ld returned 1 exit status A full build log can be found here: https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds… The last versions to build on this system were 1.8.4 and 1.9.10. The problem does not affect OS X 10.7 Lion or later. I found a similar problem reported 5 years ago on Solaris in Bug #26291 -- 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 39586] New: Fallout 4 - Steam Version - Crash on Start-up
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=39586 Bug ID: 39586 Summary: Fallout 4 - Steam Version - Crash on Start-up Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: braeden.j.christensen(a)gmail.com Distribution: --- Created attachment 52749 --> https://bugs.winehq.org/attachment.cgi?id=52749 Log File of Fallout 4 Loading the game via Steam or the Fallout 4 Launcher both produce a crash. Trying this via a winewrapper (PlayOnLinux) or regular wine produces the same result. This seems to be due to some kind of 64bit error. Attached is a log. This is the first bug report I have ever filed, and think I have filed it correctly. Please, feel free to yell RTFM if you want if I've made a mistake. :P -- 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 28

[Bug 40692] New: Rocket League needs AES encryption/ decryption implemented in bcrypt.dll
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=40692 Bug ID: 40692 Summary: Rocket League needs AES encryption/ decryption implemented in bcrypt.dll Product: Wine Version: 1.9.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: maxime(a)mmorel.eu Distribution: --- A recent update of the game in Steam broke wine support. The game requires AES encryption features from bcrypt.dll to play online. These API must be implemented with AES algorithm : BCryptOpenAlgorithmProvider BCryptGenerateSymmetricKey BCryptEncrypt BCryptDecrypt BCryptDestroyKey BCryptCloseAlgorithmProvider With stub implementation of these, the game is running and can be played in solo. -- 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 40680] New: Rocket league needs bcrypt.dll.BCryptGenerateSymmetricKey
by wine-bugs＠winehq.org Dec. 15, 2017

Dec. 15, 2017

https://bugs.winehq.org/show_bug.cgi?id=40680 Bug ID: 40680 Summary: Rocket league needs bcrypt.dll.BCryptGenerateSymmetricKey Product: Wine Version: 1.9.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: maxime(a)mmorel.eu Distribution: --- Created attachment 54554 --> https://bugs.winehq.org/attachment.cgi?id=54554 bcrypt patch Latest Steam update of Rocket League prevents it to run with wine. The game exits early with this message: wine: Call from 0x7b43cf4c to unimplemented function bcrypt.dll.BCryptGenerateSymmetricKey, aborting This can be fixed by implementing the missing symbol and making it return 0. Seems to be enough for now. -- 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 36524] New: Far Cry 2: Graphical Glitches and Unstable Gameplay
by wine-bugs＠winehq.org Dec. 12, 2017

Dec. 12, 2017

http://bugs.winehq.org/show_bug.cgi?id=36524 Bug ID: 36524 Summary: Far Cry 2: Graphical Glitches and Unstable Gameplay Product: Wine Version: 1.7.18 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ipickert55(a)gmail.com Created attachment 48607 --> http://bugs.winehq.org/attachment.cgi?id=48607 Log I have an AMD Radeon 7950, and I am getting serious graphical errors. The screenshots will explain it better than I can, it is basically just random colors all over the screen. On top of this, if I raise the settings to anything higher than low, the game will crash almost immediately. -- 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

[Bug 41361] New: MSI uninstaller calls wrong Custom Action and performs wrong action
by wine-bugs＠winehq.org Dec. 12, 2017

Dec. 12, 2017

https://bugs.winehq.org/show_bug.cgi?id=41361 Bug ID: 41361 Summary: MSI uninstaller calls wrong Custom Action and performs wrong action Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: reinhold.hoffmann(a)hotmail.com Distribution: --- Created attachment 55713 --> https://bugs.winehq.org/attachment.cgi?id=55713 msi with special prepared custom actions to show the bug In certain situation the MSI uninstaller calls a wrong custom action. When an app is installed and the same app msi installation is called again, this app should be repaired or removed. This is initiated properly but for "Remove" the wrong custom action is called and the software is not removed. I have prepared a dummy repro based on the installer of Notation Player, please find attached. This repro contains of 4 custom actions. - Install after the software is installed but not yet registered - Commit when the software is installed and registered in the Registry just before the end of the installaion process - Rollback when a Rollback is performed - Uninstall when an uninstallation is performed. The custom action of the repro in all cases simply displays which custom action is called. How to reproduce the failure: ------------------------------ Scenario 1: Installation OK: custom actions Install and Commit are called Scenario 2: OK: when uninstalling with uninstaller the Uninstall custom action is called FAILURE situation: ------------------ Perform Scenario 1. Perform Scenario 1 again Here the according Repair/Remove window pops up. When selecting "Repair" the Install and Commit actions are called. This is correct. But when selecting "Remove" the Install and Commit custom action are called, too. This is wrong. When selecting "Remove" the Uninstall custom action had to be called and the software needs to be removed. The uninstaller confirmes that the app has been successfully removed. Indeed, the uninstaller shows that the software is removed but it is not. The software is not removed but still exists. For a sophisticated custom action handling this scenario brings the system into an undefined state. An experienced person is required to fix this situation. -- 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 15

[Bug 41890] New: Fallout 4 (Steam): Game menu / intro doesn' t show up because of multiple DirectX11 errors
by wine-bugs＠winehq.org Dec. 12, 2017

Dec. 12, 2017

https://bugs.winehq.org/show_bug.cgi?id=41890 Bug ID: 41890 Summary: Fallout 4 (Steam): Game menu / intro doesn't show up because of multiple DirectX11 errors Product: Wine Version: 1.9.24 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: kaazoo(a)drqueue.org Created attachment 56276 --> https://bugs.winehq.org/attachment.cgi?id=56276 terminal output from game startup (including Steam) until back screen The game fails to show any menu or intro video because of many DirectX11 related errors. A black screen is displayed instead. These are the most appearing errors from d3d11: fixme:d3d11:d3d11_immediate_context_ClearState iface 0x27b379a0 stub! fixme:d3d11:d3d_buffer_init Ignoring structure byte stride 48. fixme:d3d11:d3d_buffer_init Ignoring structure byte stride 512. fixme:d3d11:d3d_buffer_init Ignoring structure byte stride 8. fixme:d3d11:device_parent_create_swapchain_texture Implement DXGI<->wined3d usage conversion. fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x27b379c0, container_parent 0x27b37570, wined3d_desc 0x23ec88, wined3d_texture 0x27b69f30 partial stub! fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x27b379c0, container_parent 0x27b6c750, wined3d_desc 0x23f348, wined3d_texture 0x27b6c900 partial stub! fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x27b379c0, container_parent 0x27b6c750, wined3d_desc 0x23f348, wined3d_texture 0x27b6f1b0 partial stub! fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x27b379c0, container_parent 0x27b6c750, wined3d_desc 0x23f348, wined3d_texture 0x27b6f1b8 partial stub! fixme:d3d11:shdr_handler Unhandled chunk "PCSG". fixme:d3d11:shdr_handler Unhandled chunk "RDEF". fixme:d3d11:shdr_handler Unhandled chunk "STAT". fixme:d3d11:skip_dword_unknown $ADDRESS fixme:d3d11:wined3d_depth_stencil_view_desc_from_d3d11 Unhandled depth stencil view flags 0x1. fixme:d3d11:wined3d_depth_stencil_view_desc_from_d3d11 Unhandled depth stencil view flags 0x2. fixme:d3d11:wined3d_depth_stencil_view_desc_from_d3d11 Unhandled depth stencil view flags 0x3. fixme:d3d11:wined3d_usage_from_d3d11 Unhandled bind flags 0x80. These are the most appearing errors from d3d: err:d3d:wined3d_check_gl_call >>>>>>> GL_INVALID_ENUM (0x500) from creating VAO @ ../../../dlls/wined3d/context.c / 1914. err:d3d:wined3d_check_gl_call >>>>>>> GL_INVALID_ENUM (0x500) from extension detection @ ../../../dlls/wined3d/directx.c / 3935. fixme:d3d:buffer_type_hint_from_bind_flags Unhandled bind flags 0x8. fixme:d3d:buffer_type_hint_from_bind_flags Unhandled bind flags 0x88. fixme:d3d:buffer_type_hint_from_bind_flags Unhandled bind flags 0x8b. fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. fixme:d3d:wined3d_buffer_create Ignoring access flags (pool). fixme:d3d:wined3d_shader_resource_view_create_texture_view OpenGL implementation does not support texture views. fixme:d3d:wined3d_shader_resource_view_init Buffer shader resource views not supported. fixme:d3d:wined3d_shader_resource_view_init Shader resource view not supported, resource format WINED3DFMT_R16_TYPELESS, view format WINED3DFMT_R16_UNORM. These are the most appearing errors from d3d_shader: fixme:d3d_shader:shader_sm4_read_dcl_resource Unhandled resource type 0xa. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x5b, opcode_token 0x0400005b. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x82, opcode_token 0x05000082. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x83, opcode_token 0x05000083. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x9d, opcode_token 0x0300009d. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x9e, opcode_token 0x0400009e. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xa1, opcode_token 0x030000a1. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xb0, opcode_token 0x070000b0. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xb1, opcode_token 0x070000b1. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xb4, opcode_token 0x090000b4. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xbe, opcode_token 0x010018be. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00111103. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00199983. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x800000c2. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000142. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000182. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000202. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80000282. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x800002c2. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80002302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80004302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80010302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80018302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80022302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80026302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80028302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x8002e302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80032302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80038302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80050302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80070302. fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x80100302. fixme:d3d_shader:shader_sm4_read_param Skipping modifier 0x00000001. Please see the attached logfile for details. -- 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

[Bug 41566] New: Amaranth Audio Cycle crashes when opening certain windows
by wine-bugs＠winehq.org Dec. 12, 2017

Dec. 12, 2017

https://bugs.winehq.org/show_bug.cgi?id=41566 Bug ID: 41566 Summary: Amaranth Audio Cycle crashes when opening certain windows Product: Wine Version: 1.9.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: katsunori.kumatani(a)gmail.com Distribution: --- Created attachment 55897 --> https://bugs.winehq.org/attachment.cgi?id=55897 Terminal output + Crash dump Cycle is a VST synthesizer, but also comes as standalone. Download the demo here: http://www.amaranthaudio.com/data/binary/CycleDemoInstaller.exe Since the author hasn't updated it for close to 2 years, please download and back it up even if you don't want to investigate the bug yet, for the future (alternatively, if site goes down I can upload the demo installer somewhere). Steps to crash: 1) Install Cycle, we're interested in the "Standalone" because it's easier to debug/test, but the VST version has the exact same crash. 2) Launch it, e.g: /opt/wine-devel/bin/wine "~/.wine/drive_c/Program Files (x86)/Amaranth Audio/Cycle/Cycle.exe" 3) Go to the Audio tab at the top, and click on "Modulation Matrix". 4) Cycle Crashes. Btw, yes, I did try it in 32-bit WINEPREFIX as well, same thing, I forgot to set the WINEARCH when doing this dump in a fresh prefix, but trust me it is the same crash on NULL (just test it yourself). So it doesn't matter, the exact same thing happens in 32-bit WINEPREFIX. The terminal output + crash dump is 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 13