Fedora 27 + google-chrome-stable (66) => nothing provides libappindicator3.so.1

227 views
Skip to first unread message

Mike P.

unread,
Apr 30, 2018, 2:37:44 AM4/30/18
to Chromium-discuss
Hello,

I've been using Google Chrome on Fedora for years now, and a recent update (trying to install stable 66.x) is blocked by the following dependency error:

```
$ sudo dnf install google-chrome-stable
Last metadata expiration check: 0:00:00 ago on Thu 26 Apr 2018 11:13:11 AM PDT.
Error: 
 Problem: conflicting requests
  - nothing provides libappindicator3.so.1()(64bit) needed by google-chrome-stable-66.0.3359.117-1.x86_64
```

This bugzilla seems to hint that this root cause might be an RPM packaging problem: https://bugzilla.redhat.com/show_bug.cgi?id=1544362

...as the participants in the thread seem to be troubleshooting for CentOS (ie. solution suggests installing `EPEL` repo + `libappindicator-gtk3` package), but there don't seem to be any packages available in Fedora repos that satisfy this dependency symbol.

Alternatively, trying to install 
`chromium` suffers a similar, but different dependency problem:

```
$ sudo dnf install -y chromium
Last metadata expiration check: 0:02:03 ago on Fri 27 Apr 2018 11:17:35 AM PDT.
Error: 
 Problem: conflicting requests
  - nothing provides libminizip.so.1()(64bit) needed by chromium-65.0.3325.181-1.fc27.x86_64

$ dnf whatprovides libminizip*
Last metadata expiration check: 0:06:06 ago on Fri 27 Apr 2018 11:15:08 AM PDT.
Error: No Matches found
```

If anyone here is be familiar with Google Chrome's packaging for Fedora, any ideas as to what I could try next to get either browser installed?

Thanks!

PhistucK

unread,
Apr 30, 2018, 2:50:56 AM4/30/18
to emp...@gmail.com, Chromium-discuss
You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.


PhistucK


--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

Mike P.

unread,
Apr 30, 2018, 1:34:33 PM4/30/18
to Chromium-discuss, emp...@gmail.com
Thanks for the response PhistucK. I've resolved my issue, the primary fedora repo was manually disabled earlier from a previous package troubleshooting session, and so re-enabling it fixed the problem for me.

Thanks again for the response and the advice though- good to know for future reference.
Reply all
Reply to author
Forward
0 new messages