Chrome Releases

Release updates from the Chrome team

Stable Channel Update for Desktop

Wednesday, October 12, 2016
Share on Google+ Share on Twitter Share on Facebook
Google
Labels: Stable updates

61 comments :

arekm said...

No flash anymore? I don't see libpepflashplayer.so in 54 on Linux.

1:14 PM, October 12, 2016
arekm said...

... and self reply, yes:
https://bugs.chromium.org/p/chromium/issues/detail?id=645687#

1:26 PM, October 12, 2016
William Clark said...

This is my first time ever, commenting on Google Chrome releases.
I just wanted to say "Thank You" Google Chrome Team for making the Chrome interface bigger on High-DPI screens. It looks great now, I hope you guys don't change it.
There is only one problem:
The "Dialog Box" in Google Chrome (e.g. For Username or Password) is a little bit blurry, beside that, everything else looks outstanding.

Thanks a lot and I greatly appriciate your effort guys.

2:30 PM, October 12, 2016
JPereira said...

Not good. Interface, fonts,....got bigger :/

2:55 PM, October 12, 2016
R.A. de Hosson said...

Unfortunately there is the scaling error again on high DPI.
Everything looks too big, I have to start Chrome in compatiblity mode with DPI scaling off in order to get a normal interface... NOT GOOD.

3:06 PM, October 12, 2016
Leo said...

在高分屏下,把Windows的显示自定义绽放级别调高(如125%),这个最新版本的Chrome界面显示变大,难看极了。即使把chrome.exe的文件属性中的兼容性设置为“高DPI设置时禁用显示绽放,也没有用。

6:37 PM, October 12, 2016
He Jx said...

Can not move bookmarks in bookmarks bar

8:14 PM, October 12, 2016
R.A. de Hosson said...

I do not have the above problems with the bookmark bar.
However, I do hope Google will fix the scaling problem in an update.
In the mean time, besides using the compatability mode (mentioned earlier), you can change the windows register:

HKCR\ChromeHTML\shell\open\command\(default)="C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --force-device-scale-factor=1 "%1"

11:56 PM, October 12, 2016
Dorian B. said...

For Google developers.

Please put back the "Simplify Page" option in Google Chrome/Chromium. No current extension hasn't exactly the functions of the "Simplify Page" option.
What is so hard to put you, Google developers, the option back?
You too arbitrary and foolishly decisions in recent years.

I don't want to use extensions for the following reasons:
1. viruses;
2. the duration of the limited life of any non-Google extensions from Web Store;
3. extensions are not always updated according to the version of Google Chrome and they become incompatible with it.

I used the "Simplify Page" option for two clear reasons:
- remove banner adverts from save PDF/print;
- many site has programming language HTML / CSS / etc. old who can’t save as a PDF file or can’t print (blank page appears in PDF or to print) if it was not turned on "Simplify Page" option.

Please to bring the "Simplify Page" option back in Google Chrome/Chromium.

Thank you for understanding.

2:24 AM, October 13, 2016
Philip Lee said...

Actually DPI is fixed now. Pages are scaled the same as Edge browser from MS with no blurr. Been waiting for this forever.

6:37 AM, October 13, 2016
Jim Tricarico said...

Having a problem since upgrading to this version. Several websites (soundcloud, join.me, etc.) are showing SSL certificate errors that cannot be bypassed. NET::ERR_CERT_REVOKED This did not occur 15 minutes ago prior to upgrading Chrome.

11:05 AM, October 13, 2016
Anthony-Follett said...

I agree with Jim^ SSL Errors are not for everyone running MacOS Sierra and Chrome 54 for HTTPS only sites.

www.hpb.com shows "Your connection not private" error.

Confirmed it did not happen on Version 53 but when about 15 people in our Dev Department upgraded, we then saw the issue.

THIS IS VERY BAD!

11:31 AM, October 13, 2016
Joseph terracciano said...

we are seeing issues where user cant launch chrome. the process is running but the browser doesn't open since upgrading.

