How to Install and Use UnGoogled Chromium Safely

Troubleshooting Common Issues in UnGoogled Chromium

UnGoogled Chromium strips Google integration from Chromium to improve privacy and control. That can occasionally cause behavior different from mainstream Chromium or Chrome. This guide walks through common problems, diagnostic steps, and concrete fixes.

1. Installation fails or package not found

• Cause: Missing repository, wrong package name, or incompatible build for your OS.
• Fixes:
  1. Confirm you’re using the correct package name for your platform (e.g., ungoogled-chromium on many Linux distros, unofficial builds or portable binaries for Windows/macOS).
  2. On Linux, add the appropriate third-party repository or use an AUR helper for Arch. Update package lists:
     • Debian/Ubuntu: sudo apt update && sudo apt install ungoogled-chromium
     • Arch/Manjaro: use yay -S ungoogled-chromium or the AUR package.
  3. If using a prebuilt binary, verify system architecture (x86_64 vs arm64) and permissions. Make the binary executable:
     bash

     chmod +x ./ungoogled-chromium

  4. If building from source, ensure build dependencies and correct build flags; follow the project’s README.

2. Extensions don’t install or run

• Cause: UnGoogled Chromium disables Chrome Web Store integration and some extension APIs for privacy.
• Fixes:
  1. Install extensions from CRX files or alternative stores (e.g., webextension install links). Drag-and-drop the .crx into the Extensions page (chrome://extensions) or use “Load unpacked” for developer builds.
  2. If an extension uses Google-specific APIs (identity, push), it may not work. Look for privacy-respecting alternatives.
  3. Enable required extension APIs intentionally only if you understand the privacy trade-offs; check browser flags or patch settings used in your build.

3. Sites ask you to “use Chrome” or block the browser

• Cause: Some sites detect browser user-agent or expect Google services.
• Fixes:
  1. Try changing the user-agent temporarily via a user-agent switcher extension or developer tools to a Chromium/Chrome UA string.
  2. If the site requires Google services (e.g., proprietary DRM or sign-in), you may need a different browser for that site or accept partial functionality.
  3. Inspect the site console (F12) for errors pointing to blocked Google scripts and consider selectively allowing required domains if you trust them.

4. DRM / Widevine-protected content won’t play

• Cause: Widevine CDM is not bundled and may be blocked for privacy reasons.
• Fixes:
  1. Obtain Widevine for your platform (some distributions provide a package or you can extract it from Chrome). Install and register the module per your distro’s instructions.
  2. On Linux, use a helper package (where available) that fetches Widevine from Chrome.
  3. If you prefer privacy over playback, accept that DRM media may remain inaccessible.

5. Sync, sign-in, or Google account features missing

• Cause: Intentional removal of Google services.
• Fixes:
  1. Use alternative sync solutions: local profile backups, third-party sync (e.g., Firefox Sync for bookmarks via export/import), or file-syncing services you control.
  2. For password management, use a standalone password manager instead of built-in Chrome passwords.

6. Performance issues or crashes

• Cause: Build-specific bugs, missing optimizations, incompatible flags, or extensions.
• Fixes:
  1. Start in a clean profile: run with –user-data-dir=/tmp/ungc-test to see if the issue persists.
  2. Disable all extensions and re-enable one-by-one to isolate offenders.
  3. Launch with default flags (avoid aggressive privacy patches that disable sandboxing unless you understand risks).
  4. Check logs and crash reports in chrome://crashes (if enabled) or run from terminal to capture output.
  5. Install a different build (official ungoogled release vs community build) to see if problems are build-specific.

7. Networking problems (DNS, proxy, or blocked requests)

• Cause: Privacy patches may block certain hostnames or alter DNS resolution.
• Fixes:
  1. Verify system DNS and proxy settings outside the browser.
  2. Temporarily disable any host-blocking lists or adblocking to confirm the cause.
  3. If you use a custom hosts file or filters, remove entries affecting required domains.
  4. Use developer tools (Network tab) to see which requests are failing and why.

8. Certificate or HTTPS errors

• Cause: Missing system CA certificates, strict pinning, or blocked OCSP/CRL checks.
• Fixes:
  1. Ensure your OS has up-to-date CA certificates installed.
  2. If OCSP/CRL requests are blocked by privacy settings, temporarily allow them for needed sites.
  3. Inspect the specific TLS error in the browser and address it (expired cert, hostname mismatch, etc.).

9. Problems after updating UnGoogled Chromium

• Cause: Configuration changes, incompatible flags, or profile format changes.
• Fixes:
  1. Backup your profile before updating: copy the user-data directory.
  2. After update, start with a fresh profile to test; then selectively migrate extensions and settings.
  3. Check the changelog for breaking changes and required configuration updates.

Diagnostic checklist (quick)

1. Reproduce in a fresh profile (–user-data-dir).
2. Disable extensions.
3. Run from terminal and capture output.
4. Check developer console for errors.
5. Try a different ungoogled build or an official Chromium/Chrome to isolate whether it’s specific to UnGoogled Chromium.
6. Restore system certificates and DNS/proxy defaults temporarily.

When to report a bug

• Collect steps to reproduce, browser version/build, OS, terminal output/crash logs, and any relevant console/network traces. Report to the build’s issue tracker (include your build’s origin and exact version).

Final notes

UnGoogled Chromium trades some convenience for privacy and control. Many “issues” are intentional design choices; weigh fixes against privacy trade-offs and prefer targeted exceptions over broad re-enabling of Google services.