https://bugs.winehq.org/show_bug.cgi?id=55240
Bug ID: 55240 Summary: The 64-bit winmm:capture & winmm:wave get BADDEVICEID on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
The 64-bit winmm:capture & winmm:wave get BADDEVICEID on Windows 10+:
capture.c:180: Test failed: waveInGetDevCapsW(0): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID(A device ID has been used that is out of range for your system.) [...]
wave.c:691: Test failed: waveOutGetDevCapsW(WAVE_MAPPER): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID(A device ID has been used that is out of range for your system.) [...]
See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave
This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit:
commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard julliard@winehq.org Date: Mon Jul 10 17:18:49 2023 +0200
gitlab: Upgrade the Debian image to bookworm.
Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler.