<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Intel GeminiLake corruption at top of screen caused by fbc" href="https://bugs.freedesktop.org/show_bug.cgi?id=108085#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Intel GeminiLake corruption at top of screen caused by fbc" href="https://bugs.freedesktop.org/show_bug.cgi?id=108085">bug 108085</a> from <a class="email" href="mailto:lui@fgcint.com" title="Luigi Cantoni <lui@fgcint.com>"> Luigi Cantoni</a> <pre>Now it gets confusing. It appears I was wrong my fix is not a fix. It depends on what order you do things and also a bit on what is on the graphical screen as to if you see it or not. The good bit is I appear now to have a method to make it fail etc (and sort of work). If I have ctrl-alt-F1 with the graphical login screen ctrl-alt-F2 is a logged in session ctrl-alt-F3 is the character based login. This is the screen display with the problem visible on it. Swap from F1<->F3 100% looks OK Swap F1<->F2 100% OK (always was and never had an issue) Swap F2<->F3 and my problem is there. Do F2->F3 (problem there) do F3->F1->F3 problem not there Or do F2->F1->F3 problem not there. It fixes up the display if I go through the F1 (graphical login) screen. I just re-tested my machines with my X11 conf file there and not there and the behaviour is as described above. The file makes no difference. I had not noticed that behaviour before as I normally go from F2-F3 and back again without going through F1. Also something I have noticed is that when I swap out of F2 for a moment the screen goes silly in the top left with the graphical data and F3 does not clear it but F1 seams to clear it out. My guess is the swap screen code is writing the data out (maybe only as temporary buffer) and F1 (as an initialisation code) clear that temporary area out) and that is what is happening and why F1 fixes it. Might have been helpful to know that.</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 assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>