<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - two external screens permanently go blank on HP EliteBook Folio G1" href="https://bugs.freedesktop.org/show_bug.cgi?id=108462#c73">Comment # 73</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - two external screens permanently go blank on HP EliteBook Folio G1" href="https://bugs.freedesktop.org/show_bug.cgi?id=108462">bug 108462</a> from <a class="email" href="mailto:johannes@sipsolutions.net" title="Johannes Berg <johannes@sipsolutions.net>"> Johannes Berg</a> <pre>Actually, it got MUCH worse. Not only do screens (all, including the internal) keep flickering/turning on and off with that kernel like before, but it also loses one of the external screens entirely. What happens is that with this new kernel, going into gdm3 turns off both external displays. This does NOT happen with gdm3 with a different kernel, including rc1, there they are turned on (and keep flickering) in gdm3. When I log in, only one external display is turned on again. Note that a similar behaviour happened before - if I were warm-rebooting the machine, only one external display would turn on after the reboot. A cold reboot turned on both external screens reliably. So the "can only turn on one of the two after two had been turned off" was already there, but what's new is that without any changes other than the kernel, gdm3 now turns off both external screens on the login screen. Much worse, because now with this kernel I can only use one external screen at all (except during boot, well...)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>