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 Ubuntu
Bugs, which is subscribed to 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
