How to Install Google Chrome on Ubuntu (Engineer's Approach)
Google Chrome is not included in Ubuntu’s default repositories due to licensing restrictions. Still, integration is straightforward and generally stable on LTS releases (tested: Ubuntu 22.04, 20.04). Below, concrete procedures for both graphical (GUI) and command-line (CLI) installations, including common debugging and automation options.
Direct Download & Graphical Install
Requirement: ubuntu-software or gdebi installed (default on Ubuntu Desktop).
1. Obtain the Installer:
- Open Firefox or another browser.
- Download Chrome’s latest
.debfor Debian/Ubuntu from
https://www.google.com/chrome/. - Confirm download of:
google-chrome-stable_current_amd64.deb
(Checksum validation optional but recommended for scripts.)
2. Trigger Installation:
- Navigate to the Downloads directory.
- Double-click the
.debfile. This launches Ubuntu Software Center. - Click Install → Authenticate.
Note: Occasionally, the Software Center hangs at "Waiting to Install…"; if so, fallback to command-line (sudo dpkg -i …).
3. Launch & Configure:
- Find Google Chrome in Activities/Search, launch.
- (Optional) Set as default. Sync via Google account if required by workflow.
Install via Terminal (Scriptable, Repeatable)
Standard method with wget/curl (no snap):
# Update package metadata
sudo apt update
# Fetch official .deb (as of 2024-06, version typically >=126.0.x)
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
# Install the package
sudo dpkg -i google-chrome-stable_current_amd64.deb
# Resolve unmet dependencies (often libappindicator, libnss3, etc.)
sudo apt -f install
Known issue:
If you see
dpkg: error processing package google-chrome-stable (--install): dependency problems - leaving unconfigured
Run sudo apt -f install again, then re-run sudo dpkg -i.
Fast test launch (doesn't block shell):
google-chrome &
If you run into
[24551:24551:0607/151229.500133:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
try updating libnss3 or running with --no-sandbox (but don’t use --no-sandbox in production).
Keeping Chrome Updated
After .deb install, /etc/apt/sources.list.d/google-chrome.list will contain:
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Chrome patches are then handled by apt upgrade, integrating with your normal system update cadence.
Check for repo presence:
cat /etc/apt/sources.list.d/google-chrome.list
Troubleshooting and Real-World Notes
| Symptom | Fix/Note |
|---|---|
| Chrome fails to start (no output) | Try launching from terminal, check logs |
| Dependency errors (dpkg) | Run sudo apt -f install |
| Profile corruption after crash | Remove ~/.config/google-chrome (last resort, profile is lost) |
| Hardware DRM fails (Netflix, etc.) | Ensure libwidevinecdm0 is installed; test in Chrome, not Chromium |
| Usage in minimal installs (no GUI) | Use --headless mode for CI pipelines |
Non-Obvious Tips
- For automated rollouts, apt pinning or puppet/ansible modules can handle version control; direct
.debinstallation is fine for one-off machines but not ideal on fleets. - Some GNOME environments show two Chrome launchers after upgrade. Remove redundant
.desktopentries in~/.local/share/applications/.
Sample Install Script for CI or Lab Setup
set -e
sudo apt update
wget -qO /tmp/chrome.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install -y ./tmp/chrome.deb || sudo apt -f install -y
Summary:
Google Chrome on Ubuntu is a routine, production-weight install. GUI method suffices for ad-hoc use; automated or bulk deployment should leverage CLI and scripts. Monitor Google’s repository for update cadence aligning with security posture.
If downstream Chromium (snap/ppa) suffices for your workflow, consider it for stricter open-source policies—but expect some media/playback incompatibilities.