Bug#953982: wine-development: wine in Debian fails to start "Uru", but upstream wine works fine (regression)

[Diafero <diafero@arcor.de>]

Package: wine-development
Version: 5.2-3
Severity: important

Dear Maintainer,

The online version of the old game "Uru: Path of the Shell" has worked fine in
wine for many years, up until version 4.21.  But with recent versions (I tried
5.1 and 5.2), it stopped working: on startup, when it should download some basic
information from the server, it shows "Unable to download update file".

Downgrading wine again to 4.21 fixes the issue.

The log output with WINEDEBUG=fixme+all,+winsock until the moment the error
message appears is

000d:err:module:__wine_process_init
L"C:\\windows\\system32\\winemenubuilder.exe" not found
000b:err:wineboot:process_run_key Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
0009:trace:winsock:DllMain 0x7ee40000 0x1 0x32fd24
0009:trace:winsock:GetAddrInfoW nodename L"the-deep-island.de", servname (null),
hints 0x32de20, result 0x32de1c
0009:trace:winsock:WS_getaddrinfo "the-deep-island.de", (null) 0x823490 ->
0x32dd58 0
0009:trace:winsock:WS_inet_ntop family 2, addr (0x8234e4), buffer (0x32dbc0), len 16
0009:trace:winsock:WS_getaddrinfo => 0x8234b8, flags 0, family 2, type 0,
protocol 0, len 16, name (null), addr { family AF_INET, address 85.214.18.84,
port 0 }
0009:trace:winsock:WS_inet_ntop family 2, addr (0x823524), buffer (0x32dbc0), len 16
0009:trace:winsock:WS_getaddrinfo => 0x8234f8, flags 0, family 2, type 0,
protocol 0, len 16, name (null), addr { family AF_INET, address 85.214.18.84,
port 0 }
0009:trace:winsock:WS_inet_ntop family 2, addr (0x823564), buffer (0x32dbc0), len 16
0009:trace:winsock:WS_getaddrinfo => 0x823538, flags 0, family 2, type 0,
protocol 0, len 16, name (null), addr { family AF_INET, address 85.214.18.84,
port 0 }
0009:trace:winsock:WS_inet_ntop family 2, addr (0x822f7c), buffer (0x822ffc), len 65
0009:trace:winsock:WSAStartup verReq=101
0009:trace:winsock:WSAStartup succeeded starts: 1
0009:trace:winsock:WS_socket af=2 type=1 protocol=0
0009:trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0
flags=0x1
0009:trace:winsock:WSASocketW   created 0100
0009:trace:winsock:WS_inet_ntop family 2, addr (0x822f7c), buffer (0x32dd9e), len 16
0009:trace:winsock:WS_connect socket 0100, ptr 0x822f78 { family AF_INET,
address 85.214.18.84, port 80 }, length 16
0009:warn:winsock:wsaErrno errno 115, (Operation now in progress).
0009:trace:winsock:WS_connect   connected 0100
0009:trace:winsock:WS_setsockopt (socket 0100, level IPPROTO_TCP, name
TCP_NODELAY, optval 0x32de30 (1), optlen 4)
0009:trace:winsock:WS_setsockopt (socket 0100, level SOL_SOCKET, name
SO_SNDTIMEO, optval 0x32dfa8 (15000), optlen 4)
0009:trace:winsock:WSAIoctl 0100, FIONBIO, 0x32df30, 4, 0x32df30, 4, 0x32ded8,
(nil), (nil)
0009:trace:winsock:WSAIoctl -> FIONBIO (0)
0009:trace:winsock:WS2_sendto socket 0100, wsabuf 0x32de94, nbufs 1, flags 0, to
(nil), tolen 0, ovl (nil), func (nil)
0009:trace:winsock:WS2_sendto fd=19, options=0
0009:trace:winsock:WS2_sendto  -> 132 bytes
0009:trace:winsock:WS_setsockopt (socket 0100, level SOL_SOCKET, name
SO_RCVTIMEO, optval 0x32cce8 (15000), optlen 4)
0009:trace:winsock:WS2_recv_base socket 0100, wsabuf 0x32cb84, nbufs 1, flags 0,
from (nil), fromlen -1, ovl (nil), func (nil)
0009:trace:winsock:WS2_recv_base fd=19, options=0
0009:trace:winsock:WS2_recv_base  -> 527 bytes

I compiled upstream wine 5.2 myself, and then everything works fine. The log
looks basically the same (except some addresses are different).
I reported this upstream at https://bugs.winehq.org/show_bug.cgi?id=48741, but
as long as I cannot reproduce upstream this seems much more like a Debian-side
issue.
I think either this is caused by some patch Debian carries, some
packaging/linking issue, or one of the optional dependencies that packaged wine
uses but my own compilation does not (but I tried to get anything
network-related... any guesses?).

Kind regards
diafero