11:47 AM, October 13, 2016
Kyle Tillman said...

We had to go and disable the QUIC protocol to make this version work with secure sites. This needs to be triaged ASAP. Making a bug report as well.

1:51 PM, October 13, 2016
Jack Rugile said...

I can confirm Jim's issue here as well. SoundCloud in particular is what tipped me off.

2:46 PM, October 13, 2016
Chloe Simpson said...

I can navigate to websites like youtube.com and most other sites by entering the address. However google.com gives an error (ERR_QUIC_PROTOCOL_ERROR) as if the address is incorrect, therefore I cannot perform any google searches by going directly to google or by entering a search in the address bar. I tried logging out of my account and reinstalling chrome (therefore it is definitely not an extension problem since none are enabled and there is also no browsing history) but the issue persists.

2:59 PM, October 13, 2016
Jack Rugile said...

It looks like this is the cause for some of the SSL issues mentioned here: https://twitter.com/globalsign/status/786617201788723200?lang=en

3:01 PM, October 13, 2016
Brian Geng said...

This release seems to break if you have Software Restriction Policies in place in Windows. I've had to rollback and prevent automatic updates as this version of Chrome will not launch. The policies have not changed at all between upgrades so something in this version has introduced an incompatibility.

5:00 PM, October 13, 2016
Michael Bierman said...

I'm seeing the same as Jim. Several sites claim NET::ERR_CERT_REVOKED and there's no way around it.

11:42 PM, October 13, 2016
Zhangir Duiseke said...

Hello, motherfucking Google! I would like to thank degenerate Google Chrome developers for making interface FUCKING huge. Thank you very fucking much. Fucking fix it NOW!

4:13 AM, October 14, 2016
Clemens Stubbe Østergaard said...

This update has completely jumbled Facebook for me. Youtube, Gmail, e-mail, Soundcloud, HBO, and seemingly everything else all works fine, but Facebook is way fucked.
Everything appears out of place, text shows up as links, the formatting is consistently off, icons are shifted to the side, and the page has been made three times as wide with none of this "great" new scaling. The last thing makes me think this is a problem with the already useless new scaling B*llshit, but I'm not that into computers.

Anyway, thanks Obama.

4:20 AM, October 14, 2016
Kenneth said...

We utilize software restriction policies in our domain, and with these in place we cannot start version 54 of chrome. Also present on beta channel (version 55).

4:36 AM, October 14, 2016
Wouter said...

Big screw up with the DPI again. UI is huge, and webpage is displayed way to big. Google tells me im not the only one. Please revert back with the dpi settings.

6:52 AM, October 14, 2016
Mark Peterman said...

The chrome PDF viewer plugin is not working for me. I had to get an extension off of the web store. Is anyone else able to use the chrome PDF viewer plugin?

7:21 AM, October 14, 2016
ER said...

getting flash plugin update errors

9:11 AM, October 14, 2016
Rendy Darmawan said...

I hate this update, UI so HUGE, i need interface in 53

11:04 AM, October 14, 2016
Dan Gallacher said...

I am also having issues with Launching this new version of Chrome with Software Restriction enabled. I have been able to determine that has something to do with the enforcement of certificate rules. If you turn off certificate rule enforcement on the policy then Chrome will launch.

However, this is not a good solution since we use certificate rules to whitelist other applications. While I can disable certificate enforcement to allow Chrome to work, it will prevent several other programs to be blocked by Software Restriction.

11:17 AM, October 14, 2016
Soledad Miranda said...

There is the scaling error on high DPI. Everything looks too big.

11:21 AM, October 14, 2016
Joseph Tikalsky said...

Also experiencing an issue with Quic Protocol. The update is trickling down to our 5,000 desktops and we are receiving lots of complaints of being unable to access Google.com, Drive, Youtube, etc. Basically any website that is being operated by Google. Other websites such as CNN.com and MSN.com, as well as internal websites, work perfectly fine. Google websites also work as expected in other browsers, such as IE and Firefox.

