Chrome Crashing when Attempting to Update from 52 -> 54
Reported by
cam.clay...@momsorganicmarket.com,
Oct 21 2016
|
||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Steps to reproduce the problem:
1. End Users unable to send mail, or update labels in Gmail
2. Click About and Chrome 52 attempts to update
3. Chrome 52 update fails, and users are unable to continue using Gmail
What is the expected behavior?
Chrome updates successfully, users are able to use Gmail.
What went wrong?
Update failed (error: 12)
Error details:
2016-10-21 09:11:46.310 GoogleSoftwareUpdateAgent[1241/0xb031d000] [lvl=3] -[KSInstallAction performAction] KSInstallAction install script failure. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:2307 - '/tmp/KSInstallAction.RUrHtY10Hl/m/.keystone_install'] ("rsync: mkdir \"/Applications/Google Chrome.app/Contents/Versions/54.0.2840.71\" failed: Permission denied (13)\nrsync error: error in file IO (code 11) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(544) [receiver=2.6.9]\nrsync: connection unexpectedly closed (8 bytes received so far) [sender]\nrsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(453) [sender=2.6.9]\n.keystone_install: rsync of versioned directory failed, status 12\n" - '/tmp/KSInstallAction.RUrHtY10Hl/m/.keystone_install' [kKSInstallScriptErrorDomain:7])
2016-10-21 09:11:46.313 GoogleSoftwareUpdateAgent[1241/0xb031d000] [lvl=3] -[KSCompositeAction(KSActionProcessorDelegate) processor:finishedAction:events:errors:] KSUpdateAction action had a subaction fail, abort. [com.google.UpdateEngine.CommonErrorDomain:101 - 'KSCompositeAction.m:216'] (KSInstallAction install script failure. - '/tmp/KSInstallAction.RUrHtY10Hl/m/.keystone_install' [com.google.UpdateEngine.CoreErrorDomain:2307])
2016-10-21 09:11:46.322 GoogleSoftwareUpdateAgent[1241/0xb031d000] [lvl=3] -[KSAgentApp(KeystoneDelegate) updateEngineFinishedUpdate:errors:wantsReboot:] Finished with com.google.Chrome : errors 2, should reboot: NO
Crashed report ID:
How much crashed? Just one tab
Is it a problem with a plugin? N/A
Did this work before? Yes 51
Chrome version: 52.0.2743.116 Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 23.0 r0
Happening on Mac, and Windows, users are logged into the Browser, and we are GSuite/Google For Work customers.
Initial error message states, "Some features of MOM's Organic Market, were not able to be loaded. Please reload the browser or try the Basic HTML version."
,
Oct 21 2016
mark@, can you have a look at this? looks like keystone is failing.
,
Oct 21 2016
This isn’t a crash, it’s an update failure. I see: rsync: mkdir "/Applications/Google Chrome.app/Contents/Versions/54.0.2840.71" failed: Permission denied (13) This is indicative of Chrome not having permission to update itself. Most likely, Chrome is being run by a different user than the one that installs it and owns the .app on disk. Chrome may have detected this problem and offered, via infobar, an option to “set up automatic updates for all users.” But even if the opportunity to act on that infobar was missed, it’s possible to set Chrome up to be able to update itself in this situation. Go to Chrome’s About page (Chrome:About Google Chrome) and click the “Set up automatic updates for all users” button. You will be prompted for an administrator’s username and password, which you should provide. Let me know if that works for you.
,
Oct 21 2016
Hello, I attempted the Allow All Users to Update, and it did ask for privileges but failed. I then went logged out of the user account, and went into the admin account. When I entered the About screen, Chrome had updated to 53 from 52. I then did the update, and reloaded and it went to 54, so this issue is resolved for us. Windows users are no longer having an issue, we believe they were due to Virtu being disrupted. Thanks for the assistance, Cam
,
Oct 21 2016
I’m concerned about the failure you experienced in “set up automatic updates for all users.” Boris, is there anything that we can do to debug the promotion flow? Cam, I’m glad you were able to update. If there are lingering problems, I’d still like to investigate, because I’m afraid that this might happen to you again the next time we release an update. I don’t want you to have to switch to your admin user to install updates. The “set up automatic updates” feature is supposed to handle situations like yours seamlessly.
,
Oct 21 2016
The user it was affecting has left for the day, Please let me know if you need any more information for debugging and or testing of patches. Thanks, Cam
,
Oct 21 2016
I am also curious why the elevation failed from the non-admin user. Keystone logs extensively any failures. Cam, is it possible for you to log on as admin again and run the command below and send us the generated report? Also, please tell us roughly when the problem occurred. /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics |
||||
►
Sign in to add a comment |
||||
Comment 1 by meh...@chromium.org
, Oct 21 2016Components: Internals>Installer