https://bugs.winehq.org/show_bug.cgi?id=53969
Bug ID: 53969 Summary: lets vpn Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: kalistochina@yahoo.com Distribution: ---
Created attachment 73559 --> https://bugs.winehq.org/attachment.cgi?id=73559 crash report
Lets vpn installed, cannot be launched, only minimized icon shows in a tray
https://bugs.winehq.org/show_bug.cgi?id=53969
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|lets vpn |LetsVPN does not work Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO
--- Comment #1 from Gijs Vermeulen gijsvrm@gmail.com ---
wine-7.0.r0.g2fc92f8b ( TkG Staging )
Custom wine versions are not supported here, please try with upstream wine, preferably wine-7.21.
Always attach the full terminal output, not only the backtrace, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal_output.29.3F
Is there a free and legal download this can be reproduced with?
1 0x69d8d98f D3DAssemble+0xc7f() in d3dcompiler_47 (0x0f50eb98)
You might want to try 'winetricks -q d3dcompiler_47'.
https://bugs.winehq.org/show_bug.cgi?id=53969
--- Comment #2 from Rafał Mużyło galtgendo@o2.pl ---
You might want to try 'winetricks -q d3dcompiler_47'.
You *do* know that's a workaround, not a fix ?
As for the problem, I wonder if it won't be another case of vkd3d-shader failing to parse a shader...
It depends on where that 'D3DAssemble+0xc7f' is actually pointing to in the sources.
https://bugs.winehq.org/show_bug.cgi?id=53969
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #2)
You might want to try 'winetricks -q d3dcompiler_47'.
You *do* know that's a workaround, not a fix ?
Yes, but suggesting workarounds to users is generally helpful.
As for the problem, I wonder if it won't be another case of vkd3d-shader failing to parse a shader...
It depends on where that 'D3DAssemble+0xc7f' is actually pointing to in the sources.
7.0 predates use of vkd3d-shader to compile HLSL; before that point HLSL compilation would fail, although I wouldn't exactly expect it to crash. Hence testing with a more recent version would be generally useful.
https://bugs.winehq.org/show_bug.cgi?id=53969
--- Comment #4 from Gijs Vermeulen gijsvrm@gmail.com --- *** Bug 53982 has been marked as a duplicate of this bug. ***
-
WineHQ Bugzilla