https://bugs.kde.org/show_bug.cgi?id=522149
Bug ID: 522149
Summary: Cold boot/login applies wrong triple-monitor
layout/sizing on NVIDIA X11; logout/login restores
output configuration
Classification: Plasma
Product: kwin
Version First 6.7.0
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: multi-screen
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 193678
--> https://bugs.kde.org/attachment.cgi?id=193678&action=edit
KWin X11 diagnostic bundle: service status, current-boot KWin journal excerpts,
prior kwin_x11 coredump summaries/details, and NVIDIA/DRM kernel log excerpts
I selected the multi-screen component because this is an X11 triple-monitor
issue; the output configuration component appears to be marked Wayland-only.
===
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.
--
You are receiving this mail because:
You are watching all bug changes.
