I can confirm this, as can many users on Reddit. Linux GUI apps are completely non-usable.

I'm upset about this one.

Xeyes windows transparent, so do other Linux apps....!!!!

Deleted: Screenshot 2018-08-30 at 3.13.38 PM.png 3.2 MB

	Screenshot 2018-08-30 at 3.13.38 PM.png 3.2 MB View Download

Please roll back the version asap. The latest dev build has many bugs with Android Apps / Crostini apps. Even opening Linux Files renders a transparent image. Any think that appears over the transparent application blurs with it. e.g. open files an then open chrome on top of it. Minimize chrome and watch the blur!

Just to point out, only 3 commits refer to changes in crostini.

https://chromium.googlesource.com/chromium/src/+/e96a626064602f3d8d29179fa96cc2f9f3222072

https://chromium.googlesource.com/chromium/src/+/e7776d510ab1353f54a420c2b857f3368fed47aa

https://chromium.googlesource.com/chromium/src/+/a250ec3ab9e982d9618127273c54dab7e56ff9ba

The last one seems most likely to be the problem, but I haven't been able to test this yet. I can also confirm that this is regression from 70.0.3524.2.

Same issue after the update..

Just an update, the last commit i pointed out was literally just the addition of a Typedef, which is unlikely to cause a bug.

Updating my comment here:

Looking like if I attempt to open an X application via the CROS terminal (accessing via vsh/lxc) the environment isn't properly forwarding to the Wayland host on ChromeOS.

```
pgebheim@penguin:~$ tilix

(tilix:1071): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(tilix:1071): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed

(tilix:1071): dconf-WARNING **: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY

(tilix:1071): dconf-WARNING **: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY

(tilix:1071): dconf-WARNING **: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY

(tilix:1071): dconf-WARNING **: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY
```

I suspect that we're seeing "transparent" apps because when you click you launch a linux app ChromeOS is setting up the window and then forwarding that renderer, but on the linux side the environment isn't working correctly so you end up with the app not actually rendering.

Just a thought/noticing.

Nope, I'm wrong here too -- these always appear to happen under Wayland with tilix.

Days like this when you wish your Chromebook wasn't your primary development environment. None of the changes I pointed out seem to reference UI. That doesn't mean none of them are the cause, but it almost doesn't seem likely that any of them are. I'm attempting to dig as deep as i can without running code but I can't promise much. Hopefully this is assigned soon.

A workaround is to follow the guide below and install the LXDE Desktop and access it with the VNC Viewer. 

http://linuxiumcomau.blogspot.com/2018/07/introduction-to-crostini-part-1-hp.html

I'm now running into the transparent window issue myself but the LXDE Desktop works fine.

Deleted: Screenshot 2018-08-30 at 7.41.19 PM.png 2.7 MB

	Screenshot 2018-08-30 at 7.41.19 PM.png 2.7 MB View Download

@timloh Respectfully, how was this fixed ~a week ago? Does this mean that it was just released today without the patch? Will there be a patched version rolling out soon? Can you provide any insight? 

Was working fine on the previous update for me.   Glad to see I am not the only one having this issue. Nothing seems to work now :(

I have some problem, after update chrome os v69(dev channel) to v70(dev channel)

 Issue 879350  has been merged into this issue.

 Issue 879124  has been merged into this issue.

 Issue 879575  has been merged into this issue.

Can someone please either provide insight or reopen either this or 877254?

Either this needs to be reopened, or 877254, as I too am still having this issue, and my Pixelbook is telling me I am all the way up-to-date. 

I am too having this issue. Freshly updated, still no joy. Please reopen this one. 

 Issue 879583  has been merged into this issue.

 Issue 879273  has been merged into this issue.

Turns out this was fixed but the fix wasn't released. It will be fixed after 70.0.3533.0.

When will that be released? I just left on a trip with my pixelbook as my only computer to develop on. This is a huge problem and feels like it deserves a quick patch or some way around it immediately.

Sadly I did too. I know it's my fault for using unstable but it had been so
good for so long :(

My wife had to fly me in a new laptop for emergency code patches at this
convention

Issue seems corrected on canary at this time. 

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

Then use VNC viewer for Chrome to access your container.

This is already fixed in Canary... So why Google leave us in this situation since 2 days without any DEV update...?

This is already fixed in Canary... So why Google leave us in this situation since 2 days without any DEV update...?

I'll survive a few days in Crosh, but it really feels like something went wrong here. I'm on the dev channel because I decided that lxc containers on Pixelbook was the most secure environment to launch my application, and things were working well enough for my use case (Tilix; Sublime; Docker; NPM; DAT; Rasa Stack (Tensorflow)... and I never would have expected such a crazy regression.

But hey... been meaning to brush up on my tmux and vim.

Rock on.

@Commenter 20, It's unlikely we will know until it happens.

@Commenter 25
" ... Turns out this was fixed but the fix wasn't released. It will be fixed after 70.0.3533.0. ... "

Can we rely on a release for this fix on a reasonable time frame ??

Hi Google team, this is causing a big problem for me (and many other devs, as is evident in this thread). We urgently need a patch to fix this and get to a stage for linux apps are running. Please share an update on this ? Thanks

All, this issue was merged into  issue 877254  per #c13, please track it there.

Interested in a fix for this as soon as possible as well.  Just got my Pixelbook and am dead in the water before I really got started.

Look, it should come as no surprise that the Dev channel may have problems
from time to time. Obviously, don't buy hardware and start a production
development environment if that's the case.

That said, I am running just fine on the latest Canary release. The
transparent window problem is gone, and so far, so good.

Just devil's advocate, everyone here knows that dev can be unstable. But we
also don't think companies should release broken software and then go home
for the long weekend.

----
*- justin *| @framerate <http://twitter.com/framerate> | framerate.io

70.0.3538.7 has started rolling out to Dev

After updating to 70.0.3538.7, I can confirm X11/Wayland apps work again on my Pixelbook

Thanks for resolving this.  I've confirmed my Pixelbook is also able to render Visual Studio Code again. 

As much as I've been a thorn complaining, I really appreciate you guys
fixing this. Very eager to see this come to beta and stable so we can
spread the love of Chrome OS to all our dev friends!

<3

----
*- justin *| @framerate <http://twitter.com/framerate> | framerate.io

Successfully updated to version 70.0.3538.7.

I confirm that Linux applications are working fine here.