The Chromium version is 55.0.2883.75-4.

Attached is the launcher script. Here is the section where the error occurs:


if [ $want_debug -eq 1 ] ; then
  if [ ! -x $GDB ] ; then
    echo "Sorry, can't find usable $GDB. Please install it."
    exit 1
  fi
  tmpfile=`mktemp /tmp/chromiumargs.XXXXXX` || { echo "Cannot create temporary file" >&2; exit 1; }
  trap " [ -f \"$tmpfile\" ] && /bin/rm -f -- \"$tmpfile\"" 0 1 2 3 13 15
  echo "set args $CHROMIUM_FLAGS --single-process ${1+"$@"}" > $tmpfile
  echo "# Env:"
  echo "#     LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
  echo "#                PATH=$PATH"
  echo "#            GTK_PATH=$GTK_PATH"
  echo "#      CHROMIUM_FLAGS=$CHROMIUM_FLAGS"
  echo "$GDB $LIBDIR/$APPNAME -x $tmpfile"
  $GDB "$LIBDIR/$APPNAME" -x $tmpfile
  if [ $want_temp_profile -eq 1 ] ; then
    rm -rf $TEMP_PROFILE
  fi
  exit $?
else
  if [ $want_temp_profile -eq 0 ] ; then
    exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
  else
    # we can't exec here as we need to clean-up the temporary profile
    $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
    rm -rf $TEMP_PROFILE
  fi                          # ERROR - Syntax error: "fi" unexpected (expecting "}")
fi

Deleted: chromium 3.5 KB

chromium 3.5 KB View Download

Downgraded to chromium_55.0.2883.75-3_amd64.deb and the problem went away.

Tested on chrome #55.0.2883.59 and #57.0.2984.0 on Ubuntu 14.04 and not able to reproduce the issue.Please find the screen shots for your reference.

@keanetoken:
Could you please check with latest versions and let us know the behavior of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 681955.png 29.6 KB

	681955.png 29.6 KB View Download

Upgrading today did not fix the issue. I can't install dependencies to build a newer version:

~$ sudo apt build-dep chromium
[sudo] password for keantoken: 
Reading package lists... Done
Picking 'chromium-browser' as source package instead of 'chromium'
Selected version '55.0.2883.75-4' (unstable) for chromium-browser
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:chromium-browser : Depends: libpci-dev but it is not going to be installed
                              Depends: libudev-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
keantoken@ronin:~$ sudo apt install libpci-dev libudev-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libudev-dev : Depends: libudev1 (= 232-11) but 232-10 is to be installed

OP: The script that contains the syntax error is provided by the chromium_browser package from Debian.  The official chromium repo does not have that file.

Please try to see if you can reproduce with google-chrome-stable.  If you cannot, try opening a bug with Debian.

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@ keanetoken : Could you please update on Comment #6 and please confirm if the issue is still seen on the latest stable(56.0.2924.87) on your system.

Thank You!

@keanetoken, can see it has been an year since this issue was reported. Could you please confirm if the issue persists your side? 

Thanks!
GS

As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end.

Thanks!