# Travis is downloading older Chrome versions in place of chrome: stable **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** build-env\ **Created:** [September 10, 2019, 7:51pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040 "2019-09-10T19:51:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![tmcconechy](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/tmcconechy/32/2679_2.png) [@tmcconechy](https://travis-ci.community/u/tmcconechy)\ **Post date:** [September 10, 2019, 7:51pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/1 "2019-09-10T19:51:35Z")
Suddenly today (approx 25 minutes ago) our builds started to download an older version of chrome. This causes chrome driver to fail. We are using the following in our .travis.yml addons: chrome: stable This had been working fine: Before: [https://travis-ci.com/infor-design/enterprise/jobs/232840997#L517](https://travis-ci.com/infor-design/enterprise/jobs/232840997#L517) Now: [https://travis-ci.com/infor-design/enterprise/jobs/233764514#L492](https://travis-ci.com/infor-design/enterprise/jobs/233764514#L492) Is this being worked on or is it an unknown problem or change needed in our config? The issue is that this fails all the tests now. [https://travis-ci.com/infor-design/enterprise/jobs/233757159#L585](https://travis-ci.com/infor-design/enterprise/jobs/233757159#L585) Im not sure if this is related but if i try manually installing chrome i get this error: [https://travis-ci.com/infor-design/enterprise/jobs/233773743#L1709](https://travis-ci.com/infor-design/enterprise/jobs/233773743#L1709) Any Suggestions Please? We are totally stuck now. ---
**Author:** ![wedamija](https://avatars.discourse-cdn.com/v4/letter/w/22d042/32.png) [@wedamija](https://travis-ci.community/u/wedamija)\ **Post date:** [September 10, 2019, 8:51pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/2 "2019-09-10T20:51:13Z")
I’m seeing the same, and having the same issue with Chromedriver. ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [September 10, 2019, 9:01pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/3 "2019-09-10T21:01:48Z")
First, you are downloading `chrome: beta` in the failing job. ([https://travis-ci.com/infor-design/enterprise/jobs/233764514/config](https://travis-ci.com/infor-design/enterprise/jobs/233764514/config)) Second, [https://travis-ci.com/infor-design/enterprise/jobs/233764514#L424](https://travis-ci.com/infor-design/enterprise/jobs/233764514#L424) (I actually found it by searching the raw log for “chrome”): > dpkg-deb: error: archive ‘/tmp/google-chrome-beta\_current\_amd64.deb’ has premature member ‘control.tar.xz’ before ‘control.tar.gz’, giving up Means that `dpkg` cannot understand the package’s format. Since `xz` is a newer format than `gz`, this most likely means that `dpkg` is too old. I.e. that **Google has dropped Trusty support in its Chrome `.deb` packages, and you need to migrate to Xenial or Bionic.** The Chrome version that you see further on is presumably a preinstalled one. ---
**Author:** ![dominic](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dominic/32/14_2.png) [@dominic](https://travis-ci.community/u/dominic)\ **Post date:** [September 11, 2019, 2:26am UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/4 "2019-09-11T02:26:10Z")
I’m trying to get confirmation (e.g. from Google) but I believe @native-api is right: Google has dropped Trusty support for Chrome [with the latest release today](https://chromereleases.googleblog.com/2019/09/stable-channel-update-for-desktop.html). As mentioned, the best suggestion would be to try to run your builds on Xenial instead with `dist: xenial` in your .travis.yml file. ---
**Author:** ![tmcconechy](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/tmcconechy/32/2679_2.png) [@tmcconechy](https://travis-ci.community/u/tmcconechy)\ **Post date:** [September 11, 2019, 2:03pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/5 "2019-09-11T14:03:34Z")
Thanks @dominic and @native-api. Using xenial seems to work. I only needed to change dist: trusty to dist: xenail Two follow up questions: 1. Any problem using this on our open source builds? I see this from that reference page link: > Please note that Xenial is available on our hosted fully virtualized infrastructure. If you are running an Enterprise installation, please reach out to [enterprise@travis-ci.com](mailto:enterprise@travis-ci.com) to see how you can use the Xenial Docker images. 1. Is there a VM that that mimics this for docker [https://hub.docker.com/u/travisci/](https://hub.docker.com/u/travisci/) i should use? We need this for visual image regression tests when creating them for development. Thanks ---
**Author:** ![dominic](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dominic/32/14_2.png) [@dominic](https://travis-ci.community/u/dominic)\ **Post date:** [September 11, 2019, 2:22pm UTC](https://travis-ci.community/t/travis-is-downloading-older-chrome-versions-in-place-of-chrome-stable/5040/6 "2019-09-11T14:22:46Z")
@tmcconechy Glad to hear switching to Xenial helped. Here are the answers to your questions: 1. You can definitely use Xenial for your open source builds on both [travis-ci.org](http://travis-ci.org) and [travis-ci.com](http://travis-ci.com). This is what we mean when we say “our hosted fully virtualized infrastructure”. In fact, it’s now the default distribution too: [https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment](https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment). 2. Since we don’t have a container-based infrastructure anymore, we unfortunately don’t provide equivalent Docker containers like we did in the past. If it helps, you have the option to connect directly to the VM using [our debug mode feature](https://docs.travis-ci.com/user/running-build-in-debug-mode/). Take note that this needs to be enabled manually by us for open source repositories. Just reach out to `support [AT] travis-ci [DOT] com` if needed. Hope this helps!