Was this happening on the previous dev?

+1 to #1; if this was occuring in the previous dev push (69.0.3494.0) we'll leave as a beta blocker.  Need to bisect.   Also provide device details if possible (which Chromebook(s) was/were it/they)?  Thanks

AFAIK, at least three diff platforms were tested and all failed, so it might be all-arch affected.
Yes, we'll check if previous dev candidate was affected. The severity of this bug is not going to let fast bisect, as recovery is needed to fix the behavior. 

Let see if we see this problem on previous released (10888.0.0) build before bisect.   Will ctrl-shift-0 restore the display to default size?
 

Able to reproduce this issue using R69-10895.4.0 on Asuka, Hana, veyron_jerry, and kefka.

re: c#4

ctrl-shift-0 does reset the display size successfully.

Unable to reproduce this using M69-Dev 10895.4.0 using kevin device.

Able to reproduce this issue on M69_10888.0.0 build.

Thanks sontis@. Removing the RBD.

Using the keyboard shortcuts (ctrl/shift/- and ctrl/shift/+) will change the display size after several presses (up to 3 on jerry).  

However, even though the display size appears changed, the UI is still unresponsive until we execute ctrl-shift-0 to reset to default.

The original chrome session logs show:
...
[1:1:0724/154942.543105:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:0724/154943.254322:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:0724/154943.454943:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:0724/155015.816843:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1287:1299:0724/155652.680033:WARNING:screen_manager.cc(116)] Display controller (crtc=38) already present.
[1287:1299:0724/155652.682210:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=38 connector=60 origin=0,0 size=0x0
[1287:1299:0724/155653.014927:ERROR:drm_display.cc(186)] Failed to set gamma tables for display: crtc_id = 38


After playing with ctrl/shift/[-+0] I see other logs coming up like:

[1350:1378:0725/102923.836556:VERBOSE1:drm_util.cc(471)] Failed to get EDID blob for connector 32
[1350:1378:0725/102923.836801:WARNING:screen_manager.cc(116)] Display controller (crtc=21) already present.
[1350:1378:0725/102923.837591:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/display-subsystem.5/drm/card1 crtc=21 connector=32 origin=0,0 size=0x0
[1350:1378:0725/103113.960578:VERBOSE1:drm_util.cc(471)] Failed to get EDID blob for connector 32
[1350:1378:0725/103113.960809:WARNING:screen_manager.cc(116)] Display controller (crtc=21) already present.
[1350:1378:0725/103113.969565:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/display-subsystem.5/drm/card1 crtc=21 connector=32 origin=0,0 size=1366x768



Finally I was able to get the device unstuck and reboot successfully. The full log after the reboot are at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/867178

Re> Finally I was able to get the device unstuck 

I found that I can type with kb and chrome to navigate to web site. Checked again and it looks like ctrl+shift+0 does bring back the input and sane state to some good extent.