headless mode attempting to mkdir, needs permissions?

1,852 views
Skip to first unread message

Brian Cardarella

unread,
Oct 9, 2017, 11:50:14 AM10/9/17
to Chromium-dev
When launching Chrome from the CLI if I don't use `--headless` Chrome launches without issue. But if I add `--headless` I get "Permission denied" errors. Chrome appears to be calling `mkdir` on a directory it doesn't have permission to. Chrome was installed through the regular dmg package.

Is there a way to disable the need for Chrome to mkdir in headless? It would be great if I didn't have to chown the entire directory.

➜  MacOS ./Google\ Chrome --headless
[1009/100340.443190:ERROR:crash_report_database_mac.mm(94)] mkdir /Applications/Google Chrome.app/Contents/Versions/61.0.3163.100/Google Chrome Framework.framework/Versions/A/new: Permission denied
[1009/100340.443558:ERROR:crash_report_database_mac.mm(94)] mkdir /Applications/Google Chrome.app/Contents/Versions/61.0.3163.100/Google Chrome Framework.framework/Versions/A/new: Permission denied
[1009/100340.443617:INFO:crashpad_client_mac.cc(295)] restarting handler in 0.987s
[1009/100340.590801:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.

Alex Clarke

unread,
Oct 9, 2017, 3:17:59 PM10/9/17
to Brian Cardarella, Chromium-dev
For anyone that missed the discussion on the other list, we're tracking this issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=772920

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/3a579e11-1c27-40ca-b77d-c719a2cb952e%40chromium.org.

Robert Sesek

unread,
Oct 9, 2017, 6:29:13 PM10/9/17
to alexc...@google.com, Brian Cardarella, Chromium-dev
I think this is because you're starting Chrome from within the "MacOS" directory. Try cd'ing out of there and launching as Google Chrome.app/Contents/MacOS/Google Chrome.

rsesek / @chromium.org

Reply all
Reply to author
Forward
0 new messages