P. G. wrote:
There was already a google-chrome-stable repo in yum.repos.d from before, so I updated chrome. This is where the problems/confusion began...
- google-chome-stable is no longer located in /usr/bin
- no links appear in the launcher (easy to create manually)
- dead links to the executable in /usr/bin and
/etc/alternatives 4. chrome is now installed to /opt 5. the google chome repo file has vanished from yum.repos.d 6. privacy badger does not recognize chrome in /opt and no amount of uninstalling, closing down chrome, restarting and freshly installing the badger would get it to work
So...
Can I manually create the google-chrome-stable repo file and will it now update the version installed to /opt, or is this going to cause a big mess?
Or, do I henceforth have to uninstall chrome and reinstall for every new upgrade?
I think there was a fairly brief hiatus in google-chrome-stable in Fedora-24, which has been cured by the most recent update.
ls -ls /usr/bin/google* Sep 4 12:19 /usr/bin/google-chrome -> /etc/alternatives/google-chrome Sep 2 00:20 /usr/bin/google-chrome-stable -> /opt/google/chrome/google- chrome ls -ls /etc/alternatives/google-chrome Sep 4 12:19 /etc/alternatives/google-chrome -> /usr/bin/google-chrome- stable