Disabling Quic Protocol from chrome://flags solves the issue, but I don't want to do that on 5,000 machines. Anyone have any help? I'm hoping the Chrome team will just need to resolve this on their end. Unfortunately, we have 10,000 Chromebooks as well that will receive the new version 54 and I'm hoping that doesn't break them.

11:47 AM, October 14, 2016
Richard Bustamante said...

Thanks everyone for your comments. We've been looking into the issues raised here, and are working to address them.

3:30 PM, October 14, 2016
EVCC Food Day said...

My god, I updated my browser thinking it might fix the problem I'm having using Chrome with Play Music. Instead everything is giant now! The address bar, the tabs, and the webpages. I went from using zoom at 110% to moving backwards to 89-90% depending on the webpage. There's no reason for it to be this big!

2:12 AM, October 15, 2016
KANGOD said...

I‘m getting "Adobe Flash Player is out of date" error on 54.0.2840.59.
OS: Ubuntu 14.04
Chrome: Version 54.0.2840.59 (64-bit)
Seems I can't upload a sreenshot, So here is the "chrome://plugins/" content for Flash Player:
[pre]
Adobe Flash Player - Version: 23.0.0.185
Shockwave Flash 23.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 23.0 r0
Version: 23.0.0.185
Location: internal-not-yet-present
Type: PPAPI (out-of-process)
Disable
MIME types:
MIME type Description File extensions
application/x-shockwave-flash Shockwave Flash .swf
application/futuresplash FutureSplash Player .spl
[/pre]

4:29 AM, October 15, 2016
侯志伟 said...

Hi KANGOD,

I have a same issue with you.

11:50 PM, October 15, 2016
Unknown said...
This comment has been removed by the author.
12:24 AM, October 16, 2016
Bill Mastrippolito said...

If your chrome has just made everything larger with todays update, here is your solution to get it back to normal.
Right click on your chrome icon, then click on properties, click in the "target" box, go to the end of that field which should end with " put a space after that then paste the following after that space

--high-dpi-support=1 --force-device-scale-factor=1

then click ok then close and reopen chrome and you should be back to normal.

5:43 AM, October 16, 2016
Jeffrey Oelkers said...

While I don't find the increased size of elements in this update to be as overt and productivity reducing as past instances of inflation, I still find my typical split screen setup to be overly crowded, where I have to resize website UI elements/panels a good deal more than I did before updating.

One other change has reversed the fix of a problem that had intermittently annoyed me for years. I have most of the bookmarks in the Chrome bookmarks bar arranged in folders. This works really well for me, however, when I click to open a folder after the most recent update, I cannot close it by clicking on it a second time. The folder can be closed by pressing ESC, but in most situations, this is not as efficient as clicking on the open folder's icon to close it. If the 'second click to close' behavior could be reinstated, that would be great.

11:06 AM, October 16, 2016
Room 9 said...

Facebook videos and Vimeo videos don't seem to play properly anymore since the update. They start then stop and buffer for ages before starting and stopping all the way to the end.

11:32 AM, October 16, 2016
Robert Wignall said...

Also experiencing the unable to launch issue on a domain with SRP in place. Chrome.exe will appear in task manager, but no window launches. Nothing in logs, but uninstalling and putting in an earlier version restores functionality.

8:34 PM, October 16, 2016
James Keating said...

I am also having the issue with SRP. I have had to temporarily disable Certificate Restriction enforcement but this is not viable for the long term.

James

2:20 AM, October 17, 2016
Micu X said...

In my office we also have a problem with running new version of Chrome on Win7. The problem is characterized by running two processes named chrome.exe and no application showing up. We do not have any SRP policies set and nothing I've tried helped.
My colleague pointed out that when he was setting up the new PC he was able to run the Chrome v54 normally but after he updated the OS Chrome started to have the same issues like written above - maybe that tip will help someone find the solution.

