Created attachment 1957648 [details] journalctl -b for configuration with both monitors Description of problem: I have system with two monitors: Main monitor - AOC275QXL (HDMI 2560x1440 FreeSync) Auxilary monitor - Nec2090 (DVI-D 1600x1200) Video HD4550 (HDMI+DVI-D) Just before start SDDM my AOC275QXL show "No signal". How reproducible: always Steps to Reproduce: 1. Power on system - picture on both monitors 2. Select fedora in grub - picture on both monitors 3. View boot logs (rhgb disabled) - picture on both monitors 4. Start SDDM - picture only on auxilary monitor Actual results: "No signal" on main monitor after SDDM start. In KDE for X11 and Wayland modes main monitor show "No signal". Expected results: Both monitors can show picture in SDDM & KDE Additional info: In "KDE monitor settings" I can see both monitors. I can change resolution for main monitor, turn on/off "Main monitor switch", enable/disable monitor - no visual changes on main monitor (still "No signal"). Start system only on main monitor gor same effect - "No signal" after SDDM start This configuration normally worked before on F37. During F38 install (from scratch) installer worked on main monitor without problems.
Is SDDM itself using Wayland or X11? Is sddm-x11 installed, or sddm-wayland-plasma?
It's seems, that SDDM uses Wayland. How I can to check it? [root@megaboss ~]# dnf list installed "sddm*" Установленные пакеты sddm.x86_64 0.19.0^git20230404.e652433-1.fc38 @fedora sddm-breeze.noarch 5.27.4.1-2.fc38 @fedora sddm-kcm.x86_64 5.27.4-1.fc38 @fedora sddm-wayland-plasma.noarch 5.27.4.1-2.fc38 @fedora
Yep, looks like you're using SDDM with Wayland. In that case KWin is involved so it may be a KWin bug. But first... are you using an AMD GPU? If so, it could be the following driver bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2497.
No, definitely not https://gitlab.freedesktop.org/drm/amd/-/issues/2497. In that bug problems with second monitor after sleep. I tried to start my system with main monitor only, but got same effect - "No signal". May be I should to install sddm-x11 package? But how to switch SDDM to use X11? What If I switch "DisplayServer" setting to "x11" in /etc/sddm.conf? In this case, we will know - is there a problem in Wayland?
Switching to x11 for sddm can be done with "sudo dnf swap sddm-wayland-plasma sddm-x11" and reboot.
Alternatively, you can drop in a file "sddm-x11.conf" to /etc/sddm.conf.d with the following contents: """ [General] DisplayServer=x11 """
Interesting... With x11 enabled in SDDM I have both monitors working. Than, if I load KDE in x11 mode, both monitors working too! But if I load KDE in wayland mode, my main monitor show "No signal". Re-enter in KDE after that in x11 mode did not help. Only system reboot enable main monitor again. At least now I can work on both monitors. :) And we know that Wayland has some issues with my configuration.
This is starting to feel like a KWin issue. Maybe submit a bug upstream at https://bugs.kde.org/enter_bug.cgi?product=kwin&component=wayland-generic.
Create bug report in upstream https://bugs.kde.org/show_bug.cgi?id=468744
Sorry, can not reproduce this bug anymore. May be last updates fix this somehow. Both modes (X11 & Wayland) work properly in SDDM and KDE now.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.