https://bugs.winehq.org/show_bug.cgi?id=56493
--- Comment #8 from Hans Leidekker hans@meelstraat.net --- (In reply to Dmitry Timoshkov from comment #7)
(In reply to Dmitry Timoshkov from comment #6)
(In reply to Hans Leidekker from comment #5)
It's likely a regression but it's not certain because the installer ignores it and returns success anyway. And as you mentioned, starting the service afterwards works fine. I don't want to spend time chasing this if I don't have to ;-)
The problem is that the crash sometimes leads to creation of the debugger prompt window that breaks an unattended install. Before the problematic commit there were no any debugger windows that needed a user response during the installation.
Also the regression may indicate that the installation process after that commit has changed, and now some components could be instaled in wrong order, that potentially may break other installers.
Sure but the installer doesn't show this behavior in a 64-bit prefix. It could be a bug in the installer too. I hope you understand that I want to verify this.