I still have the same issue with 2.55 which started for me in 2.53, where the taskbar has clipping on part of the clock and sometimes the start button, on secondary monitors. I am still running 2.51 on my primary system because the clipping is really bad and causes flickering, and it's quite distracting and annoying.
I updated to 2.55 on another computer just to test, and I think maybe the flickering and clipping is a bit less in this 2.55 version, or maybe it's just more consistent and less chaotic, but it still persists and you can see here in the screenshot the same small bit of clipping can be seen on each of the three secondary displays in the clock area where the start of the "S" in Sun is cut off. Sorry if it's small and hard to see without zooming in, but it's the best way to capture what is going on. When you actively drag windows from one screen to the next, the left and right sides of the taskbar start flickering and more of the clock gets cut off and sometimes the left side of the start button is cut off also. But once you release a window into a destination screen, it will refresh after a moment, and the result is usually as you can see here, it consistently cuts off some of the left side of the clock text. So, when windows are not moving, it's not that bad, just part of the clock is cut off but, while you are actively moving windows, lots of flickering and clipping on the taskbar on all displays where there is movement.
The primary display (the one with the task tray and pinned shortcuts) functions properly all the time and does not experience any clipping or flickering, only the secondary displays. Settings are to always show taskbars on all screens. This screenshot was taken via RDP, so this issue happens on the system locally, and even when connected via Windows RDP.
On the same system running version 2.51, everything is perfect, no flickering when moving windows around and no clipping or cut off areas in the taskbar.
Both systems running Windows 11 24H2, and both have Nvidia GPU with the same latest "game ready" drivers.
I'm curious if anyone else has experienced issues like this when using multiple displays or if this is something unique to my two computers and these 4x monitors??
Thanks for any attention and time spent looking into this issue and work done on a resolution.