[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-11-18 Thread Nathan Pratta Teodosio
My proposed fix to Chromium start-up script wasn't foolproof. One can naturally also export CHROMIUM_FLAGS instead of defining it in ~/chromium.init. Passing arguments via a variable is a bad idea if one wants both to be reliable with odd input (i.e. accept arguments with spaces (as in the bug

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-10-21 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-09-20 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-09-20 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-09-19 Thread Nathan Teodosio
When a string is put in a shell variable, white-space loses its syntactical information. Merely quoting $CHROMIUM_FLAGS in the launcher won't do, since we rely on word splitting to split arguments, as noted in #3. The launcher has a #!/bin/sh shebang, so it's meant as a POSIX compliant shell

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-09-19 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Tags removed: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2022-09-19 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2018-03-09 Thread Olivier Tilloy
** Changed in: chromium-browser (Ubuntu) Assignee: Chad Miller (cmiller) => (unassigned) -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2017-04-26 Thread Olivier Tilloy
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-22 Thread Miyuki Taniguchi
Space characters in chromium flags seem to be always parsed even if they are escaped. (Of course, it must be a bug.) When splitting all flags in $CHROMIUM_FLAGS by newline and running chromium after IFS=$'\n' , it works. (And do not escape spaces. like --user-agent=foo bar , not

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-10 Thread Iuri Chaer
Uh, I've tried that, but it keeps splitting the argument values no matter how many slashes I add (they end up interpreted as part of the URL -- for instance, instead of "B" chromium gives me "B/" in the address bar). I've been trying to understand what bash is doing, but it's really eluding me.

Re: [Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-10 Thread Chad Miller
I agree that it's tricky. The two solutions I can think of is your idea of an array, and assumption that the variable should go through two levels of interpretation. The way that makes current scripts and files still work is the latter. It would go like this: If there is a special character in

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-10 Thread Iuri Chaer
I noticed that last night =( so sad how often I seem to be surprised by how shell expansion works. Best I could come up with was transform CHROMIUM_FLAGS into an array and use "${CHROMIUM_FLAGS[@]}" in the calls instead. Sorry for the failed patch attempt. -- You received this bug notification

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-09 Thread Ubuntu Foundations Team Bug Bot
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

[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes

2015-11-09 Thread Chad Miller
I don' think this patch does what you expect. Try with more than one value in the variable. CHROMIUM_FLAGS='--user-data-dir=/tmp/cr --user-agent="A B C"' ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Chad Miller (cmiller) ** Changed in: chromium-browser (Ubuntu)