## Problems With Low Density
The feature of this release of Chrome OS that i most looked forward to was the addition of support to change the display of Linux Apps to a lower density resolution. Unfortunately, it did not initially work on my Pixelbook.
First, I have found that I can only see the option to change an app to Low Density if it is on the shelf, I do not see the option when I right-click an icon in the Launcher.
Initially I tried the Low Density option for Krusader and Gnome File Manager and in both cases it did not work. I would select Low Density and then try to launch the app, which appears to try to work but the app never launches. Repeated attempts do not get the app to launch. Further, the Terminal app fails to work properly. The only solution is to restart the Pixelbook and disable the Low Density option.
I posted a question on Reddit 
asking whether anyone else seen this and one person posted a fix that involved shutting down the Linux container, starting it and then doing:
sudo apt update sudo apt dist-upgrade
Which appears to fix the problem on my Pixelbook. I still have to move the app icon to the shelf, but the after selecting Low Density it appears to stick.
Well actually, the Low Density option does not appear to stick with the app. Right now it seems that I have to manually select it every time I want to launch the app.
## Launching Second Container
I can now launch an app installed in a secondary container from the Launcher even if the container is not running. Prior this update I could not start apps from Launcher even though an icon was added; I had to manual start the container and start apps from the command line. Now, clicking a Launcher icon starts the app and if the container is not running it is started and then the app launches. I installed Gnome Terminal in the secondary container and can now launch it directly to use Docker.
## Google Assistant
A nice new feature is the addition of Google Assistant. You can configure assistant to listen for the "Ok Google" trigger phrase, but I have decided to not enable this function. Instead, I have configured Assistant to default to voice input so that when I press the assistant button on the keyboard it immediately starts listening, and I find this to be a very handy and intentional way to trigger assistant.