looks like this https://chromium-review.googlesource.com/1176182


Dom, can you take a look? Let me know if you want to revert.

Fix is up: https://chromium-review.googlesource.com/c/chromium/src/+/1188343

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4e71dae7cedd62d6fc123939d8e4929bebe6e706

commit 4e71dae7cedd62d6fc123939d8e4929bebe6e706
Author: Dominik Laskowski <domlaskowski@chromium.org>
Date: Sat Aug 25 04:12:45 2018

exo: Do not commit if widget creation is deferred

Bug:  877254 
Test: gtk3-demo
Test: exo_unittests
Change-Id: Iec316067589088e85dec3429df4fe9f5a5604a65
Reviewed-on: https://chromium-review.googlesource.com/1188343
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586116}
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/client_controlled_shell_surface.cc
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/client_controlled_shell_surface.h
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/shell_surface.cc
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/shell_surface.h
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/shell_surface_base.cc
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/shell_surface_base.h
[modify] https://crrev.com/4e71dae7cedd62d6fc123939d8e4929bebe6e706/components/exo/shell_surface_unittest.cc

 Issue 877370  has been merged into this issue.

 Issue 877637  has been merged into this issue.

 Issue 879234  has been merged into this issue.

 Issue 879236  has been merged into this issue.

I'm confused. How was this patch released today broken but was fixed a week ago?

Commentor #10

IIUC I believe the issue noted in #c1 per CL 1176182 landed in 70.0.3524.0
( https://chromium.googlesource.com/chromium/src/+/5b1287f22fd78da6b7600e73d7dcbd6b9d8180c5/chrome/VERSION )

And the fix for it noted in #c2 per CL 1188343 will land in 70.0.3533.0
( https://chromium.googlesource.com/chromium/src/+/4e71dae7cedd62d6fc123939d8e4929bebe6e706/chrome/VERSION )

I have a Pixelbook, running on the dev channel, and my device is telling me it is up-to date. Any suggestions on how to pull the fixed version? 
chrome://settings/help is showing me (Version 70.0.3532.8 (Official Build) dev (64-bit))

How is this closed before the build came out that experienced the problem.  I think this oversight may be causing Google to ignore a critical bug between releases rather than push a new dev channel update.

Right, the fix landed in 70.0.3533.0, which started propagating to canary images today. It will be included in the next dev channel push, which is slated for early next week, probably Wednesday due to the holiday.

Are the releases on dev channel tested for basic functionality? It seems that they are not, at least judging by this 70.0.3532.8 update. 

It would be good to know the exact policy on this.

This dev channel is the only way to run Crostini on Google's Pixelbooks (and several other ChomeOS devices, IIRC), in case one might wonder why one sees so many complaints here.
 

As a work around for now. Install LXDE using tasksel and install tightvncserver.

Then use VNC viewer for Chrome to access your container.

Google promised all this amazing stuff with Crostini so of course we all jumped to the dev channel. But then stuff like this without prioritization on shipping the fixed version (or even any communication why beta channel got it and then rolled it back). 

I think maybe the dream of ChromeOS dev machines just lost a little credibility. Back to the Dell XPS! :(

I know this is a bug tracker. I know it's an unstable build. But we don't have any other place to let Google know our disappointment so I just thought I'd post it here. I made the unfortunate decision to bring my pixelbook as my main machine athie conference to use to launch my products beta. Oops. 

@Comment 17 - we all need to remember that the dev channel by it's definition is considered unstable. I cannot recommend using anything aside from stable or beta on a critical/primary machine. Things will break on occasion but this is the cost of being able to test all of the new and exciting features. I will agree that breaking crostini is a step back but it should be fixed in a few days.

For sure. I 100% acknowledge this is my fault. It's just... Preaching to the choir I know. Google talked about this with much fanfare and it's still only on dev channel, so it's special circumstances that so many or us followed their hype train to end up here :)

I guess I know a thing or two about  large open-source projects, and I
cannot but remark that the release management on this one is seriously
deficient.

E.g. a little while ago on some devices Canary was behind Dev.

And this current issue has caused in particular Pixelbook users so much
trouble, as noone tried to pick up a reasonably stable Dev version and make
it Beta --- indeed, there is no Crostini on Beta for Pixelbooks.

Last but not the least, "unstable" != "totally broken", really. In the
absense of version rollback functionality, users are at your mercy, and
having huge regressions on de facto Beta (and yes, Dev on Pixelbooks is de
facto Beta) ought to be avoided.

Since this bug is so significant, can we get an early push of the fix to the dev channel?

@Comment 18 - Yes, we all remember that dev channel is considered unstable, but a version rollback must be an option too

Issue 880100 has been merged into this issue.

Chrome Stable 69 was released today, I would expect 71 for dev to be out soon which will come with the patch. Hang in there a bit longer.

Setting the right labels.

Apps are working in eve, setzer,bob and kevin on 11021.5.0, 70.0.3538.7

No updates...!!
How long to wait for the update.?

It is expected sometime this week, it can be as early as today. No date was ever promised

Even after 1 week no updates.. 10 years of Chrome... mmm

As you saw in #68, the problem has been fixed and verified, we might have an update anytime in this week.

Yes! It's fixed

Updating...

Successfully updated to version 70.0.3538.7.

I confirm that Linux applications are working fine here.

Thanks for confirming everyone! 

 Issue 879819  has been merged into this issue.