File: master-preferences.patch

package info (click to toggle)
chromium 140.0.7339.185-1
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 6,193,740 kB
  • sloc: cpp: 35,093,945; ansic: 7,161,670; javascript: 4,199,694; python: 1,441,797; asm: 949,904; xml: 747,515; pascal: 187,748; perl: 88,691; sh: 88,248; objc: 79,953; sql: 52,714; cs: 44,599; fortran: 24,137; makefile: 22,114; tcl: 15,277; php: 13,980; yacc: 9,000; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (21 lines) | stat: -rw-r--r-- 796 bytes parent folder | download | duplicates (7) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
 
description: search for {initial,master}_preferences in /etc/chromium
author: Andres Salomon <dilinger@debian.org>

The default chromium behavior of checking the current binary directory for
initial_preferences or master_preferences doesn't conform to debian policy.

--- a/chrome/browser/first_run/first_run_internal_linux.cc
+++ b/chrome/browser/first_run/first_run_internal_linux.cc
@@ -19,11 +19,7 @@ bool IsOrganicFirstRun() {
 }
 
 base::FilePath InitialPrefsPath() {
-  // The standard location of the initial prefs is next to the chrome binary.
-  base::FilePath dir_exe;
-  if (!base::PathService::Get(base::DIR_EXE, &dir_exe)) {
-    return base::FilePath();
-  }
+  base::FilePath dir_exe = base::FilePath("/etc/chromium");
 
   return installer::InitialPreferences::Path(dir_exe);
 }