[FIX] Archlinux not opening chrome when clicking the "website" link
[FIX] Archlinux not opening chrome when clicking the "website" link
Hi everyone,
I'm having an issue with RDM on Arch Linux. When I set Google Chrome as my default browser, website links fail to open consistently. I discovered that RDM searches for a /bin/chromium file. If you have the google-chrome-stable package installed, RDM won't be able to find and launch it.
To resolve this problem, simply run the following command:
sudo ln -s /bin/google-chrome-stable /bin/chromium
This will create a symbolic link from /bin/google-chrome-stable to /bin/chromium, allowing RDM to find and launch Google Chrome as expected.
Please let me know if anyone else is encountering this issue.
All Comments (1)
Hi dmoro,
It indeed searches for "/bin/chromium", but also "/bin/google-chrome". As it happens, the official packages on Debian and RedHat distributions automatically add a link called "google-chrome" pointing to "google-chrome-stable" or the unstable version depending on what is installed. However, since all Google Chrome packages on Arch (outside of base Chromium of course) are user-maintained repositories in the AUR, we didn't check for the name of their binaries because we couldn't guarantee how user created package repositories would have the binaries called or if they would create the correct link or even that they wouldn't be changed by their maintainers over time to some other binary name. Due to all those reasons, we decided to go with the nomenclature of the official packages because we felt confident they wouldn't drastically change any time soon. To circumvent that, the solution you offered is also what I would also personally recommend (or a symbolic link with the name "google-chrome" like what the Debian and RedHat packages we looked that did). Another solution would be to leave the option "Web Browser" to Default. That will instead call "xdg-open" and automatically open your default web browser. However, that has some limitations and will ignore some of your connection's settings.
I hope this helped. We will look into falling back to the binary name "google-chrome-stable" for those of you who have this same issue, but we hope that the solutions that dmoro and I offered will help any of you with the same problem in the meantime.
Best regards.
Nicolas Parr