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.
The attachment "Patch adding quotes to /usr/bin/ chromium- browser" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]