https://bugs.kde.org/show_bug.cgi?id=522149
Ed <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |RESOLVED Resolution|--- |NOT A BUG --- Comment #9 from Ed <[email protected]> --- I found the root cause and this can be closed as a local hardware/topology issue rather than a KWin bug. One of my monitors was connected through an HDMI source-switching/splitter-type device so I could switch between machines, and that same monitor also had another direct cable/source path involved. In other words, my display topology was more complicated than I realized. During cold boot, the GPU/KWin/KScreen stack was likely seeing confusing or unstable monitor/EDID/source information from that setup. After simplifying/removing that switching path and correcting the monitor cabling, the issue no longer appears to reproduce. The cold-boot display layout now initializes correctly. I apologize for the noise, and I sincerely appreciate the time spent looking at this — especially the triage around whether this was distinct from the logout/shutdown teardown issue, and the request to test Wayland. That helped me narrow the problem down. Thank you to Nate, Vlad, Xaver, David, and everyone else copied here. Please close this as a local configuration/hardware issue / not a KWin bug. -- You are receiving this mail because: You are watching all bug changes.
