wine-bugs December 2016

wine-bugs@winehq.org

1 participants
7925 discussions

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

12 Dec '17

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 12 Dec '17

12 Dec '17

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 12 Dec '17

12 Dec '17

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

[Bug 35745] New: Proetus 8 install stops when asking for license key
by wine-bugs＠winehq.org 11 Dec '17

11 Dec '17

http://bugs.winehq.org/show_bug.cgi?id=35745 Bug ID: 35745 Summary: Proetus 8 install stops when asking for license key Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jozamm(a)gmail.com Created attachment 47737 --> http://bugs.winehq.org/attachment.cgi?id=47737 Errors during proteus installation Hi, I am installing proteus 8.1 sp1 and the install stops when asking for the licence key. I click on next and nothing happens. I tried the solution of bug 35544 by installing winetricks -q w57 but it didnt work. I am using wine 1.7.13. The main error seems to be fixme:wshom:ClassFactory_QueryInterface (0x7ff0d6c8cac0)->({342d1ea0-ae25-11d1-89c5-006008c3fbfc} 0x55cee0) fixme:wshom:WshShell3_QueryInterface Unknown iface {fc4801a3-2ba9-11cf-a229-00aa003d7352} fixme:wshom:WshShell3_QueryInterface Unknown iface {719c3050-f9d3-11cf-a493-00400523a8a6} Any help would be appreciated, jozamm -- 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 41690] New: winegstreamer compiler warnings when building Wine 64-bit
by wine-bugs＠winehq.org 11 Dec '17

11 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=41690 Bug ID: 41690 Summary: winegstreamer compiler warnings when building Wine 64-bit Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 56086 --> https://bugs.winehq.org/attachment.cgi?id=56086 Compiler warnings for winegstreamer When compiling the 64-bit version of wine-1.9.22-129-g906e770, I receive the attached compiler warnings for winegstreamer. -- 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 32861] New: Closing Mathematica via window with main menu leads to hang
by wine-bugs＠winehq.org 10 Dec '17

10 Dec '17

http://bugs.winehq.org/show_bug.cgi?id=32861 Bug #: 32861 Summary: Closing Mathematica via window with main menu leads to hang Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Classification: Unclassified At start Mathematica opens two windows: one with decoration and main menu, and another with startup screen. On Windows when you click close button on menu window, Mathematica quits. On Wine it just hangs. -- 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 14296] New: winhelp: Extraneous flashing cursor/caret
by wine-bugs＠winehq.org 08 Dec '17

08 Dec '17

http://bugs.winehq.org/show_bug.cgi?id=14296 Summary: winhelp: Extraneous flashing cursor/caret Product: Wine Version: 1.1.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Wine winhelp shows a flashing cursor/caret symbol when you click somewhere in the text. Windows winhelp does not do that. That behaviour may be desired, e.g. it makes selecting text using the keyboard possible. However... Click in a page so the cursor is shown, then click on a link to go to another page. A flashing cursor is present at the top left, even before you click in the page. On some help pages, the flashing cursor is present at the top left even before the user clicks in the page. Also, if there is a large graphic at the top left, the flashing cursor may appear (see cwdeluxe.hlp and click on the picture). Windows 95 Winhelp does not allow images to be selected. cwdeluxe.hlp is in winehelp_bugs.tar.bz2 at http://bugs.winehq.org/attachment.cgi?id=14574 -- 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 12

[Bug 41837] New: Way of the Samurai 4 has black blocks in the main menu without native d3dx9
by wine-bugs＠winehq.org 08 Dec '17

08 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=41837 Bug ID: 41837 Summary: Way of the Samurai 4 has black blocks in the main menu without native d3dx9 Product: Wine Version: 1.9.24 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 56261 --> https://bugs.winehq.org/attachment.cgi?id=56261 Wine 1.9.24 without "winetricks d3dx9" I have a 32-bit Windows XP prefix in Wine 1.9.24 with the following overrides installed via winetricks: amstream quartz devenum wmp9 physx d3dcompiler_43 (These winetricks are required to even be able to start the game...) If I do not run the command "winetricks d3dx9" then the main menu has black blocks in the main menu. I've tried installing the individual d3dx9 dlls ( d3dx9_36, d3dx9_26, d3dx9_43, d3dx9_39, d3dx9_42, d3dx9_35, d3dx9_31, d3dx9_28) that are available to install via winetricks but none of those helped. Terminal output without "winetricks d3dx9" being ran has been 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

[Bug 34328] New: World of Tanks: Purple graphics errors
by wine-bugs＠winehq.org 08 Dec '17

08 Dec '17

http://bugs.winehq.org/show_bug.cgi?id=34328 Bug #: 34328 Summary: World of Tanks: Purple graphics errors Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: JohannesBauer(a)gmx.de CC: wine-bugs(a)winehq.org Classification: Unclassified I'm using wine-1.7.0 which I've patched with the disable-dynamic-vertex-buffers.patch (https://github.com/Pinkbyte/pinkbyte-overlay/blob/master/app-emulation/wine…). When I play (no matter what graphics settings, no matter if fullscreen or windowed), I get purple bars over some text elements. It's annoying ingame because I cannot tell the difference which players are alive and which are dead anymore. Here's a screenshot of what it looks like: http://i.imgur.com/QFuwKqA.png I'm on Gentoo LInux x86_64 with a Nvidia graphics cards and the proprietary Nvidia driver: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) Details: 01:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device 1270 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at cc00 [size=128] [virtual] Expansion ROM at fc000000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: nvidia Is there anything I could try to get rid of this problem? Other than this it runs very nicely. -- 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 11

[Bug 42128] New: Anime Studio Professional 8 hogs CPU after it's closed.
by wine-bugs＠winehq.org 08 Dec '17

08 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=42128 Bug ID: 42128 Summary: Anime Studio Professional 8 hogs CPU after it's closed. Product: Wine Version: 2.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lanfrda1(a)gmail.com CC: wine-bugs(a)winehq.org Distribution: Ubuntu Created attachment 56668 --> https://bugs.winehq.org/attachment.cgi?id=56668 Proof that it's using up the CPU. When I close the program, the task isn't killed, and it hogs up a cpu thread to 100%, until I kill the process. -- 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 December 2016