Comment #8 on issue 9339 by blackboxxx: Incorrect folder permissions after  
updating system-level Chrome
http://code.google.com/p/chromium/issues/detail?id=9339

OK, I reproduced the issue again. This time I did the following:
1) Uninstalled Chrome and all Google applications, deleted registry keys
HKCU\Software\Google and HKLM\Software\Google.
2) Downloaded Chrome from google.com/chrome. Version = 1.0.154.53
3) Switched to beta channel using chromechannel-2.0.exe, forced update via  
About >
Update now. Version = 2.0.169.1
4) Set the registry entry ChromeInstallerCleanup of type REG_SZ with  
value "0" under
HKLM\Software\Google\Update (this didn't have any effect, see below).
5) Switched to dev channel, closed all instances of Chrome, rebooted a few  
times and
left the machine idle for a couple of hours.
6) When I got back, Chrome was updated to version 2.0.171.0 and the  
permissions error
was there.

Attached are the screenshot of the message displayed when attempting to  
open the
folder and the report of icacls, cacls and dir /q on two folders -  
Application and
Application\2.0.171.0. It's worth to note that the folder "2.0.171.0" is  
owned by
SYSTEM, not Administrators as its parent.

Sorry, but the verbose logging didn't work. There was no log neither in  
Chrome, nor
in TEMP directory. I checked the registry value I set earlier and it was  
still there.
Apparently the log is generated only when the installer is run with  
--verbose-logging
parameter, which is impossible because the issue happens only with  
auto-updates.

Attachments:
        chrome1.png  37.5 KB
        icacls.log  4.3 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to