Chrome Dev 69.0.3486.0
Disappointed that the networking bug where VPN connections are not extended to the container (https://bugs.chromium.org/p/chromium/issues/detail?id=834585#c10) isn’t fixed yet in this release. It’s the one issue stopping me from using the Pixelbook as my primary laptop 
Extending to an external HDMI monitor works again… No more washed out display!
Terminal app now has a Shut Down Linux option but only when you right click in the drawer.
Appears to shut down the termina vm as I couldn’t vsh termina after I ran it… so essentially a vmc stop termina
This commit should be interesting to many … now *.linux.test is a secure domain for Chrome OS.
lxc & lxd are now updated to version 3.0
(termina) chronos@localhost ~ $ lxc --version
3.0.0
(termina) chronos@localhost ~ $ lxd --version
3.0.0
The title says dev channel but the post says beta channel 
on the chromereleases site I mean.
Oh look, now literally no linux apps will open for me, including the terminal. Cool.
Edit: Another reboot did it for me as well. I noticed when I opened the terminal first, the first time it actually said error and closed (too quickly to see the full error message). Then upon reopening, it works and all my Linux apps do as well.
One good thing about the update, I no longer have to disable blink-heap-incremental-marking
Hmmm, I also got a firmware update with the latest CrOS update too -
- OS Release : Linux 4.4.138-14447-g7e90a0e25e5e
- Kernel Rel.: 4.4.138-14447-g7e90a0e25e5e
- CROS Root : ROOT-B (/dev/mmcblk0p5)
- OS Vers. : 10820.0.0
- Browser Ver: Google Chrome 69.0.3473.0
- ARC Vers. : 4861648
- CrOS FWID : Google_Eve.9584.151.0
+ OS Release : Linux 4.4.139-14472-g6853af561948
+ Kernel Rel.: 4.4.139-14472-g6853af561948
+ CROS Root : ROOT-A (/dev/mmcblk0p3)
+ OS Vers. : 10866.1.0
+ Browser Ver: Google Chrome 69.0.3486.0
+ ARC Vers. : 4884711
+ CrOS FWID : Google_Eve.9584.160.0
Smart Lock was mostly broken in the prior build – it looked like it was trying but it never found my phone. Smart lock is completely broken for me in this build – no lock with a spinner around it at all on my login screen.
Has anyone tried this new build with the Samsung Chromebook Pro? I saw that VMX in Skylake has been enabled a few patches ago for glados machines.
This build enables crostini for the HP 14-ca020nr. It’s a US model sold in retail channels that from what I’ve been able to tell is an almost-but-not-quite HP 14" G5. The G5 seems to have better specs. It identifies as ‘Snappy’/Kernel 4.4 and is a 4gb/N3350/16GB Chromebook sold in retail channels like Office Depot and Walmart for around $229.00USD-$249.00USD and looks pretty much identical to the G5, but has lower specifications and doesn’t claim to be waterproof/water resistant or built to milspec, but does charge off of usb-c.
Edit: model number corrected to HP 14-ca020nr
Looks to me like the pulled back the 69.0.3486.0 release from dev channel.
For anyone having the problem of Terminal not launching anymore, even with the latest components installed, I have a workaround:
vsh termina
run_container.sh --container_name penguin --shell --user
Once in the container, sudo reboot
Wait a couple of seconds and then a Terminal window appears, and everything runs normally after this.
It’s a bit disappointing that the chromereleases blog reports that version 69.0.3486.0 / 10866.1.0 is out in the wild:
And yet both the cros-updates & cros-omahaproxy servers still report verson 69.0.3473.0 / 10820.0.0 as current:
Where are we supposed to get reliable info. ???
Working fine here with VSCode
Seems to be stable for me, I have not noticed any major changes
Can someone check and see if this release still has the screen “flash” fix? Meaning, when you are at the “desktop” and open the notification menu for instance the screen would “flash” and saturation would become much more dynamic, some are saying it’s been fixed, can someone confirm?
Thanks!
The autocomplete/popup window system crashing bug isn’t fixed, at least not for me using Goland/IntelliJ.
EDIT: complained too soon; thanks to the comments below, after updating cros-termina and rebooting a couple of times everything seems to work!
Anyone else lose docker after a powerwash?