desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #147944
[Bug 1514484] [NEW] Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
Public bug reported:
You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever
comes after the first space is going to be interpreted as an URL by the
actual chromium binary. Easy repro:
1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg:
$ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init
2. Run chromium:
$ /usr/bin/chromium-browser
3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'.
The cause for this funny behavior is the lack of quotes around
$CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser --
it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script.
I've tried working around it but couldn't, no amount of escaping and
extra quotes seems to help if it's called like that.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "Patch adding quotes to /usr/bin/chromium-browser"
https://bugs.launchpad.net/bugs/1514484/+attachment/4515594/+files/patch.txt
--
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/1514484
Title:
Chromium start-up script doesn't accept argument values with spaces in
$CHROMIUM_FLAGS, cause is lack of quotes
Status in chromium-browser package in Ubuntu:
New
Bug description:
You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever
comes after the first space is going to be interpreted as an URL by
the actual chromium binary. Easy repro:
1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg:
$ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init
2. Run chromium:
$ /usr/bin/chromium-browser
3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'.
The cause for this funny behavior is the lack of quotes around
$CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser
-- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the
script. I've tried working around it but couldn't, no amount of
escaping and extra quotes seems to help if it's called like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+subscriptions
Follow ups
-
[Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
From: Miyuki Taniguchi, 2015-11-22
-
[Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
From: Iuri Chaer, 2015-11-10
-
[Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
From: Iuri Chaer, 2015-11-10
-
[Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
From: Chad Miller, 2015-11-09
-
[Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
From: Ubuntu Foundations Team Bug Bot, 2015-11-09