<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - screen behind docking station doesn't work properly during boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=108460#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - screen behind docking station doesn't work properly during boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=108460">bug 108460</a> from <a class="email" href="mailto:johannes@sipsolutions.net" title="Johannes Berg <johannes@sipsolutions.net>"> Johannes Berg</a> <pre>(In reply to Stanislav Lisovskiy from <a href="show_bug.cgi?id=108460#c4">comment #4</a>) > Would be nice to attach also Xserver and gdm logs to see if they got > correspondent uevents and got connector states updated properly. > There are no such problems with Ubuntu 16/18 at least with the same kernel. > I've seen a similar bug and the problem was that gdm sometimes simply didn't > initiate modeset for some connectors. Wait, I'm talking about boot, I don't think Xserver/gdm are relevant? This is what happens directly after grub, basically. You don't have anything but initramfs, I'd be very surprised if Fedora was putting Xserver and/or gdm there. Though perhaps I could check what happens if I make the boot non-quiet, and let boot messages scroll through - I suspect they will only show up on one external screen too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>