<div dir="ltr">I've been troubleshooting a problem for some time where chrome browser windows fails to properly go to full screen.<div><br></div><div>I posted the question below on <a href="https://unix.stackexchange.com/questions/305376/chrome-on-gnome-randomly-fails-to-go-full-screen">StackExchange</a> and a response pointed to this as graphics driver issue.</div><div><br></div><div>After almost wearing out google, setting boot time options to enable i915 debugging, digging through dri and tracing/events/i915 in the debugfs, I'm looking for a next step.</div><div><br></div><div>Here are the details:</div><div><br></div><div><div>I have Centos 7 running the 4.7.1 kernel (elrepo-ml) on an intel NUC with intel HD Graphics i915.</div><div><br></div><div>I'm trying to run Chrome in full screen mode `google-chrome --full-screen --kiosk http:192.168.2.20` (just a local server with the default apache2 page) and it works most of the time, but randomly (every second to fifth time) it doesn't fully display the page and looks like this:</div><div><br></div><div><img src="cid:ii_is9kffph0_156bf02a30e3cd8b" width="544" height="306"><br><br></div><div><br></div><div>You can see that chrome "thinks" it's full screen because of the way that the page is rendered.</div><div><br></div><div>One interesting behavior is that if I ALT-TAB to another window (hidden in the screen shot), then the page will render full screen under the window just brought to the front.</div><div><br></div><div>There is nothing interesting in X.org logs -- the same lines are repeated in both successful and unsuccessful full-screen attempts. (The same lines are logged in /var/log/gdm/ when gdm is in debug mode).</div><div><br></div><div>`[352467.250] GetModeLine - scrn: 0 clock: 148500</div><div>[352467.250] GetModeLine - hdsp: 1920 hbeg: 2008 hend: 2052 httl: 2200</div><div>[352467.250] vdsp: 1080 vbeg: 1084 vend: 1089 vttl: 1125 flags: 5</div><div><br></div><div>I've tried to force a refresh (which may be what ALT-TAB) programatically with xrefresh, but that doesn't' make any difference.</div><div><br></div><div><br></div><div>System details:</div><div><br></div><div>- Hardware: Intel NUC NUC5CPYH Processor</div><div>- Intel Celeron N3050 with Intel HD Graphics</div><div><br></div><div>Driver:</div><div><br></div><div>$ modinfo i915 | grep version</div><div>srcversion: 4F4A9108A6D94B8919E3154</div><div>vermagic: 4.7.1-1.el7.elrepo.x86_64 SMP mod_unload modversions</div><div><br></div><div>Hardware:</div><div><br></div><div>$ dmesg | egrep "i915|[Gg]raphic"</div><div>[ 0.000000] Reserving Intel graphics stolen memory at 0x7cf00000-0x7eefffff</div><div>[ 2.356158] [drm] Memory usable by graphics device = 2048M</div><div>[ 2.498705] [drm] Initialized i915 1.6.0 20160425 for 0000:00:02.0 on minor 0</div><div>[ 3.284294] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device</div><div>[ 6.301736] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])</div><div><br></div><div><div>What could be causing this behavior and what can I do to consistently get a full screen image?</div></div></div><div><br></div><div>Thanks</div><div><br></div><div>Mike</div></div>
<br>
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)">CONFIDENTIALITY NOTICE: </span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)"><br></span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)">The information in this communication, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. If you are not the addressee or if you received this communication in error, you are hereby notified that any review, retransmission, dissemination or other use of, or taking or any action in reliance upon, this information is prohibited. If you did receive this communication in error, please destroy it, all copies and any attachments, and notify the sender as soon as possible. The individual sender of this e-mail is responsible for its content, and EXOS does not assume any legal liability or responsibility for the accuracy, completeness or usefulness of any information, product, or process disclosed. Further, any comments, statements or opinions expressed by the author in this communication do not necessarily reflect those of EXOS.</span>