CHROMIUM_USER_FLAGS environment variable is ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
High
|
Chad Miller |
Bug Description
The script that starts Chromium has a section that's supposed to check whether the environment variable CHROMIUM_USER_FLAGS is defined, as if so, use it rather than CHROMIUM_FLAGS.
However, the script checks if the length of the string (not the variable) "CHROMIUM_
I've attached a patch file that fixes the problem.
Steps to reproduce:
1) Set the environment variable CHROMIUM_USER_FLAGS to a non-empty string. Something like:
export CHROMIUM_
2) Run /usr/bin/
3) Look at the process's command line from ps to see if the options in CHROMIUM_USER_FLAGS are included.
Expected behavior: The flags from CHROMIUM_USER_FLAGS are added to the command line, and the flags from CHROMIUM_FLAGS are not.
Observed behavior: The flags from CHROMIUM_FLAGS are used, and the flags from CHROMIUM_USER_FLAGS are ignored.
Changed in chromium-browser (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → High |
status: | New → Fix Committed |
I'm fixing in 14.10 U only. It's too dangerous to change in 14.04 T and 12.04 P.