The only official thing I have seen outside these forums was the initial announcement -That's the one i tried and it made no difference which is why I went to last resort and digging into the documentation to find absolutely nothing.
That was never a great advert for Wayland IMO.Compensation for displays which use overscan is tricky under Wayland, and we haven’t quite got it working yet, so this has been removed for now. The vast majority of displays nowadays don’t need it, but we will be putting it back when we have worked out how best to do it!
And it's rather annoying it was removed for X11 and not just Wayland, seeing as older Pi can only use X11 and overscan used to work fine. It is what kept me from upgrading to Bookworm.
I would also question "the vast majority of displays nowadays don’t need it". Monitors don't, modern and expensive TV maybe not, but many of us are using Pi with older TV which do. Often they don't need it for the LCD itself; that is fine, fits image to LCD perfectly. But the TV has a frame which overlaps the LCD thus requiring it. None of the TV I have support overscan adjustment beyond Zoom and similar features which don't do as needed.
Most users probably won't need it but I would expect there's a significant minority who do.
With a TV which defeats added borders by auto-zooming I don't know what the solution would be. But, if overscan did work previously, it should continue to work with Bookworm, would be an unwanted 'negative improvement' if it doesn't.
But 'wlr-randr' perhaps does. The desktop "Screen Configuration" uses that.Its very confusing where "HDMI-A-1" comes from, xrandr doesn't display that
There's an added complication in DISPLAY=:0 now AIUI has to be WAYLAND_DISPLAY="wayland-1" in some places.
So there's now at least three different ways to refer to the same thing, and you have to pick the right one for the context. But I don't think anyone ever said Linux wasn't confusing and built on shifting sand.
Statistics: Posted by hippy — Sat May 11, 2024 12:47 pm