Tuesday, August 7, 2018

Stable Channel Update for Chrome OS



The Stable channel has been updated to 68.0.3440.87 (Platform version: 10718.71.2/3) for most Chrome OS devices. This build contains a number of bug fixes and security updates. Systems will be receiving updates over the next several days.
New Features
  • 802.11r Fast BSS Transition Support
  • Ability to use Select to Speak with touch/stylus only
  • Admin policy to enable/disable adding of native printers client side
  • Enabling/disabling ChromeVox through the side volume keys (tablets/convertibles)
  • High resolution image support in camera app
  • Introduction of Display Size settings
  • Material 2.0 dialogs and secondary UI on ChromeOS
  • Overview visual refresh and motion spec improvements
  • PIN sign-in support
  • Select-to-Speak ability to select specific text to be read aloud by highlighting the text, then pressing Search + s. This works in addition to the original behavior of pressing Search and clicking an item or dragging a box around content to be read aloud.
  • Support Child account as first sign-in
  • Two new shortcuts to toggle the magnifiers on/off

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).

Bernie Thompson
Google Chrome

Labels: ,

38 Comments:

Blogger Bruce D Ranger said...

Just updated my ASUS CN62 i3 to Version 68.0.3440.87 (Official Build) (64-bit) with a build date of Thursday, August 02, 2018. My Toshiba Chromebook 2 (2015) is still on Version 67.0.3396.99 (Official Build) (64-bit).

11:19 AM, August 07, 2018  
Blogger Jonathan Bardi said...

The updates roll out over a series of days. Different device models will often not receive the update on the same day. In fact, it could be up to a week or so between different models.

1:46 PM, August 07, 2018  
Blogger Sue said...

What happened to fixing the problem with Chromebook not waking up from sleep when you open the lid? Acer C720, have not received the update yet, but don't that fix in the list of bugs fixed.

1:59 PM, August 07, 2018  
Blogger SamH said...

The best way to know when a build is ready-to-download for your Chromebook is to check this spreadsheet:
https://cros-omahaproxy.appspot.com/
Find your machine in the sheet, and it will identify which dev, beta, or stable build is currently ready.

2:06 PM, August 07, 2018  
Blogger Nelson Garcia said...

My Acer C720 isn't accepting 68.0.3440.87. A powerwash didn't correct the problem, I'm waiting until the update icon appears before I file a bug report.

3:51 PM, August 07, 2018  
Blogger Sue said...

I left out a word in my post. I said I don't see the fix for the bug about Chromebook not waking up from sleep when the lid is raised, in the list of bug fixes in the update. My post was not about when my Acer C720 will get the update.

4:07 PM, August 07, 2018  
Blogger Nelson Garcia said...

So I waited until the update icon appeared on its own and restarted. My device still shows I'm on 67.0.3396.99.

4:16 PM, August 07, 2018  
Blogger 7of9 said...

This comment has been removed by the author.

5:06 PM, August 07, 2018  
Blogger Unknown said...

You can monitor your chromebooks updates with this small Android App: https://play.google.com/store/apps/details?id=ua.kyiv.heneraliuk.crosupdates

11:56 PM, August 07, 2018  
Blogger Unknown said...

This is the same as the beta version released last week, and which is still not installing on Acer C720s.

6:58 AM, August 08, 2018  
Blogger Unknown said...

Well, this update isn't completing on Acer C720 for me either: After the requested restart it's still on 67.0.3396.99 and the update tries to install again (and again etc).

8:01 AM, August 08, 2018  
Blogger Daniel Bautista de Cabo said...

Same issue here with an Acer C720p: it's still in 67.0.3396.99 even though I have upgraded several times...

10:44 AM, August 08, 2018  
Blogger Nelson Garcia said...

As per Jim Dantin at the Google Product Forum, there's a bug and it's being worked on.

11:26 AM, August 08, 2018  
Blogger photo_ted said...

I don't see any mention of Linux.

Starting in May many articles touted loading Linux in a VM on Chrome OS on some hardware (I have a Pixelbook) with stable support in 68.

Am I missing something? I don't even see how to install it.

2:20 PM, August 08, 2018  
Blogger Nicolò Santangelo said...

When this update is available for my acer chromebook 15 C85-571

4:36 PM, August 08, 2018  
Anonymous Anonymous said...

Please folks stop complaining about a update that's every one knows is coming in a week or two. That's very normal process as you must know by now.
As someone posted you can check your Chromebook here https://cros-updates-serving.appspot.com if you don't see an update for your Chromebook you probably get in next week 😀 my Acer 14 Chromebook nearly always gets it a week later when a new update arrived.

10:51 PM, August 08, 2018  
Blogger leo kooijman said...

Same issue here with an Acer C720p: it's still in 67.0.3396.99 even though I have upgraded several times...

Same problem here

1:55 AM, August 09, 2018  
Blogger pr said...

photo_ted Linux support was pushed back to Chrome 69

