Bug 1544362 - rpm can't find provides for libappindicator3 even though it is installed
Summary: rpm can't find provides for libappindicator3 even though it is installed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-12 09:37 UTC by darrell pfeifer
Modified: 2018-04-23 07:35 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-12 09:44:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description darrell pfeifer 2018-02-12 09:37:26 UTC
dnf download google-chrome-unstable
Last metadata expiration check: 0:42:53 ago on Mon 12 Feb 2018 12:43:23 AM PST.
google-chrome-unstable-66.0.3343.3-1.x86_64.rpm                                                18 MB/s |  51 MB     00:02    

rpm -Uvh goo*.rpm
error: Failed dependencies:
        libappindicator3.so.1 is needed by google-chrome-unstable-66.0.3343.3-1.x86_64

rpm -q --whatprovides libappindicator3.so.1
no package provides libappindicator3.so.1

rpm -q --provides libappindicator-gtk3
libappindicator-gtk3 = 12.10.0-16.fc27
libappindicator-gtk3(x86-64) = 12.10.0-16.fc27
libappindicator3.so.1()(64bit)

[root@localhost darrell]# dnf list libappindicator-gtk3
Last metadata expiration check: 0:46:28 ago on Mon 12 Feb 2018 12:43:23 AM PST.
Installed Packages
libappindicator-gtk3.x86_64                                       12.10.0 16.fc27                                        @koji

dnf list rpm
Last metadata expiration check: 0:49:59 ago on Mon 12 Feb 2018 12:43:23 AM PST.
Installed Packages
rpm.x86_64                                                4.14.1-6.fc28.1

Comment 1 Panu Matilainen 2018-02-12 09:44:19 UTC
libappindicator3.so.1 is not the same as libappindicator3.so.1()(64bit)

It seems google-chrome-unstable-66.0.3343.3-1.x86_64 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.

Comment 2 Christopher Svanefalk 2018-04-18 08:59:25 UTC
This is still an issue now that Google Chrome 66 is stable:

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

Comment 3 Christopher Svanefalk 2018-04-18 09:19:51 UTC
this can be solved by installing EPEL and package libappindicator from there.

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

Comment 4 Kristian Windsor 2018-04-20 16:28:54 UTC
I am also experiencing this issue with Chrome Stable v64 on Centos 7

> sudo yum install google-chrome-stable
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      Resolving Dependencies
      --> Running transaction check
      ---> Package google-chrome-stable.x86_64 0:66.0.3359.117-1 will be installed
      --> Processing Dependency: libappindicator3.so.1()(64bit) for package: google-chrome-stable-66.0.3359.117-1.x86_64
      --> Finished Dependency Resolution
      Error: Package: google-chrome-stable-66.0.3359.117-1.x86_64 (google-chrome)
                 Requires: libappindicator3.so.1()(64bit)

> sudo yum -y install epel-release
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      Nothing to do

> sudo yum -y install libappindicator
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      No package libappindicator available.
      Error: Nothing to do

> sudo wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> sudo rpm -ivh epel-release-latest-7.noarch.rpm
      warning: epel-release-latest-7.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
      Preparing...                          ################################# [100%]
              package epel-release-7-11.noarch is already installed

Comment 5 Panu Matilainen 2018-04-23 07:35:58 UTC
Folks, this is not a Google Chrome support forum.


Note You need to log in before you can comment on or make changes to this bug.