6:17 AM, October 17, 2016
Tyler Erickson said...

I'm having the same issue with SRP. Disabling Certificate restriction enforcement also worked for me but also not a long term solution.

6:28 AM, October 17, 2016
Unknown said...

+1 on the SRP Issue and disabling certificate resolution as a fix. Even after that, though, users can't use any sites that require flash. The plugin fails on download. Are other folks having the same issue?

12:12 PM, October 17, 2016
Mike Vitale said...

Is there a set date when Flash will be permanently disabled within Chrome?

12:20 PM, October 17, 2016
The Frugal Geek said...

I am running into the flash plugin issue also. Using Chrome Enterprise some users even though they are on the proper version of Chrome their flash is showing x.x.x.166 instead of x.x.x.185 and getting the "click to run once". Anyone else getting this?

7:05 PM, October 17, 2016
Travis Rowland said...

Whoever decided it was a good idea to remove the bits which made the docked Google Hangouts chat windows possible, is a fucking idiot. Now I am forced to run a portable version of Chrome 53 JUST FOR HANGOUTS!

3:05 AM, October 18, 2016
Albert Altman said...

Was the touch screen issue fixed ?
I had an issue with touch screen scrolling.
Looks like it works now (tested on https://inbox.google.com).

7:29 AM, October 18, 2016
Albert Altman said...

Was the touch screen scrolling issue fixed ?
I did not see any comets about that.
I tested with inbox.google.com and it seems ok now.

The problem was that instead of scrolling the text selection action was used.

Thank you upfront!

7:32 AM, October 18, 2016
Jae Chung said...

just received the latest update on Chrome (54.0.2840.59 m)
and I can't go to any of Google site.
I get an error with ERR_QUIC_PROTOCOL_ERROR.

5:47 AM, October 19, 2016
Kubas789 said...
This comment has been removed by the author.
11:32 AM, October 19, 2016
miniwrld at work said...

@Jae Chung I get this error too. To work around it you need to set "Experimental QUIC protocol" to "Disabled" in chrome://flags.

4:18 AM, October 20, 2016
ConejoValleyVermin said...

Just updated to v54 Chrome. Please, oh please correct the huge (Yuge!) size of your new Chrome. I feel like I'm in kindergarten. Look! See Jack. See Jack run. Run, Jack, run!

I've tried every correction I have found on the internet to no avail. I'm running Windows 10 64. The prior version was sleek and beautiful. What happened?
Thank you.

1:06 PM, October 21, 2016
Weekend Wang said...
This comment has been removed by the author.
8:23 PM, October 21, 2016
Weekend Wang said...
This comment has been removed by the author.
8:36 PM, October 21, 2016
Weekend Wang said...

Hi @侯志伟 , you can manually update flash as Google said: https://support.google.com/chrome/answer/6213033?hl=en .
Well, in case that the "chrome://components" update doesn't work(which is my situation), here is how I solve the flash issue:
1. Download PPAPI Flash plugin at https://get.adobe.com/flashplayer/, for me(Ubuntu 14.04 x64), it's `flash_player_ppapi_linux.x86_64.tar.gz`.
2. Extract the archive, copy `libpepflashplayer.so` and `manifest.json` to `~/.config/google-chrome/PepperFlash/[flash_version_number]`, where [flash_version_number] is 23.0.0.185 now.
3. Add chrome flags to specify flash plugin. My "Exec" line in "google-chrome.desktop" file is as following:
`Exec=/usr/bin/google-chrome-stable --incognito --ppapi-flash-path=/home/kangod/.config/google-chrome/PepperFlash/23.0.0.185/libpepflashplayer.so --ppapi-flash-version=23.0.0.185`
4. Start chrome then flash works well.

References:
[Only ChromeOS has precompiled Flash that needs to get copied to the output directory. On other platforms, Flash is either component-updated only or not supported at all.](https://chromium.googlesource.com/chromium/src/+/366d572053dd85c8eeda802f423716d9b008fe01%5E%21)
[list of some chrome switches](https://chromium.googlesource.com/chromium/src/+/54.0.2840.73/chrome/common/chrome_switches.cc#741)

8:38 PM, October 21, 2016
ganeshaxl said...

After updating to this version, window.opener.location.reload(true) - not working and window.opener.closed is always showing false

10:40 PM, October 24, 2016
Jeb Rothberg said...

Great job, you broke the UI with this DPI scaling garbage. Luckily someone posted the fix in a previous comment, by adding launch options (--high-dpi-support=1 --force-device-scale-factor=1) because for some reason your stupid browser totally ignored 'disable DPI scaling' in the application properties.

8:39 AM, October 25, 2016
Michael Bierman said...

I am using the Version 54.0.2840.71 (64-bit) on Mac (Sierra 10.12.1) Today I got this error:

You are using an unsupported command-line flag: --extension-on-chrome-urls. Stability and security will suffer.

see https://www.evernote.com/l/AAISuKWzQ6ZFVrvf7OQlG1lvTuMeW6RVunQ


I only see this in the gmail tab. While I see some mentions of this problems in past postings, they don't seem to address this particular behavior.

Any help would be appreciated!

11:22 AM, October 25, 2016
Kevin Jhangiani said...

This release breaks all extension menus on my setup, presumably due to some display scaling changes. I've had issues with chrome since the material-icons ux update.

From 53.x to this release however, when using a retina display monitor (primary laptop monitor, win 10, 125% scaling), and 2 external 100% scaling monitors (chrome is open on the externals), all the extension menus get out of sync the progressively further your mouse hovers down them.

IE, Lastpass, ublock, etc - anything with a menu thats on my toolbar at the top, if I click to open the extension menu, then move my mouse down the list of options, you can see the highlighted option get progressively further and further from where the mouse cursor is, such that there is about 150px difference between mouse location and highlighted option near the bottom of these menus.

This is not an extension bug as it is reproducible on various extension menus. Furthermore, dragging the chrome window back to my retina monitor with 125% scaling, the mouse is back in sync with the menu.

I'm looking for a way to undo this update or a workaround for this issue as the browser is entirely unusable right now. I tried the dpi scaling options on the shortcut as well as compatibility mode but neither made a difference

2:39 PM, October 25, 2016
Charles Collier said...

Please fix scaling please zoomed in way to much.

7:58 PM, October 25, 2016
Jens Viebig said...

Some years ago i switched from Firefox to Chrome because of this DPI shit. No Chrome does the same...Please at least make it possible to switch off that shit!

12:01 AM, October 26, 2016
Donna L. said...

All of a sudden everything is HUGE on my Chrome browser...some pages are running right off the screen! What's up with that??

5:52 AM, October 26, 2016

Post a Comment

  

Labels


  • Admin Console
  • Android WebView
  • Beta
  • Beta updates
  • chrome
  • Chrome Beta for Android
  • Chrome Dev for Android
  • Chrome for Android
  • Chrome for iOS
  • Chrome for Meetings
  • Chrome OS
  • Chrome OS Management
  • Chromecast Update
  • Desktop Update
  • dev update
  • Dev updates
  • Flash Player update
  • Hangouts Meet hardware
  • Stable updates


Archive


  •     2018
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2017
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2016
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2015
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2014
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2013
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2012
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2011
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2010
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2009
    • Dec
    • Nov
    • Oct
    • Sep
    • Aug
    • Jul
    • Jun
    • May
    • Apr
    • Mar
    • Feb
    • Jan
  •     2008
    • Dec
    • Nov
    • Oct
    • Sep

Feed

Googleon Google+
Follow

Company-wide

  • Official Google Blog
  • Public Policy Blog
  • Student Blog

Products

  • Android Blog
  • Inside Search Blog
  • Lat Long Blog

Developers

  • Developers Blog
  • Chromium Blog
  • Android Developers Blog
  • Google
  • Privacy
  • Terms