App is damaged after run in headless mode on clean installation[OSX]
Reported by
volodymy...@gmail.com,
Sep 6 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36 Steps to reproduce the problem: 1. Install Chrome and don't launch it. 2. Run Chrome in headless mode from terminal: "/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --headless --disable-gpu --remote-debugging-port=9222" 3. Try to launch Chrome from Launchpad or Dock What is the expected behavior? Normal launch as usual. What went wrong? Chrome app becomes damaged Did this work before? N/A Chrome version: 61.0.3163.79 Channel: stable OS Version: OS X 10.10.5 Flash Version:
,
Sep 6 2017
Can you explain more by what you mean by "damaged"?
,
Sep 7 2017
Thank you for providing more feedback. Adding requester "skyostil@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7 2017
Looks like the comment was deleted. Could you post it again?
,
Sep 7 2017
Can't attach the image, message becomes deleted... http://imgur.com/a/3TWOK
,
Sep 7 2017
Thank you for providing more feedback. Adding requester "skyostil@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 11 2017
I'm not able to reproduce the error, can you confirm if you are trying to run both applications (headless and non-headless) at the same time. This might be the issue, but it does work fine for me
,
Sep 11 2017
,
Sep 11 2017
I'm not running both applications at same time, what version of chrome do you use?
,
Sep 13 2017
,
Sep 14 2017
What do you mean by "Chrome app becomes damaged"?
,
Sep 14 2017
What do you mean by "Chrome app becomes damaged"? http://imgur.com/a/3TWOK App cant be launched anymore after step #2
,
Sep 16 2017
[mac bug triage] By damaged the reporter refers to macOS telling them that the Chrome application is damaged and should be thrown away (it will not run). This could be a signing problem caused by something writing into the Chrome.app file package, or from actual files being removed from within Chrome.app.
,
Sep 19 2017
,
Sep 19
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by pbomm...@chromium.org
, Sep 6 2017Labels: Proj-Headless M-61