summaryrefslogtreecommitdiff
path: root/devel/electron4/files/patch-chrome_app_chromium__strings.grd
diff options
context:
space:
mode:
Diffstat (limited to 'devel/electron4/files/patch-chrome_app_chromium__strings.grd')
-rw-r--r--devel/electron4/files/patch-chrome_app_chromium__strings.grd11
1 files changed, 11 insertions, 0 deletions
diff --git a/devel/electron4/files/patch-chrome_app_chromium__strings.grd b/devel/electron4/files/patch-chrome_app_chromium__strings.grd
new file mode 100644
index 000000000000..d91e57b0fea5
--- /dev/null
+++ b/devel/electron4/files/patch-chrome_app_chromium__strings.grd
@@ -0,0 +1,11 @@
+--- chrome/app/chromium_strings.grd.orig 2019-03-15 06:36:59 UTC
++++ chrome/app/chromium_strings.grd
+@@ -814,7 +814,7 @@ Signing in anyway will merge Chromium information like
+ </message>
+
+ <!-- ProcessSingleton -->
+- <if expr="is_linux or is_macosx">
++ <if expr="is_linux or is_macosx or is_posix">
+ <message name="IDS_PROFILE_IN_USE_POSIX" desc="Message shown when the browser cannot start because the profile is in use on a different host.">
+ The profile appears to be in use by another Chromium process (<ph name="PROCESS_ID">$1<ex>12345</ex></ph>) on another computer (<ph name="HOST_NAME">$2<ex>example.com</ex></ph>). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.
+ </message>