Description of problem: When SDDM Wayland is running in a multi-display system, Version-Release number of selected component (if applicable): 5.27.1-1.fc38 How reproducible: Always Steps to Reproduce: 1. Set up a VM simulating two displays 2. Install Fedora KDE 3. Boot into installed environment Actual results: Only one of the displays has the SDDM login window. Expected results: All displays should have the SDDM login window. Additional info: Original upstream bug: https://github.com/sddm/sddm/issues/1672 The SDDM fix is already in, we need the layer-shell-qt fix too.
Proposed as a Blocker for 38-beta by Fedora user ngompa using the blocker tracking app because: This violates the criteria: "A system installed without a graphical package set must boot to a working login prompt without any unintended user intervention, and all virtual consoles intended to provide a working login prompt must do so." I assume the implication is that physical consoles are also covered under this.
(In reply to Fedora Blocker Bugs Application from comment #1) > Proposed as a Blocker for 38-beta by Fedora user ngompa using the blocker > tracking app because: > > This violates the criteria: "A system installed without a graphical package > set must boot to a working login prompt without any unintended user > intervention, and all virtual consoles intended to provide a working login > prompt must do so." I assume the implication is that physical consoles are > also covered under this. Blech, wrong quoted criteria. This violates "Shutting down, rebooting, logging in and logging out must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops." It doesn't show up properly on all displays, which can be a problem when you don't know which display is primary in Wayland.
FEDORA-2023-13c2d4f2e6 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-13c2d4f2e6
FEDORA-2023-13c2d4f2e6 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-13c2d4f2e6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Proposed as a Freeze Exception for 38-beta by Fedora user frantisekz using the blocker tracking app because: FE may be more appropriate here.
Counting +1s for blocker as also +1 for FE, we have +8 at https://pagure.io/fedora-qa/blocker-review/issue/1051 , so marking accepted FE. Blocker vote is more split, leaving open for now.
I was facing this same behavior on my fisical F37 installation. After upgrading it to 5.27.2-1 ( https://bodhi.fedoraproject.org/updates/FEDORA-2023-3548d2815a ) now this bug is fixed.
FEDORA-2023-13c2d4f2e6 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.