Hi, thanks for your report.
I can't really read backtraces, but wonder if these identical lines are normal: > 22 0x000000007bf00d99 _start+0x28() in <wine-loader> (0x0000000000000000) [...] > 200 0x000000007bf00d99 _start+0x28() in <wine-loader> (0x0000000000000000) Maybe try to install the dbgsym packages for at least wine64 and libwine:amd64. See: https://wiki.debian.org/AutomaticDebugPackages Then, did you test with wine-development? $ sudo apt install wine-development $ sudo update-alternatives --config wine --> Choose "1 /usr/bin/wine-development" $ wine --version --> Verify that you are using wine-development now Is your test suite freely available online (or can you make it so)? >From the Debian Wine packaging itself this issue might only be because of the alternatives system added in 1.8.3-3, or because of a patch for building with newer gnutls (since 1.8.4 also in upstream). I don't really think this is the case, so in the end I guess you'll have to report this upstream: https://wiki.winehq.org/Bugs Please report your findings for both wine and wine-development and if possible post the link to your test suite. When you've done so please notify this report here by sending an email, starting with something like this line: control: forwarded -1 https://bugs.winehq.org/show_bug.cgi?id=XXXXX Greets jre