While Xorg lets you create any resolution of your choice, doing so will result in indirect rendering, which will result in tearing with the modeset driver.
So this bug seems like user error... You just need to remove the custom mode "1912x1080" or find out what/where that came from.
Looking deeper at this bug I just noticed the issue is triggered by using a fake screen resolution:
1912x1080_60.00 (0x48) 171.250MHz -HSync +VSync *current +preferred
It should be 1920x1080 (https:/ /support. hp.com/ au-en/document/ c05033206# AbT3).
While Xorg lets you create any resolution of your choice, doing so will result in indirect rendering, which will result in tearing with the modeset driver.
So this bug seems like user error... You just need to remove the custom mode "1912x1080" or find out what/where that came from.