Wednesday, February 13, 2019

Beta Channel Update for Chrome OS

The Beta channel has been updated to 73.0.3683.32 (Platform version: 11647.28.0) for most Chrome OS devices. This build contains a number of bug fixes, security updates and feature enhancements.

If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Cindy Bayless
Google Chrome

Labels: ,

15 Comments:

Blogger LarryT said...

Please address this issue,if not already done with Video streaming VIA Videostream app for Chrome.(Lenovo Yoga laptop)I use this app for streaming movies from my movies library on my external drive. The app did not work until I contacted tech support at VideoStream.
Here was their fix:
Google Chrome recently released an update that changes the UI of the casting function, this causes the "blurry" screen issue when trying to choose a casting device or a video. This issue occurs on the Google Apps version of Videostream. We have logged the bug with Google and are waiting to hear back. For now, the issue can be fixed by following these steps:

1. Go to chrome://flags/
2. Search "Views Cast dialog"
3. On the "Views Cast dialog" feature, change it from "Default" to "Disabled"
4. Search "Upcoming UI features"
5. On the "Upcoming UI features" feature, change it from "Default" to "Disabled"
6. You should see a prompt on the bottom left to restart chrome

7:07 AM, February 14, 2019  
Blogger Dave Chien said...

I think there may be a VPN issue with this release. I have a L2TP VPN set up to connect to my work, and I use the Microsoft Remote Desktop Android app to RDP into my servers after I connect to the VPN as-needed. I typically just let my HP Chromebook x360 14 (nami) sleep, but I have found that since this release, I am able to connect to the VPN but I cannot RDP to the server. I have to power off the Chromebook, restart it, and then connect to the VPN again in order to get it to work.

3:20 PM, February 14, 2019  
Blogger Unknown said...

I can't get login ! after input my password, the screen turn black, and I see the login screen again !

3:25 AM, February 15, 2019  
Blogger Unknown said...

Having issues with some Adobe Flash apps flickering black. They still work, but get in the way of productivity.

6:46 AM, February 15, 2019  
Blogger Unknown said...

I agree with @Dave Chien. Seeing same issue with L2TP VPN, but also other issues related to the VPN: I cannot access some sites that should be visible over a VPN connection (our GITLAB instance, for example). Looks like a routing table issue.

1:37 PM, February 15, 2019  
Blogger Rhakeios said...

Hmm, the latest update deleted my Gmail shortcut, but I found out how to put it back again. I wonder if it's deleted other shortcuts I haven't noticed yet.

1:49 PM, February 17, 2019  
Blogger LOAN SERVICES said...

Bent u op zoek naar een lening? Wij helpen particulieren en bedrijven leningen te verkrijgen voor bedrijfsuitbreiding en een nieuw bedrijf op te zetten, variërend van elk bedrag. Krijg een lening tegen een betaalbare rente. Heeft u dit geld / lening voor uw bedrijf nodig en uw facturen op te ruimen? Stuur ons dan nu een e-mail voor meer informatie. Neem nu contact met ons op via e-mail: allrisefinancial@gmail.com

8:26 AM, February 19, 2019  
Blogger  said...

Here I met the same issue with @Dave Chien. I am using shadowsocks for my VPN. If I turn off my VPN and turn it back on, no matter which page I try to open with chrome browser, it'll show "no internet". And there is no other solution but restarting the device and connect to my VPN again. I am using this chromebook in China which makes it even harder to ignore this issue. Please fix the problem ASAP. Thanks.

8:32 AM, February 19, 2019  
Blogger Unknown said...

There is an issue with managed chrome devices where you cannot launch the kiosk apps on managed chromebooks. The entire taskbar is locked upon powering on the device. You cannot click on Shutdown, Kiosk Apps, or System tray as they are all locked out until after you login.

We cannot function without access to the kiosk app folder on the taskbar. We currently have over 1000 devices that are basically useless for state testing at this time. Please look into this issue.

Thanks!

5:56 AM, February 21, 2019  
Blogger Nate Jones said...

Same exact issue as Unknown commenter. Lower menu bar is unresponsive at log in screen. The chromebooks that are not in the Beta Channel do not have this issue.


7:35 AM, February 21, 2019  
Blogger Unknown said...

I have the same issue with tack bar, kiosk app and the power button not working on managed chromebooks.

7:11 AM, February 25, 2019  
Blogger Scott Endicott said...

Our school district is also being affected. We have about 1000 also that have updated to 73 beta and now our taskbar (including apps/kiosk) is inaccessable. HELP!

7:51 AM, February 25, 2019  
Blogger Unknown said...

District with 8k+ chromebooks in use and required by our state to use kiosk mode for testing next week....

google spams us about not having sufficient chromebooks in BETA channel, so we move some into beta.... now we have 10% of our devices that can't use kiosk mode for anything.....

we need a fix for this yesterday. 73.0.3683.32 did not work 73.0.3683.48 does not work.

6:22 AM, February 26, 2019  
Blogger Scott Endicott said...

This may be helpful...
We disable public session kiosk on all our Chromebooks, even though we use kiosk apps. However, enabling public session kiosk seems to allow us to run other kiosk mode apps and the system tray is 'unlocked.' I've opened a critical case with Google and we'll see what happens. This was never the behavior prior to beta version 73.

12:36 PM, February 26, 2019  
Blogger Scott Endicott said...

Our 'plan B' is enabling public session kiosk temporarily on beta channel Chromebooks and forcing the state testing kiosk app on them (which does work).

12:39 PM, February 26, 2019  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home