https://bugs.winehq.org/show_bug.cgi?id=55628
Bug ID: 55628 Summary: user32:monitor fails to change the screen bpp on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
user32:monitor fails to change the screen bpp on macOS:
monitor.c:806: Test failed: Device \.\DISPLAY1 test 1 expect dmBitsPerPel 16, got 32 monitor.c:857: Test failed: Failed to find a different mode. monitor.c:879: Test failed: Device \.\DISPLAY1 test 0 expect dmBitsPerPel 8, got 32 monitor.c:2416: Test failed: bpp 16: Expected 16, got 32. monitor.c:2416: Test failed: bpp 8: Expected 8, got 32. monitor.c:2467: Test failed: Expected BITSPIXEL 8, got 32. monitor.c:2480: Test failed: Expected bpp 8, got 32. monitor.c:2484: Test failed: Expected bpp 8, got 32. monitor.c:2506: Test succeeded inside todo block: bpp 8: Selecting bitmap succeeded. monitor.c:2558: Test failed: Failed to find a different resolution for \.\DISPLAY1. monitor.c:2571: Test failed: Expected BITSPIXEL 8, got 32. monitor.c:2586: Test failed: Expected BITSPIXEL 16, got 32.
See https://test.winehq.org/data/patterns.html#user32:monitor
The failures are systematic and only happen on macOS (see Remi's rbernon-macos-* cloud test machines).
Looking at macdrv_ChangeDisplaySettings() in dlls/winemac.drv/display.c it looks like changing the display bit depth is not supported... at least by winemac.drv if not by macOS itself. Windows applications that need 8 and 16 bpp are probably old and rare now so this may not be a major compatibility issue, but it is going to be an issue for this test. Hence the following questions: * Does macOS support changing the display bit depth? * If not is this something winemac.drv can emulate? * If not, how can we get the test to not fail without essentially dropping these tests on all platforms?
https://bugs.winehq.org/show_bug.cgi?id=55628
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase