The chromium-browser package in Ubuntu's LTS repos is rather old for the older 12.04LTS & 14.04LTS. See this search of Ubuntu's packages for chromium-browser to see that chromium-browser is at:

  • version 37.x in 12.04LTS (Apparently from June 2014)
  • version 53.x in 14.04LTS (Apparently from June 2016)
  • version 55.x in 16.04LTS through 16.10

Whereas Firefox is at version 51.0.1x in every currently supported Ubuntu release from Precise (12.04LTS) to Yakkety (16.10) (actually, Zesty 17.04 has version 50, but it's still March so it's not really released yet).

The official Ubuntu repositories are generally the best place to get the latest supported versions of everything, and using apt/synaptic/software center is generally the best way to update software (supported by this similar Q How to install the latest stable version of Chromium?).

Especially considering using an old web browser is generally a bad idea, and Google says that Gmail (and probably other Google apps too?) will no longer support Chrome (essentially Chromium) versions 53 & older past 2017, why have the older, still-supported Ubuntu LTS's apparently given up on Chromium?

PS. I'm not asking about why "packages in the official Ubuntu repositories [are] older than the latest (upstream) versions from Debian Sid, PPAs, the authors, etc.?" (related Q: Why don't the Ubuntu repositories have the latest versions of software?), but rather why the latest versions from Ubuntu itself aren't updated, while Firefox is.


2 Answers 2


Firefox is in main, and Canonical commits to providing security updates for software in main (which, in the case of a browser, is all of them). Chromium isn't in main, it is universe - so it is updated by volunteers. It might have simply become too much of an effort to update Chromium for 12.04, all the more so since Google doesn't support 12.04 for Google Chrome, so breaking changes might have been made since.

For 14.04, the latest versions of Chromium have failed to build, bugs have been filed with no response from maintainers. Since Chrome still supports 14.04, I assume this might be fixable, and no one has volunteered to fix it.


I know a little of this.

Beyond chromium not in main and hot having a guaranteed support policy, there are a few other reasons older versions can lag or be unsupported.

lang C++: 12.04 was released around the time that a new C++ standard was developed, and Chromium upstream soon thereafter adopted the new language features. The 12.04 system c++ runtime doesn't support them. It is possible to use build tools that were never in 12.04 and retro-fit ABI changes, but it's kind of hard. Static linking like proprietary Google Chrome isn't very good. Non-main and very old distro made this lowest priority.

arch x86: Upstream chromium dropped i386 support. Ubuntu still must support it. Firefox doesn't have this extra burden.

arch arm64: We wish to support new desktop architectures in Ubuntu, and while there are mobile phones running Chrom-e, ARM64 desktop isn't even on Chromium upstream's radar. Firefox upstream has better support.

velocity: There are fifty something major-version releases in a relatively short lifespan of project. Add that insane pace to the above troubles and and some other more minor things like next month's gtk2->gtk3 replacement, and all make chromium unusually hard to support, or harder than Firefox is.

If there are volunteers who wish to help, then I want to help you to help. Join Freenode #ubuntu-chromium . Your task is to clone the "working" packaging branches and propose merges. https://code.launchpad.net/~chromium-team


  • Interesting, thanks! Are you a maintainer for Ubuntu-Chromium, or Chromium in general? I'm not very familiar with irc, you mean the server irc.freenode.net & then #ubuntu-chromium ? If I found the right one, it appeared empty at the moment. Maybe there a more general web page?
    – Xen2050
    Mar 31, 2017 at 4:02

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .