https://bugs.kde.org/show_bug.cgi?id=522149
--- Comment #8 from Ed <[email protected]> --- Created attachment 194167 --> https://bugs.kde.org/attachment.cgi?id=194167&action=edit Journal snippet capturing the rapid client.platformscreens geometry loop and QRect shifting at 08:32:33 during cold boot initialization. I am attaching a snippet of my user journal (Boot_Log_1.md) capturing the exact moment the layout corruption occurs during initialization. As you can see in the timestamps around 08:32:33, the compositor is getting trapped in a rapid, infinite geometry renegotiation loop. client.platformscreens is repeatedly firing screen update notifications and shifting the QRect canvas coordinates back and forth within the exact same second. It looks like a race condition where KWin is attempting to map the multi-monitor workspace boundaries before the proprietary NVIDIA driver has fully completed its DRM modesetting handshake with the high-refresh Blackwell hardware, causing the initial layout discovery to fail out of exhaustion. -- You are receiving this mail because: You are watching all bug changes.
