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

Issue 834228 link

Starred by 1 user
Status: WontFix
Owner:
█ timbrown@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
vamshi.kommuri@chromium.org
thomasanderson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome 66 fails install on CentOS 7

Reported by christop...@gmail.com, Apr 18 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36

Steps to reproduce the problem:
1. Install CentOS 7 with the standard Chrome repo (http://dl.google.com/linux/chrome/rpm/stable/)

2. Run yum -y install google-chrome-stable

What is the expected behavior?
Chrome 66 should be installed. This still works for 65.

What went wrong?
Yum complains about missing dependency:

Package: google-chrome-stable-66.0.3359.117-1.x86_64 (google-chrome)
Requires: libappindicator3.so.1()(64bit)

The issue has been raised with CentOS upstream (RHEL), where it is treated as a Chrome bug, not an OS one:

https://bugzilla.redhat.com/show_bug.cgi?id=1544362

From comments on that issue:

"It seems google-chrome-unstable-66.0.3343.3-1.x86_64 [now stable] has a dependency on a 32bit version of libappindicator3.so.1 (hence no 64bit marker in the name), is probably wrong. So not a bug in rpm but in google-chrome-unstable."

Did this work before? N/A 

Chrome version: 66.0.3359.117  Channel: stable
OS Version: CentOS 7
Flash Version:

Comment 1 by christop...@gmail.com, Apr 18 2018 

Nevermind, this can be solved by installing EPEL and package libappindicator from there.

yum -y install epel-release
yum -y install libappindicator

Comment 2 by vamshi.kommuri@chromium.org, Apr 18 2018

Labels: Needs-Triage-M66

Comment 3 by vamshi.kommuri@chromium.org, Apr 19 2018

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
Thanks for filing the issue!

The issue seems to be out of scope for triaging from our end as this is related to CentOS 7 which isn't available with us currently, hence adding label "TE-NeedsTriageHelp" and requesting some one from Dev team to have a look into it and help in further triaging the issue.

Comment 4 by thomasanderson@chromium.org, May 1 2018

Cc: thomasanderson@chromium.org
Owner: timbrown@chromium.org
Status: Assigned (was: Unconfirmed)
timbrown: isn't this fixed on ToT?  Was the fix ever merged to M66?

Comment 5 by timbrown@chromium.org, May 1 2018

Status: WontFix (was: Assigned)
These are two separate issues. There was a problem (our/my fault) where I accidentally added a dependency on the 32-bit version of libappindicator instead of the 64-bit version (which is the redhat bug linked by the OP). That was fixed a while ago.

The issue the OP had was that they had disabled the repo (EPEL) which contained libappindicator.

In other words, there is nothing for us to fix.
►

Sign in to add a comment