New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 810643 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
█ timbrown@chromium.org
█ brettw@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Unable to get --version string from released builds

Project Member Reported by alancutter@chromium.org, Feb 9 2018 
Passing in "--version" to packaged Linux Chrome Beta or Unstable binaries doesn't produce the version number. It still works for stable and dev builds though.

Bash log:

[15:20:44] ~/repos/chromium/src $ google-chrome-stable --version
Google Chrome 64.0.3282.140 
[15:20:50] ~/repos/chromium/src $ google-chrome-beta --version
[15:20:51] ~/repos/chromium/src $ google-chrome-unstable --version
[15:20:54] ~/repos/chromium/src $ out/release/chrome --version
Chromium 66.0.3344.0

Comment 1 by timbrown@chromium.org, Feb 20 2018

Cc: timbrown@chromium.org
I'm not able to reproduce this (using zsh, but if I load bash, it works as well):

~/chromium/src % google-chrome-stable --version
Google Chrome 64.0.3282.167
~/chromium/src % google-chrome-beta --version
Google Chrome 65.0.3325.73 beta
~/chromium/src % google-chrome-unstable --version
Google Chrome 66.0.3346.8 dev


What are the beta and unstable versions that you have? Can you try in a clean bash environment (or a different shell). You can get a completely clean environment by running 'env -i bash --norc --noprofile' - you'll get a couple of error messages when running chrome this way (about not being able to create files), but the version will still be printed out.

Comment 2 by alancutter@chromium.org, Feb 20 2018

Status: WontFix (was: Untriaged)
It's no longer reproing for me. I'm not sure what in my environment state could have caused this.
►

Sign in to add a comment