Chrome Dev 69.0.3486.0

Anyone else having trouble unlocking with a PIN instead of the password? I’ve tried removing it and adding it back in, but I can’t seem to unlock my Pixelbook with a PIN.

edit: Even worse, because I changed to Password-only to unlock, and now when I try to add the PIN back it won’t save the change.

Anyone else have really laggy keyboard input in VSCode after this update?

Pixelbook Chrome OS Version 69.0.3486.0 Broke Smarklock and Pin Login

Can no longer login to my pixelbook using my Pixel 2 XL nor my pin. Only password works.

When using an external monitor, if my pixelbook lid is open then I close the lid… All apps are closed and I have to reopen everything again.

for most Chrome OS devices

Toshiba Chromebook 2?

It appears ngrok is broken (at least for me on pixelbook i5) after this update.

Hitting an ngrok generated url results in an endless loading cycle.

I have power washed a few times and downloaded the most recent version of ngrok multiple times as well.

It even fails in Crouton now.

Anyone else having weird routing issues?

For the record hitting the containers ip (e.g, 100.115.92.200) still works from chrome locally but I need to access the container from outside my network for testing and ngrok was the easiest method.

Pixelbook user on 69.0.3486 - Anyone else noticing any trouble with keyboard sensitivity? I’ve been on 69.0.3486 since it came out, for reason having trouble today with missing keystrokes. Not seeing a pattern yet - it’s OS wide (not limited to container-ed apps).

Anyone experiencing anything similar?

I too am disappointed that Chrome OS VPN is not supported in the container and it is now the only issue preventing me from using my Pixelbook instead of my windows surface book. I have been reporting this issue with each dev release since May and would like a work around or VPN tunnel support in the container.

I second this. Termux is much harder to use and lacking a lot of features I’d like to see.

You may be able to run the vpn from within the container. There could be some restriction I’m not aware of to run something like vpnc though.

I wonder if that is part of why the Palo Alto Global Protect Chrome App isnt working right for me? (Android one does, and both work on stable).

I’ve never had the washed out display issue, but occasionally I have to unplug and plug back in my monitor or else the screen will constantly shake and stutter. Though, once it’s displaying without shaking, it stays working until I log out or power on again. Anyone experience that also?

Woohoo! This has been killing my productivity. I use my pixelbook as a daily driver for development and not being able to use my 4k screen to have lots of tabs/windows was driving me nuts and slowing me down.

However… When I close my pixelbook all apps get closed if an external monitor is connected

Awesome, since I recently typed “vmc destroy termina” by accident (instead of stop), and it destroyed everything with no confirmation.

Sweet!

Did they also make linuxhost a secure domain?

Ooh…I feel like there was something important we wanted in 3.0 but I don’t remember.

oooh that is sweet, going to plat with that.

I’m experiencing the same, even after reboots. As far as I can see, I have the latest cros-termina component (10869.0.0).

P.S. You can check by going to chrome://components/

EDIT: Hmm, third reboot did it. Though, the one thing I did differntly this time was open the termina app instead of one of my linux apps directly. Further more, the first time I opened the termina app, it showed up for a second and quit, then the second time it worked (and after that I’ve been able to open my linux apps via icons).

EDIT2: Just confirmed after a few more reboots that after every reboot, I must do the following in this excact order (if you try to launch a linux app directly via its icon, things will not work until a reboot if I do not follow the below steps. Restarting termina seems to have no effect):

  1. Boot up
  2. Luanch terminal app and wait until it crashes
  3. Launch terminal app a second time. It will now work.
  4. You can now open any linux app by its icon. Rebooting will require the above steps to have to be re-done.

I haven’t seen any sort of bug report for this yet. Seems odd it’s only effecting some people

Try rebooting. This happens to me any time the system crashes.