Chrome won't open after new machine deployment

rpayne
Contributor II

I've had an issue where Chrome will bounce a few times and then stop. Never opening. This is with Google packaged pkg. Has anyone seen this?

3 REPLIES 3

mhasman
Valued Contributor

If delete that folder?
~/Library/Application Support/Google/Chrome

seanjsgallagher
Contributor

I am seeing the same thing. I was able to run a chmod -R 775 ~/Library/Application Support/Google/Chrome and then Chrome would open. I need to find a way to script this change so I can change the permissions on the users folder. Does anyone have a script for that that they would share?

seanjsgallagher
Contributor

So I looked at some scripts I had used in the past and put together the script below to change the permissions on the '~/Library/Application Support/Google/Chrome". I have tested it only on a Catalina Machine with Google Chrome as a policy and it worked for me to change the permissions.

!/bin/bash

consoleuser=$(ls -l /dev/console | awk '{ print $3 }')

echo "logged in user is" $consoleuser

folders=(
"/Users/$consoleuser/Library/Application Support/Google/Chrome"

)

search="*"

for i in "${folders[@]}"
do echo "change folder ${i}" chmod -R 775 "${i}"
done

if [ $? == 0 ]; then echo "Success"
else echo "Failure"
fi