Hey! Why did you remove thin border from drop-down menu on Linux version? Still can't get is it bug or new design improvement.. anyhow there should be shadow around it at least, 'cause when it merges with similar background in some cases - it looks pretty shitty: http://rghost.net/8XGXx4YhH.view And I still can't mute pinned tabs from another ones with chrome://flags/#enable-tab-audio-muting enabled
@fprietog It seems to be kde-specific problem then.. Can any KDE user confirm that? I'm on Plasma 5.4.2 right now and on chrome-45.x border was showing correctly.
I faced a problem about time zone in this version. The correct behavior is to obtain local time zone, but in my program, chrome automatically fetched the zero-time zone. Does anyone has the same issue with me?
This update when viewed on my AOC usb monitor (v. E1659Fwu) has made it so that main area of the screen -- all but menu area / toolbar of Chrome -- looks like an old tv screen with no signal. No other apps I use have trouble with this monitor, and Chrome worked perfectly until this update. Any ideas what caused this?!! I've turned off all extensions, cleared all possible history, rebooted, and tried a new version of the driver for the AOC monitor. As mentioned, Firefox, Safari and every other app I use work fine on this monitor. I'm on a Macbook Pro, OSX 10.10.5.
"This is your Chrome... Now you can set up Chrome just the way you like it."
Lies. --disable-new-avatar-menu no longer works. I don't want to use the new user switcher. Using --disable-new-avatar-menu maintains the old position of the user switcher but it ends there. Clicking on it produces the new user switcher window but clicking on "switch user" produces an error. Page not found. The old user switcher requires less clicks and was perfectly simple for the task. A case of KISS. The new user switcher requires more clicks and more screen space. Google, it is MY chrome, let me keep using it the way *I* want, not the new ways that you force upon us.
This release seems to have broken hardware acceleration on DisplayLink USB display adapters. Since this update, when a Chrome window is moved to an external monitor connected to a DisplayLink USB display adapter (specifically the Plugable 3.0) it displays only a window with grey diagonal lines. Disabling hardware acceleration in Chrome fixes this.
on the subject of the order of these machines and later mount occurring the intensity as they to the lead payment because they are gentle approaching the cardiovascular system. People have the self-starter to achieve their weight loss goals because the machines are swift to acquire their started and going on for speaking a passage toward flesh and blood thing healthy. NO2 Blast
As Joe Conger has already pointed out, we are getting a different version number, 46 vs 66, and this will impact the way we report, so we want to know if this is a permanent change or a failure unique to this release.
We are also seeing this at the end of the chrome_installer.log: [1016/070322:ERROR:setup_main.cc(106)] Failed to set DisplayVersion: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{66FD3DE5-373F-397D-BB7A-85E5AFAEB6A8} not found
This seems to reference a failure to complete this action:
Add options to write version number to registry.
The MSI installer creates a DisplayVersion registry entry with an encoded version of Chrome's actual version. Since this is done _after_ the setup call completes, we can't simply set the value in the normal setup process. Instead, we launch a background process that waits a while (for msiexec to complete) and then writes the updated version.
This is accomplished by having setup, upon successful completion, run itself in the background and then exit normally.
This comes from the "log" for this release and appears to be a new addition as it was never mentioned in earlier release logs. But it is unclear which version is the "encoded version", 46 or 66... still the installer log is clearly reporting an error.
So, please let us know what is going on here. Thank you.
OK, I am going to partially answer my own question. The error in chrome_installer.log is due to the fact that we are installing on 64-bit W7 and the installer is literally attempting to write to the key shown, which is a 64-bit registry location (I was assuming redirection would point the 32-bit install to syswow automatically), AND because Google never writes to the 64-bit key, even with the 64-bit version of Chrome. It is then also writing out the 32-bit key, which succeeds, but does NOT log and then exits.
So I am fairly confident that the desired behavior (desired by Google, not me) is to write out a new DisplayVersion after the msiexec process for the install has quit - usually occurs about 10 seconds after the install finishes. The technical term for this is "janky".
We use Microsoft CM2012 for deployment. The Application model in CM2012 uses Detection Methods(DMs). A common DM is to point the object at the installers MSI and it pulls all the info it needs. When you do this for this release, it still pulls version 66.110.32839, because this is still listed as the EnterpriseProduct version. So, when the CM2012 deployment initially finishes, it very quickly checks this key (within 10 seconds) and it passes the DM and reports Success back to the system. However, DMs are constantly rechecked in the CM App Model, so the next time it checks, it will change that Success into a Failure and attempt to re-run the Application. Good stuff.
There are workarounds but this takes a simple, tried and true DM from us. We can just add the 46 version in, but that becomes a manual process and it is just... so... JANKY!
Could someone explain why this was done? Why not just write out the correct version in the first place? Overwriting registry keys like this is not enterprise level behavior.
I am having issues with ImageMapster with the newest update, I don't know if it is a jquery issue or what, is anyone else having any type of issues with jquery, json, or the imagemapster plugin now that Chrome has updated? Thanks.
I often switch users and the old user switcher was more efficient than the current version as Goto San explained above. It was bad enough that Google replaced the old user switcher in previous versions of Chrome, but now they've made the work around launcher switch, "--disable-new-avatar-menu", useless.
Anyone having issues with clients (or yourself) loading pdf's in chrome, there was some changes made that as far as I know are being fixed. It has to do with changes to make the PDF viewer more strict a lot of pdf generators (including some by microsoft) are missing new lines or have white space where they should not. https://code.google.com/p/chromium/issues/detail?id=543018
The 'Right click' menu is no longer working for PDF files viewed in Chrome. I'm pretty sure this worked until recently. But if you click a link that opens a PDF file directly in the address bar (without asking to save it first), the right-click menu containing the 'Save as' and 'Print' options is no longer working. You can try it yourself: https://partners.adobe.com/public/developer/en/xml/AdobeXMLFormsSamples.pdf
Excellent release. I needed to disable 360 total security extension to stop google chrome from crashing. I am not an expert. I was having crashing issues until I just disabled the 360 plugin. The 64-bit browser is clearly faster than its 32-bit version. Thanks!
Big problem with --disable-new-avatar-menu: It leads to an error page:
This webpage is not available ERR_INVALID_URL The webpage at chrome://user-manager/ might be temporarily down or it may have moved permanently to a new web address.
Our business uses the profile icons in the menu bar. We need the quick visual indication of which profile is in which window.
Can we please get an answer regarding Rick & Joe Conger's query about the Version number change from 46 to 66 in the Chrome For Work branch? It's now been almost two weeks since their queries, and this has broken our Chrome detection method in our SCCM 2012 R2 applications.
Follow
31 comments :
Hey! Why did you remove thin border from drop-down menu on Linux version? Still can't get is it bug or new design improvement.. anyhow there should be shadow around it at least, 'cause when it merges with similar background in some cases - it looks pretty shitty:
http://rghost.net/8XGXx4YhH.view
And I still can't mute pinned tabs from another ones with chrome://flags/#enable-tab-audio-muting enabled
@Alexander Malyshev
No problem under Ubuntu 15.04 x86_64, the border and shadow are shown:
http://rghost.net/8HLHfFXQl.view
@fprietog
It seems to be kde-specific problem then.. Can any KDE user confirm that? I'm on Plasma 5.4.2 right now and on chrome-45.x border was showing correctly.
We use the Google for Work version of Chrome.
MSI Installer used: googlechromestandaloneenterprise.msi
{911F7EB3-3022-43F4-8E8C-5A99DE7F0D67}
The program version appear to have changed from 66.1010.328.69 -> 46.0.2490.71
Is it suppose to be that way now?
You guys need to fix the hardware acceleration with AMD products. Chrome sometimes crashe the graphic driver.
I faced a problem about time zone in this version. The correct behavior is to obtain local time zone, but in my program, chrome automatically fetched the zero-time zone. Does anyone has the same issue with me?
Material Design still not work =( After 2 year relise! So slow gues so slow!
Strange behaviour in Mac version.. Page trebles also Gmail looks strange..
@Tina Zhou
Issue #527318 that affected linux in m45 appears to be resolved.
Pass my thanks along to the Chromium team!
This update when viewed on my AOC usb monitor (v. E1659Fwu) has made it so that main area of the screen -- all but menu area / toolbar of Chrome -- looks like an old tv screen with no signal. No other apps I use have trouble with this monitor, and Chrome worked perfectly until this update. Any ideas what caused this?!! I've turned off all extensions, cleared all possible history, rebooted, and tried a new version of the driver for the AOC monitor. As mentioned, Firefox, Safari and every other app I use work fine on this monitor. I'm on a Macbook Pro, OSX 10.10.5.
Are there possibilities to improve html5 videos cpu usage!? Or to enable hardware acceleration on XP systems by Dx9 or opengl!?
"This is your Chrome... Now you can set up Chrome just the way you like it."
Lies. --disable-new-avatar-menu no longer works. I don't want to use the new user switcher. Using --disable-new-avatar-menu maintains the old position of the user switcher but it ends there. Clicking on it produces the new user switcher window but clicking on "switch user" produces an error. Page not found. The old user switcher requires less clicks and was perfectly simple for the task. A case of KISS. The new user switcher requires more clicks and more screen space. Google, it is MY chrome, let me keep using it the way *I* want, not the new ways that you force upon us.
This release seems to have broken hardware acceleration on DisplayLink USB display adapters. Since this update, when a Chrome window is moved to an external monitor connected to a DisplayLink USB display adapter (specifically the Plugable 3.0) it displays only a window with grey diagonal lines. Disabling hardware acceleration in Chrome fixes this.
Google Cloud Print Driver appears to crash Google Chrome after this update.
Happening across 89 laptops in our enterprise.
on the subject of the order of these machines and later mount occurring the intensity as they to the lead payment because they are gentle approaching the cardiovascular system. People have the self-starter to achieve their weight loss goals because the machines are swift to acquire their started and going on for speaking a passage toward flesh and blood thing healthy.
NO2 Blast
aptalks
As Joe Conger has already pointed out, we are getting a different version number, 46 vs 66, and this will impact the way we report, so we want to know if this is a permanent change or a failure unique to this release.
We are also seeing this at the end of the chrome_installer.log: [1016/070322:ERROR:setup_main.cc(106)] Failed to set DisplayVersion: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{66FD3DE5-373F-397D-BB7A-85E5AFAEB6A8} not found
This seems to reference a failure to complete this action:
Add options to write version number to registry.
The MSI installer creates a DisplayVersion registry entry
with an encoded version of Chrome's actual version. Since
this is done _after_ the setup call completes, we can't
simply set the value in the normal setup process. Instead,
we launch a background process that waits a while (for
msiexec to complete) and then writes the updated version.
This is accomplished by having setup, upon successful completion,
run itself in the background and then exit normally.
This comes from the "log" for this release and appears to be a new addition as it was never mentioned in earlier release logs. But it is unclear which version is the "encoded version", 46 or 66... still the installer log is clearly reporting an error.
So, please let us know what is going on here. Thank you.
OK, I am going to partially answer my own question. The error in chrome_installer.log is due to the fact that we are installing on 64-bit W7 and the installer is literally attempting to write to the key shown, which is a 64-bit registry location (I was assuming redirection would point the 32-bit install to syswow automatically), AND because Google never writes to the 64-bit key, even with the 64-bit version of Chrome. It is then also writing out the 32-bit key, which succeeds, but does NOT log and then exits.
So I am fairly confident that the desired behavior (desired by Google, not me) is to write out a new DisplayVersion after the msiexec process for the install has quit - usually occurs about 10 seconds after the install finishes. The technical term for this is "janky".
We use Microsoft CM2012 for deployment. The Application model in CM2012 uses Detection Methods(DMs). A common DM is to point the object at the installers MSI and it pulls all the info it needs. When you do this for this release, it still pulls version 66.110.32839, because this is still listed as the EnterpriseProduct version. So, when the CM2012 deployment initially finishes, it very quickly checks this key (within 10 seconds) and it passes the DM and reports Success back to the system. However, DMs are constantly rechecked in the CM App Model, so the next time it checks, it will change that Success into a Failure and attempt to re-run the Application. Good stuff.
There are workarounds but this takes a simple, tried and true DM from us. We can just add the 46 version in, but that becomes a manual process and it is just... so... JANKY!
Could someone explain why this was done? Why not just write out the correct version in the first place? Overwriting registry keys like this is not enterprise level behavior.
Hello All.
I think new release is required admin permission? Our cleints limited users cant run chrome browser but admins can run.
How can solve this?
I am having issues with ImageMapster with the newest update, I don't know if it is a jquery issue or what, is anyone else having any type of issues with jquery, json, or the imagemapster plugin now that Chrome has updated? Thanks.
I am having a number of clients that are not able to open a PDF in the browser. Would you have any suggestions that I could direct towards them?
I often switch users and the old user switcher was more efficient than the current version as Goto San explained above. It was bad enough that Google replaced the old user switcher in previous versions of Chrome, but now they've made the work around launcher switch, "--disable-new-avatar-menu", useless.
Anyone having issues with clients (or yourself) loading pdf's in chrome, there was some changes made that as far as I know are being fixed. It has to do with changes to make the PDF viewer more strict a lot of pdf generators (including some by microsoft) are missing new lines or have white space where they should not. https://code.google.com/p/chromium/issues/detail?id=543018
The 'Right click' menu is no longer working for PDF files viewed in Chrome. I'm pretty sure this worked until recently. But if you click a link that opens a PDF file directly in the address bar (without asking to save it first), the right-click menu containing the 'Save as' and 'Print' options is no longer working. You can try it yourself: https://partners.adobe.com/public/developer/en/xml/AdobeXMLFormsSamples.pdf
Excellent release. I needed to disable 360 total security extension to stop google chrome from crashing. I am not an expert. I was having crashing issues until I just disabled the 360 plugin. The 64-bit browser is clearly faster than its 32-bit version. Thanks!
Big problem with --disable-new-avatar-menu: It leads to an error page:
This webpage is not available
ERR_INVALID_URL
The webpage at chrome://user-manager/ might be temporarily down or it may have moved permanently to a new web address.
Our business uses the profile icons in the menu bar. We need the quick visual indication of which profile is in which window.
Can we please get an answer regarding Rick & Joe Conger's query about the Version number change from 46 to 66 in the Chrome For Work branch? It's now been almost two weeks since their queries, and this has broken our Chrome detection method in our SCCM 2012 R2 applications.
Post a Comment