desktop-packages team mailing list archive

[Kyle Brenneman <kyle.brenneman@xxxxxxxxx>]

Public bug reported:

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_USER_FLAGS" is zero, which of course is always
false. As a result, it never uses CHROMIUM_USER_FLAGS at all.

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_USER_FLAGS="--password-store=gnome"
2) Run /usr/bin/chromium-browser
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.

** Affects: chromium-browser (Ubuntu)
     Importance: Undecided
         Status: New

** Patch added: "chromium-user-flags-fix.patch"
   https://bugs.launchpad.net/bugs/1381644/+attachment/4237408/+files/chromium-user-flags-fix.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1381644

Title:
  CHROMIUM_USER_FLAGS environment variable is ignored

Status in “chromium-browser” package in Ubuntu:
  New

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_USER_FLAGS" is zero, which of course is always
  false. As a result, it never uses CHROMIUM_USER_FLAGS at all.

  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_USER_FLAGS="--password-store=gnome"
  2) Run /usr/bin/chromium-browser
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1381644/+subscriptions