This also happens with sublime text and evolution email client

Some comments about this on Reddit asking if I just wasn't waiting long enough made me think I should add some more details here.

I've been using Crostini awhile, so I know you have to wait a few seconds to get the container initialized the first time.  The key there is that while it is initializing you see the spinning circle on top of the icon.  I don't think I've ever experienced the issue I described upon the first time trying to open the app.  It usually happens after the app has been used and closed.  

You can tell because the first time you open an app or the penguin terminal, you do get the spinning circle on top of the icon.  When the issue I describe happens, the icon briefly changes color on the first click but never opens.  After a second click you get the brief spinning circle and the app opens up.

Hope this is useful.

Yes, that describes what happens exactly

Does this happen with all Crostini apps? Could you check the container logs (sudo journalctl in the container) to see if a message is actually being sent through (something like "Received request to launch application in container")? Thanks!

I can confirm that there is no entry on the first attempt to start GIMP but there is an entry "Received request to launch application in container" on the second attempt. Is there any more info you need (This is on a PixelBook running dev)

Yes, same here. First click did not show any message in the log, second click showed up as "Received request to launch application in container" (and then the app actually opened, too).

Often happens after the Pixelbook has been asleep, I open the lid, unlock, and then try to start a Linux app (gnome terminal) from the dock.

Pixelbook on stable version 71.0.3578.98.

Oh, and the container is already running. Other Linux apps are already open.

Based on comment #7, nothing incorrect seems to be happening in the container (e.g. Garcon error), so this seems like an issue in Chrome. Can you look?

Also, rmcneil321@, can you file feedback (three dots->Help->report an issue) and notify this bug after you've done so. We will be able to look at logs. Thanks!

Feedback filed.  I referenced this issue.
Let me know if you need anything else.
Thanks!

 Issue 922227  has been merged into this issue.

I also submitted a feedback on my 500e so you can pull data from this one as well. 

In terms of logs, I had the issue happen a few minutes ago when trying to open PCManFM.

From the logs I'd guess that something is stopping working as a result of putting the device to sleep, as from the logs it seems like the first request after waking the device is failing CreateLxdContainer due to "Endpoint read failed" (which is a grpc error).

While we investigate, could anyone confirm/deny that this only occurs at most once waking a device from sleep? Thanks!

I wasn't able to repro just now on M73 canary, but this occurred a lot for me over the holidays. While I can't be 100% positive, I would believe that it only happened on the first launch post-sleep.

I'm on stable channel and this happens every time for me. It only happens when launching the Terminal. When launching other Linux apps that I've installed, I only have to click the icon once for the app to open.

I am on stable too. Has happened to me for a few Linux apps, not limited to Terminal. Second click always starts them, and from then on every click launches.

I am 99% sure it has to do with wakeup from sleep, but when I try to deliberately put it to sleep just to reproduce the issue, and wake it up right away, the issue does not occur. Perhaps it has to sleep for at least a minimum amount of time before the issue gets triggered.

I have seen it many times, usually after I had the Pixelbook closed, stowed away, moved to a different location, then open it up after a longer time has passed.

re comment 14
The suggestion that it might be related to coming out of sleep is logical.  I will try to make a note of whether that is the case.