warnings about Dictionaries directory on Windows |
|||
Issue descriptionVersion: 53.0.2764.0 rev c7ebaa1 OS: Windows 7 x86 What steps will reproduce the problem? (1) Install official build of Chrome tagged as stable (2) Run with --enable-logging (3) What is the expected output? no warnings What do you see instead? [2472:3840:0609/155353:WARNING:file_util_win.cc(442)] Failed to create directory C:\Program Files\Google\Chrome\Application\Dictionaries, last error is 5. [2472:3840:0609/155353:WARNING:file_util_win.cc(660)] CreateFile failed for path en-US-7-1.bdic: Access is denied. (0x5) [2472:3840:0609/155353:WARNING:file_util_win.cc(442)] Failed to create directory C:\Program Files\Google\Chrome\Application\Dictionaries, last error is 5. Please use labels and text to provide additional information.
,
Jun 10 2016
I think I've already rebuilt by now - but the rev is in the #0 https://crrev.com/c7ebaa1 git fetch origin git checkout c7ebaa1 and the GYP flags I used are: GYP_DEFINES=dcheck_always_on=1 branding=Chrome disable_nacl=1 gclient sync ninja -C out\Release mini_installer and to repro I install Chrome Stable off the web first (to tag myself as Stable channel and with a brand code) then I update to my version of chrome from the build output by running: mini_installer.exe --multi-install --system-level Then I delete my user data dir, and run Chrome with --enable-logging=stderr >log.txt 2>&1 and I get those warnings. They only appear on first run.
,
Jun 10 2016
wfh@, I was looking for the chrome profile path, which is in your chrome://version.
,
Jun 30 2016
It would be the default profile path for a new install on a fresh install of Windows having never had Chrome on it before. You should be able to repro using the steps in #2, I can try and repro next time I am doing some testing in a clean VM.
,
Apr 27 2017
,
Apr 27 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by rouslan@chromium.org
, Jun 9 2016