UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10718.13.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.15 Safari/537.36
Platform: 10718.13.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. Set up a VM/container with crostini
2. run "sudo apt-get install yakuake" or "sudo apt-get install guake" in the container
3. Run yakuake or guake and change the default hot key to something other than F12 since most (all?) chromebooks don't have an F12 key.
4. Press the hotkey you chose.
4. Press the hotkey you chose again.

What is the expected behavior?
2. When yakuake or guake is visible, pressing the hotkey causes its window to disappear (usually as a slide-up animation into the top of the screen, but this can be configured for different effects).
2. When yakuake or guake is hidden, pressing the hotkey causes its window to appear (usually as a slide-down animation from the top of the screen, but this can be configured for different effects). 
3. Apps like yakuake and guake shouldn't appear in the shelf.

What went wrong?
1. Yakuake and Guake display in a window in the middle of the screen rather than as a bare (no window chrome) pane at the top of the screen.
2. Pressing the configured hotkey to hide the terminal window only seems to work when the terminal window has focus.
3. Pressing the configured hotkey to hide the quake-style terminal window seems to close the application (icon is removed from the shelf). However running "pgrep yakuake" or similar inside of the Linux container shows that it is in fact still running.
4. Pressing the configured hotkey to show the quake-style terminal when the terminal is hidden has no effect.

Did this work before? N/A 

Chrome version: 68.0.3440.15  Channel: dev
OS Version: 10718.13.0
Flash Version: 30.0.0.113 

FWIW, this is also broken under Crouton.

My developer spidey sense is telling me that there are likely two problems here:

1. Chromium OS likely doesn't yet have facilities for detecting/proxying global hotkey combinations registered by Linux apps.
2. Either ChromeOS isn't respecting window position hints from Linux apps, or something is missing in the screen metadata presented to Linux apps which prevents them from setting their window position hints correctly, or both of these issues may be present.