Fedora 44 KDE Plasma 6.7.0 + NVIDIA RTX 5080 multi-monitor corruption after login System: - Fedora 44 KDE - Plasma/KWin/KScreen 6.7.0-1.fc44 - NVIDIA RTX 5080 - NVIDIA driver 595.80 - Kernel tested: 7.0.12-201.fc44 and 7.0.11-200.fc44 - Three monitors: center 2560x1440, left/right 1920x1080 Problem: After transaction 224 upgraded Plasma/KWin/KScreen from 6.6.5 to 6.7.0, SDDM/login screen renders correctly across all three displays. After login, Plasma corrupts the desktop rendering. On X11 the center display renders incorrectly; on Wayland the failure changes location. Older kernel did not resolve it. Important log evidence: KWin crash log references: KWin::RenderLoop::activeWindowControlsVrrRefreshRate() Also seeing NVIDIA/EDID related warnings. What I tried: - Reboot - X11 and Wayland sessions - Older kernel 7.0.11 - Reset KScreen/Plasma monitor config - Re-applied xrandr layout - Confirmed NVIDIA driver loads - Confirmed monitor geometry is detected correctly - Windows drives all three monitors normally This looks like a regression in Plasma/KWin/KScreen 6.7.0 with NVIDIA/multi-monitor/VRR handling.
Created attachment 193485 [details] Boot_Logs Attached full boot_logs.txt.gz from the affected session. The grep hits include KWin/KScreen startup, NVIDIA monitor detection, Dell AW2725DM registration messages, and DrKonqi/coredump activity. I’m attaching the full log rather than excerpts so the surrounding context is preserved.
*** This bug has been marked as a duplicate of bug 521954 ***
(In reply to Vlad Zahorodnii from comment #2) > > *** This bug has been marked as a duplicate of bug 521954 *** It is NOT a Duplicate
DESCRIPTION After cold boot and login, my triple-monitor Plasma X11 session sometimes comes up with the display layout/sizing wrong. Logging out and back in, or restarting KWin, can restore the correct layout. This appears separate from Bug 521954 / the resolved logout teardown crash. The linked fixes for that bug appear to address shutdown/teardown ordering and RenderLoop/workspace lifetime issues. My remaining problem happens at cold boot/login/display initialization. SYSTEM Fedora 44 KDE Plasma X11 session kwin-x11-6.7.0-1.fc44.x86_64 NVIDIA driver 595.80 Triple-monitor setup with mixed refresh rates SYMPTOM On cold boot/login, display layout/sizing can be wrong. After logout/login or KWin restart, the layout can recover. RELATED LOG EVIDENCE On a prior event, kwin_x11 produced SIGABRT coredumps. On a later boot, plasma-kwin_x11.service stopped/restarted and logged OpenGL context cleanup warnings such as: Could not delete render time query because no context is current Could not delete framebuffer because no context is current In that later event, KWin restarted successfully as /usr/bin/kwin_x11 --replace. NOTES I am filing this separately because the main symptom is cold-boot/login display initialization, not a logout/shutdown teardown crash. If this belongs under the existing resolved bug instead, please let me know.
This doesn't look like a crash, based on your description and the logs you've provided. If there is actually a crash, we need a backrace of it. Please attach a backtrace of the crash, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Also, we'll need some specific logs for kwin. Please run the following command when this happens, and paste the output into this report. kscreen-doctor -o Also, attach the output of drm_info. Thanks! (If the command isn't found, you'll need to install it from your distro)
I captured the requested logs while the center display was still in the bad cold-boot / first-login state, before logging out or restarting KWin. Attached: * drm_info_bad_cold_boot_2026-06-25_165543.txt * kscreen-doctor_bad_cold_boot_2026-06-25_165543.txt * xrandr_bad_cold_boot_2026-06-25_165543.txt A normal graphical logout/login fixes the display state. I did not use Ctrl+Alt+F3/F2 for this reproduction.
Created attachment 193705 [details] Compressed logs captured during bad cold-boot / first-login display state before logout I captured the requested logs while the center display was still in the bad cold-boot / first-login state, before logging out or restarting KWin. Attached zip contains: - drm_info_bad_cold_boot_2026-06-25_165543.txt - kscreen-doctor_bad_cold_boot_2026-06-25_165543.txt - xrandr_bad_cold_boot_2026-06-25_165543.txt A normal graphical logout/login fixes the display state. I did not use Ctrl+Alt+F3/F2 for this reproduction.
Thanks. The kwin developers will need to take a look.
Thank you Tracey I mean I'm just assuming this your first name. I know you got bigger fresh fish to fry out there but this is a strange bird. Right after I ran those terminal commands and uploaded the files, I logged out and then log right back in and everything seemed fine. I don't know if that helps or not but it seems to assemble itself correctly after a simple log out and login after the initial cold boot
Sorry / using voice recognition = sloppy spelling and grammar.
This should be fixed in Plasma 6.7.2; see https://invent.kde.org/plasma/kwin/-/merge_requests/9443.
Created attachment 193744 [details] Recovered logout/login output logs for comparison with bad cold-boot state Thanks Earlier I attached the BAD cold-boot state files: - kscreen-doctor output - drm_info output - xrandr output I then logged out and back in, which restored the display layout visually, and captured the RECOVERED state files as well. One important observation: the BAD cold-boot `kscreen-doctor -o` output and the RECOVERED logout/login `kscreen-doctor -o` output appear identical. They report the same enabled outputs, priorities, modes, scales, and geometries. So the visible problem may not be reflected in KScreen’s logical output configuration. I am attaching the recovered/logout-login files now for comparison.
Thank you. I’m currently on Fedora’s kwin-x11-6.7.0-1.fc44 package, so I do not appear to have the 6.7.2 fix yet. I’ll retest after Fedora ships Plasma/KWin 6.7.2 and report back if the issue remains.
I reviewed KWin MR 9443, referenced as the Plasma 6.7.2 fix for Bug 521909. That MR addresses RenderLoop/workspace and EGL teardown during compositor shutdown. It does not modify output discovery, KScreen configuration, DRM modesetting, framebuffer initialization, or cold-boot startup ordering. My remaining issue occurs during first-login initialization before any logout, and the bad and recovered kscreen-doctor -o outputs are logically identical. Therefore MR 9443 may fix the associated logout crash, but it does not appear to address this report’s visible cold-boot output corruption. I will still retest 6.7.2 for confirmation. MR 9443 fixes My remaining issue ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Crash during KWin shutdown/logout Wrong rendering after cold boot/first login ───────────────────────────────────────── ───────────────────────────────────────────────────────── Missing workspace() guard in RenderLoop Logical output configuration is already correct ───────────────────────────────────────── ───────────────────────────────────────────────────────── Compositor teardown ordering Visible output differs despite identical geometry/modes ───────────────────────────────────────── ───────────────────────────────────────────────────────── EGL context destruction Logout/login rebuilds working display state The key commit explicitly says: “At shutdown, the compositor is destroyed after the workspace…” None of MR 9443’s six changes touches: - DRM connector discovery - Output geometry or modes - KScreen configuration application - Initial framebuffer setup - Multi-monitor startup ordering - NVIDIA display initialization
(In reply to Ed from comment #14) > I reviewed KWin MR 9443, referenced as the Plasma 6.7.2 fix for Bug 521909. Thanks for reviewing things and how the MR relates to the issues you're seeing. Each bug report needs to be focused on one problem. The MR addresses the KWin crash. The other problems you've outlined reference multiple distinct issues, which need to be reported in separate bug reports. See [https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket](https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket) for more explanation. Please open new reports as appropriate to the bugs you still see on your system. Thanks!
I think Nate has an open bug report that you may have not seen. I'm sorry I posted stuff the wrong area. He ask me to upload some items, and so I did. Here's where I think the new issue is being addressed https://bugs.kde.org/show_bug.cgi?id=522149