8:16 AM, August 09, 2018  
Blogger Jean-Francois Trehou said...

Same issue here with an Acer C720p: it's still in 67.0.3396.99 even though I have upgraded several times...

1:09 PM, August 09, 2018  
Blogger photo_ted said...

pr, thanks for the info. How could I have found that out myself?

3:28 PM, August 09, 2018  
Blogger Unknown said...

@Sue, I have the same issue, my Toshiba 2015 didn't wake from sleep after the last update, I still didn't get 68, so I'm hoping that we will get the update and it fixes the problem.
In the meantime I was running beta and it was working fine. I'll wait a few more days and then go back to beta.

11:09 AM, August 10, 2018  
Blogger Paul said...

Ridiculous...shelving access to external storage (e.g. microSD / USB) for apps until builds 69 or 70+. They are adding all these features when the one BIG feature that would make Chromebooks stupendously popular, they won't do. Makes ZERO sense...

4:32 PM, August 10, 2018  
Blogger bdpwsc said...

I'm with the other Acer C720 owners. Mine will not accept the 68 update. Keeps reverting back to the latest stable 67.

2:57 AM, August 11, 2018  
Blogger Paul said...

I have the Lenovo Flex 11 - 68 dropped today, but I am at work. Will have to check and see if it is doing the same thing when I get home, as it seems other models seem to be having issues with this build...here's hoping!

12:30 PM, August 11, 2018  
Blogger cvsprinter said...

C720 here. Still not accepting the update.

10:23 PM, August 11, 2018  
Anonymous Anonymous said...

Acer Chromebook 14 CB3 431 just got this update..

12:08 AM, August 12, 2018  
Blogger pssst3 said...

I don't like the new menu bar look for convertibles, having a search bar, tabs, and shortcut buttons that are 50% wider and taller than before.

While you can temporarily change this through chrome://flags "UI Layout for the browser's top chrome" set to "Normal", it's easier for me to just switch to full screen.

Ironically the result has been that I'm using Chrome browser menu bar less and shortcuts more. That's the same as what happened when the Shelf was Android-ified and the Launcher app groups were screwed up.

From what I can tell, the workings mode I'm now using is close to the earliest Chrome OS interface. Talk about a a[gainst leap backward!!

10:38 AM, August 12, 2018  
Blogger David Tingey said...

Same issue with Acer C720p: it's still at old 67.0.3396.99 even though I have upgraded several times and also trying resetting chromebook.

3:42 PM, August 12, 2018  
Blogger Unknown said...

Same issue with Google Pixel book : it's still at old 67.0.3396.99 even though I have upgraded several times and also trying resetting chromebook

7:20 PM, August 12, 2018  
Blogger Unknown said...

Hello, my Acer Chromebook 14 CB3 431 just got the Chrome OS 68 update but doesn't have any of the new features listed... like Material 2.0 and the new PIN sign-in support.

5:31 AM, August 13, 2018  
Anonymous Anonymous said...

I have a Chromebook Acer 14 CB3 431 and like someone write about the lack of some features as this update should bring. There's as i can see none features or anything else changed in this update.as i see it no change at all. I've tested beta and dev channel and none of the features from those channels are in stable channel. So this update is just for keeping us confused and more irritated as days goes by.😅

10:15 AM, August 13, 2018  
Blogger Unknown said...

I've only had this update for 2 days but so far it appears to have fixed the problem I had on my Tosh 2 2015 after the last update. It wouldn't wake from sleep, I'd have to shut it down by hand and then boot it back up so I was using it in beta. Since the update, so far, so good in stable, knock wood.

3:43 PM, August 13, 2018  
Blogger Unknown said...

Can anyone define "Systems will be receiving updates over the next several days"? I still haven't seen this update on a new Google Pixelbook. Thanks!

6:25 PM, August 13, 2018  
Blogger Jean-Francois Trehou said...

no more loop in update for my ACER 720P on stable channel. Stay now in 67.

9:17 PM, August 13, 2018  
Blogger Véronique Lafontaine said...

I just want a update for the play store to be able to use app ... So i can use some on my asus c201pa... i think all the user of other model who are unable, want it too

10:15 AM, August 14, 2018  
Blogger unextro said...

Serving of 68 is on hold now, all devices list 67 as the latest version: https://cros-updates-serving.appspot.com

10:08 PM, August 14, 2018  
Blogger Leon Magnus said...

still no google play support.. huhu.. are they still working on android compatibility? its been 2 years since they made that news.. :(

8:32 AM, August 18, 2018  
Blogger photo_ted said...

As a geek I understand things go wrong with a release and finding that last bug can take longer than you ever imagined. OTOH, there is a responsibility on the part of the dev team to communicate the status of a release, especially one that has been pulled back.

It happens, but can someone let us know what is going on? Other than the list of what is available on each platform, is there another place to get updates? What happened? What's the current estimate when it will be re-released?

11:00 AM, August 19, 2018  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home