Could you try to do a fresh boot, log in, lock screen, unlock and attach the Xorg.0.log to the bug?
The logs reported have snippets like
"[ 18.916] (II) intel(0): resizing framebuffer to 3840x1080
[ 18.932] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (1920, 0), rotation normal, reflection none
[ 23.688] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1920, 0), rotation normal, reflection none
[ 23.691] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation normal, reflection none
[ 2239.871] (II) intel(0): resizing framebuffer to 1920x1080
[ 2239.873] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 0, position (0, 0), rotation normal, reflection none
[ 2240.201] (II) intel(0): resizing framebuffer to 3840x1080"
unsure if that matches an user triggered change or if the monitor config in xorg changes when power saving starts or something
Thanks, that looks similar to bug #1295267
Could you try to do a fresh boot, log in, lock screen, unlock and attach the Xorg.0.log to the bug?
The logs reported have snippets like
"[ 18.916] (II) intel(0): resizing framebuffer to 3840x1080
[ 18.932] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (1920, 0), rotation normal, reflection none
[ 23.688] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1920, 0), rotation normal, reflection none
[ 23.691] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation normal, reflection none
[ 2239.871] (II) intel(0): resizing framebuffer to 1920x1080
[ 2239.873] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 0, position (0, 0), rotation normal, reflection none
[ 2240.201] (II) intel(0): resizing framebuffer to 3840x1080"
unsure if that matches an user triggered change or if the monitor config in xorg changes when power saving starts or something