On Mon Jun 12 07:16:53 2023 +0000, Huw Davies wrote:
What's the route for this to happen? Is `drv.pGetPropValue()` succeeding without updating `pv`? If so, with which driver?
I have not looked into that yet, I just discovered this problem because Battle.net refused to start with my latest Wine builds, and it was crashing in the PropVariantClear. I am however getting this in the log:
``` 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 0150:fixme:mmdevapi:MMDevice_SetPropValue Unhandled type 0 ```
(driver should be winepulse.drv with pipewire-pulse as server)