From aa013ba745d78caa0de890086a67d1f8dded09c9 Mon Sep 17 00:00:00 2001
From: Peter Hedenskog <peter@soulgalore.com>
Date: Mon, 18 Feb 2019 12:40:53 +0100
Subject: [PATCH] Remove Chrome specific setup (#2322)

This has been removed in Selenium (I think) and also see
https://github.com/sitespeedio/sitespeed.io/issues/1459#issuecomment-464509929
---
 docker/scripts/start.sh | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/docker/scripts/start.sh b/docker/scripts/start.sh
index ea2520fe5..65c40c5bf 100755
--- a/docker/scripts/start.sh
+++ b/docker/scripts/start.sh
@@ -25,17 +25,6 @@ else
   WPR_HTTPS_PORT=${WPR_HTTPS_PORT:-443}
 fi
 
-# Here's a hack for fixing the problem with Chrome not starting in time
-# See https://github.com/SeleniumHQ/docker-selenium/issues/87#issuecomment-250475864
-function chromeSetup() {
-  sudo rm -f /var/lib/dbus/machine-id
-  sudo mkdir -p /var/run/dbus
-  sudo service dbus restart > /dev/null
-  service dbus status > /dev/null
-  export $(dbus-launch)
-  export NSS_USE_SHARED_DB=ENABLED
-}
-
 # If we run Chrome on Android, we need to start the ADB server
 function setupADB(){
   # Start adb server and list connected devices
@@ -127,7 +116,6 @@ function runSitespeedio(){
   wait $PID
 }
 
-chromeSetup
 setupADB
 
 if [ $REPLAY ]