DescriptionRevert of Fix SELinux violation when opening Chrome on Android (patchset #4 id:60001 of https://codereview.chromium.org/1655983002/ )
Reason for revert:
Given the M bot that this broke, plus http://crbug.com/585421, I'm reverting until I can properly sort out the bugs here.
Original issue's description:
> Fix SELinux violation when opening Chrome on Android
>
> This was caused by calling PathUtils.setPrivateDataDirectorySuffix()
> on the renderer process. Moving that call into
> ChromeBrowserInitializer should fix this.
>
> BUG=560152
>
> Committed: https://crrev.com/b5ce1bf969e760539c96fd215756dd1716415f25
> Cr-Commit-Position: refs/heads/master@{#373820}
TBR=yfriedman@chromium.org,simonb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=560152
Committed: https://crrev.com/cfe52d9360013f0078ad6aa7ae7317e6b524b72c
Cr-Commit-Position: refs/heads/master@{#374666}
Patch Set 1 #
Messages
Total messages: 8 (1 generated)
|