https://bugs.kde.org/show_bug.cgi?id=523995
--- Comment #4 from Branislav Klocok <[email protected]> --- I see the same thing in a different setup, and a WAYLAND_DEBUG log suggests the wrong size comes from the Qt client, not from KWin. My trigger is undocking, closing the lid so the laptop suspends with no output, then docking again and opening the lid. The Qt clients log "There are no outputs - creating placeholder screen". Afterwards maximized Qt windows (Konsole, Dolphin, KRDC) keep the width of the laptop panel on the external monitor. Firefox, Thunderbird and Chrome come back at the right size. KWin 6.7.5, Qt 6.11.2. In the log of one Konsole window, KWin sends the correct maximized size twice after resume. The client acks it but attaches no new buffer and does not call set_window_geometry, so its window geometry stays at the old size. Seven seconds later KWin sends the old size back and the client follows. Without suspend, when the outputs never disappear, the same window resizes correctly. This matches QTBUG-141359 (https://qt-project.atlassian.net/browse/QTBUG-141359), where I posted the log details and excerpts. It may be the same bug as this one. -- You are receiving this mail because: You are watching all bug changes.
