How to Install Chromium Browser via .deb in Ubuntu 20.04

Last updated: January 4, 2022

Prefer installing Chromium browser via DEB rather than using SNAP package? Here’s how to install Chromium .deb package in Ubuntu 20.04 via PPA.

Since Ubuntu 20.04, Chromium deb in the main repository is empty!! It will automatically install the containerized snap package when you trying to install it via apt command.

For those prefer deb to the universal snap package format, user may install the browser either from Linux Mint repository or using a third-party Ubuntu PPA.

Option 1: Install Chromium using Linux Mint repository:

Linux Mint, the popular Ubuntu based system now maintains the latest Chromium DEB packages in its repositories since the developers does not like Snap.

I’ve written about how to add the Linux Mint repository and install Chromium step by step in another post.

Option 2: Install Chromium via third-party Ubuntu PPA:

Personally, I prefer the package from Linux Mint a bit more. Though, there’s now a trustworthy third-party PPA maintains the latest Chromium package. And, the PPA supports Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04 and Ubuntu 21.04 so far. Ubuntu 21.10 is somehow not supported at the moment.

1. Add the PPA

Firstly, press Ctrl+Alt+T on keyboard to open terminal. When it opens, run command to add the PPA:

sudo add-apt-repository ppa:savoury1/chromium

Type user password (no asterisk feedback) when it asks and hit Enter to continue

For Ubuntu 20.04 and earlier, the FFmpeg PPA is also required as dependency:

sudo add-apt-repository ppa:savoury1/ffmpeg4

NOTE: Update system ffmpeg library might cause conflict to other packages in your system. It’s NOT recommended for beginners!

2. Update the package cache:

For Ubuntu 18.04 and earlier, user need to manually update the package cache after adding the PPA. To do so, run command in terminal:

sudo apt update

3. Install Chromium package:

Finally, install the Chromium browser package in .deb format via command:

sudo apt install chromium-browser

Keep an eye on terminal output, it should start downloading the package from the PPA. If not, press Ctrl+C on keyboard to stop it.

Once installed, search for and open the browser from ‘Activities‘ overview screen. And, check its version in about page.

Remove Chromium:

To remove the web browser, simply open terminal via Ctrl+Alt+T shorcut key and run command:

sudo apt remove --autoremove chromium-browser

And remove the PPA, use command:

sudo add-apt-repository --remove ppa:savoury1/chromium

For the FFmpeg PPA, it’s recommended to purge it which also downgrade all installed packages:

sudo apt install ppa-purge && sudo ppa-purge ppa:savoury1/ffmpeg4

Without downgrading the packages, you may instead remove the PPA using the previous command.

Twitter

I'm a freelance blogger who started using Ubuntu in 2007 and wishes to share my experiences and some useful tips with Ubuntu beginners and lovers. Please comment to let me know if the tutorial is outdated! And, notify me if you find any typo/grammar/language mistakes. English is not my native language. Contact me via ubuntuhandbook1@gmail.com Buy me a coffee: https://ko-fi.com/ubuntuhandbook1 |

52 responses to How to Install Chromium Browser via .deb in Ubuntu 20.04

  1. Gabba Gabba Hey! June 25, 2020 at 9:42 pm

    First ungoogled-chromium and now this, slowly but surely hardware acceleration is coming to Linux via the patched stable Chromium browser.

    Thanks man, great post!

  2. just a heads-up July 1, 2020 at 2:26 pm

    In order to work properly regular Chromium is installed with “chromium-codecs-ffmpeg-extra” package. Please update your command like so:

    sudo apt install chromium-browser chromium-codecs-ffmpeg-extra

    Thank you and keep it up!

  3. Just to let you all know, if there are concerns about trust and safety – this PPA is pre-installed to the great Ubuntu MATE based respin “Li-f-e” (Linux for Education 20.04).

  4. Thanks. This installed nicely and appears to be fully functional on Mint 20 Cinnamon, based on Ubuntu 20.04. My question is whether the PPA will update Chromium from the installed repository on the regular schedule, or will it need manual reinstalls when Chromium updates are released. So far, a great contribution for Mint / Ubuntu users.

  5. Worked perfectly on Mint Mate 20.
    Great post, thanks!

  6. this works good for intel gpu. but does not with Nvidia vdpau. is there any way to enable it also for nvidia?

  7. Thanks!
    I tried the way an “Expert” said to do it and that was a waste of time. Normally his website is good but it didn’t work. You way worked with out any problems. Thank you so much.

  8. Dan Whitehead July 25, 2020 at 7:56 pm

    Will this PPA automatically update Chromium?
    Dan W

  9. @Dan Whitehead July 26, 2020 at 7:15 pm

    Yes Dan, it will.

  10. sync working in this repo ?

    • Thanks for the reply. And i want to ask any update coming for this repo ? . Sry for bad english .

      • Maintainer here.
        I’m not planning to drop support but can’t promise anything. Releases mostly depend on Fedora patches and Ubuntu/Debian builds. If it will be dropped, I’m going to leave some information on PPA page.

  11. Hopefully yes but nobody knows that for sure except for the maintainer of the PPA. Let’s just wait and see…

  12. Hey Evgen, please don’t drop the support, your Chromium in deb format with VAAPI patch is the best thing since sliced bread!

    Thank you for all the hard work, it’s greatly appreciated, keep it up!

    • Currently Chromium 85 works for me only with launch flag
      –use-gl=desktop
      If there won’t be other way, I’ll pass it to
      /etc/chromium-browser/default

      Other good news: official Chrome 86 beta now allows to enable VAAPI
      Bad news: it doesn’t work for now. So untill Google fix it, I’ll try to rebuild Chromium
      When they fix their official build, I’ll probably drop PPA. For me VAAPI is the only reason to use customized Chromium build instead of Google Chrome.

  13. Thanks Evgen, every bit of information from you is greatly appreciated.

  14. Updated build with different patch
    There’s a chance that we’ll have VAAPI support on official Ubuntu builds!
    Please support bug report bellow on the link bellow!
    https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894433

  15. Your bug report has just been supported.

    In other news, updated Chromium to version 85 via your PPA, everything works flawlessly.

    Thank you Evgen once again, and thank you Ji m for letting us know about the PPA in the first place.

    Community working together, this is THE strength of Linux.

  16. Thank You this works! Keep creating great content about Ubuntu! it’s really helpful. Thanks Again.

  17. Cannot add PPA: ‘ppa:~xalt7x/ubuntu/chromium-deb-vaapi’.
    ERROR: ‘~xalt7x’ user or team does not exist.

  18. Thanks.

    Works great in Linux Mint 20.

  19. Installed the latest version (85.0.4183.121) earlier today and everything has been working well so far. Thank you so much and keep up the excellent work!

  20. this solution did work on Xubuntu 20.04 LTS! thx for the advice

  21. Evgen, looking forward to version 86. Thank you very much for all the hard work!

  22. I have a really strange problem with the latest build. While watching a YouTube video if I select and then drag & drop (for example to the address bar) any text on that page it messes up the hardware acceleration. Can anyone else reproduce?

  23. Hi Evgen,

    Does your PPA Chromium Browser VAAPI also works on Amlogic Arm64 with Mali G52 GPU instead of Intel or AMD GPU?

  24. Hi,

    Don’t seem to be able to start Chromium with VAAPI. OS is Ubuntu 20.04.1 Kernel 4.9.224. I notice in the Synaptic Package Manager, there is “libva2”, “libva-drm2”, “libva-X11-2” installed but NO “libva”. I have uninstall “libva-Wayland2”.

    Would appreciate assistance in getting Chromium with VAAPI running. Below are the error output.

    $ chromium-browser –use-gl=desktop
    libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
    [5522:5522:1030/223507.496380:ERROR:vaapi_wrapper.cc(437)] vaInitialize failed (ignore if using Wayland desktop environment): unknown libva error
    [5522:5522:1030/223507.496623:ERROR:vaapi_wrapper.cc(440)] Could not get a valid DRM VA display
    [5522:5522:1030/223507.520427:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
    [5557:5557:1030/223507.577718:ERROR:vaapi_wrapper.cc(423)] Could not get a valid VA display
    Fontconfig error: Cannot load default config file: No such file: (null)

  25. Latest version 86 uploaded for 20.04. Previously I just copied 18.04 rebuilds but Bionic uses old libva version which is now incompatible with some 10-bit video formats and I have to apply workarounds. But there’s actually good news. Thanks to saiarcot895 ppa I figured out how to produce proper builds for 20.04! There were few requests for ARM64. Unfortunately I don’t have such device to test it but at least previous build for 18.04 finished succesfully.

  26. Just to let you know, video acceleration doesn’t work with the latest build (v86).

  27. chrome://gpu/
    Video Decode: Software only. Hardware acceleration disabled

    chrome://flags/
    Hardware-accelerated video decode: Enabled

    • Thanks.
      I guess that info is wrong (not sure why it happens but probably need to use other patch to enable VAAPI by default)
      chrome://media-internals
      actually shows that we’re using HW decoder
      MojoVideoDecoder
      and if you disable “Hardware-accelerated video decode” in chrome://flags/
      you’ll see
      FFmpegVideoDecoder or something else

      • P.S. Found patch “Check for enable-accelerated-video-decode on Linux” at AUR. Description confirms that on v86 chrome://gpu page could be misleading.

  28. Thanks Evgen for the reply but that’s not the case for me. Under ‘chrome://media-internals’ it shows ‘FFmpegVideoDecoder’ with ‘Hardware-accelerated video decode’ in ‘chrome://flags/’ enabled.

    CPU usage is heavy while playing YouTube videos. Is there anything that could be done about it?

    By the way, v87 is out, I hope you’ll do your magic on it too, and soon.

    Thank you once again.

    P.S. I want to express my gratitude to Ji m for letting us communicate here. But there has to be a better way. Is there a place (like GitHub or GitLab) where we can comunicate with you more efficiently?

  29. I have installed v87 and hardware acceleration is working again! Thank you so much Evgen, keep up the excellent work!

  30. In Chromium git repository I’ve seen movement to enable “use_vaapi” build flag by default. Just tried Google Chrome v88 (Unstable/Dev channel). Mojo/VAAPI works there!!! (if you enable flag #enable-accelerated-video-decode and install h264ify extension). That means that 3rd-party PPAs are less relevant now. There are still patches to enable accelerated-mjpeg-decode, workaround for Intel Kabylake+ etc but most users with recent distros should be fine with Google Chrome v88+

  31. Great news Evgen, thank you!

  32. Hi, I follow instruction given but it installed an older version of Chromium 85 instead Chromium 87.

    sudo add-apt-repository ppa:xalt7x/chromium-deb-vaapi
    cat <<EOF | sudo tee /etc/apt/preferences.d/pin-xalt7x-chromium-deb-vaapi
    Package: *
    Pin: release o=LP-PPA-xalt7x-chromium-deb-vaapi
    Pin-Priority: 1337
    EOF
    sudo apt update
    sudo apt install chromium-browser chromium-codecs-ffmpeg-extra

    Chromium installation was successful but the version installed is Chromium 85 instate of Chromium 87 as is listed in the ppa. Any there any other instruction that I missed out?

    • I guess you installed snap version for some reason. What is your Ubuntu version? Currently PPA has packages only for 18.04 and 20.04.

      • I am using Ubuntu 20.04.

        I have added the PPA (sudo add-apt-repository ppa:xalt7x/chromium-deb-vaapi)

        and the installed version is 85.xxx…121 (the snap version if not mistaken is 85.xxx…83) the old version that I have installed before from the PPA.

        • I can only guess possible reasons:
          – apt cache wasn’t updated
          – “apt-mark hold” for some package
          Try this:
          sudo apt purge ^chromium*
          sudo apt install ppa-purge
          sudo ppa-purge ppa:xalt7x/chromium-deb-vaapi
          sudo add-apt-repository ppa:xalt7x/chromium-deb-vaapi
          sudo apt install chromium-browser

          • Thanks for the guidance. Performed the commands as suggested:

            sudo apt purge ^chromium*
            sudo apt install ppa-purge
            sudo ppa-purge ppa:xalt7x/chromium-deb-vaapi
            sudo add-apt-repository ppa:xalt7x/chromium-deb-vaapi
            sudo apt install chromium-browser

            It still install Chromium 85.0.4183.121 Ubuntu 18.04 version and not Chromium 87 for Ubuntu 20.04.

          • Hello Evgen, will there be support of arm64? Because these version are outdated in the repo. Ubuntu 20.04

          • Thanks for updating the Chromium at ARM-64 build. Just updated to new Chromium 87.

            Version 87.0.4280.88 (Official Build) Built on Ubuntu , running on Ubuntu 20.04 (64-bit)

  33. Funny, still install the same Chromium 85.0.4183.121-0ubuntu0.18.04.1~vaapi, (Ubuntu 18.04 and not Ubuntu 20.04) and not Chromium 87. I tried with “sudo apt install chromium-browser” without chromium-codecs-ffmpeg-extra also the same result.

    khadas@Khadas:~$ sudo apt purge ^chromium*
    [sudo] password for khadas:
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Note, selecting ‘chromium-bsu’ for regex ‘^chromium*’
    Note, selecting ‘chromium-driver’ for regex ‘^chromium*’
    Note, selecting ‘chromium-chromedriver’ for regex ‘^chromium*’
    Note, selecting ‘chromium’ for regex ‘^chromium*’
    Note, selecting ‘chromium-bsu-data’ for regex ‘^chromium*’
    Note, selecting ‘chromium-browser’ for regex ‘^chromium*’
    Note, selecting ‘chromium-data’ for regex ‘^chromium*’
    Note, selecting ‘chromium-codecs-ffmpeg-extra’ for regex ‘^chromium*’
    Note, selecting ‘chromium-codecs-ffmpeg’ for regex ‘^chromium*’
    Note, selecting ‘chromium-tt-rss-notifier’ for regex ‘^chromium*’
    Note, selecting ‘chromium-lwn4chrome’ for regex ‘^chromium*’
    Note, selecting ‘chromium-browser-l10n’ for regex ‘^chromium*’
    Note, selecting ‘chromium-ublock-origin’ for regex ‘^chromium*’
    Package ‘chromium’ is not installed, so not removed
    Package ‘chromium-data’ is not installed, so not removed
    Note, selecting ‘chromium-chromedriver’ instead of ‘chromium-driver’
    Package ‘chromium-bsu’ is not installed, so not removed
    Package ‘chromium-bsu-data’ is not installed, so not removed
    Package ‘chromium-lwn4chrome’ is not installed, so not removed
    Package ‘chromium-tt-rss-notifier’ is not installed, so not removed
    Package ‘chromium-ublock-origin’ is not installed, so not removed
    Package ‘chromium-browser’ is not installed, so not removed
    Package ‘chromium-browser-l10n’ is not installed, so not removed
    Package ‘chromium-chromedriver’ is not installed, so not removed
    Package ‘chromium-codecs-ffmpeg’ is not installed, so not removed
    Package ‘chromium-codecs-ffmpeg-extra’ is not installed, so not removed
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    khadas@Khadas:~$ sudo apt install ppa-purge
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following NEW packages will be installed:
    ppa-purge
    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    Need to get 6,312 B of archives.
    After this operation, 24.6 kB of additional disk space will be used.
    Get:1 http://ports.ubuntu.com focal/universe arm64 ppa-purge all 0.2.8+bzr63 [6,312 B]
    Fetched 6,312 B in 1s (6,163 B/s)
    Selecting previously unselected package ppa-purge.
    (Reading database … 126274 files and directories currently installed.)
    Preparing to unpack …/ppa-purge_0.2.8+bzr63_all.deb …
    Unpacking ppa-purge (0.2.8+bzr63) …
    Setting up ppa-purge (0.2.8+bzr63) …
    Processing triggers for man-db (2.9.1-1) …
    khadas@Khadas:~$ sudo add-apt-repository ppa:xalt7x/chromium-deb-vaapi
    ==NOTICE==
    VAAPI should be available on official builds since version 88 (Google Chrome Dev v88.0.4324.27 confirmed to work)
    ==========

    Chromium in deb format with VAAPI support
    * Copied sources from Bionic repository or from “stage for security updates” (https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage)
    * Enabled VAAPI components building in debian/rules and debian/control
    * Enabled VAAPI by default
    * Applied additional Fedora patches
        * enable-hardware-accelerated-mjpeg.patch
        * fix-vaapi-on-intel.patch
        (https://src.fedoraproject.org/rpms/chromium/blob/master/f/chromium.spec)
    * Builds for current LTS (Focal, 20.04) and previous (Bionic, 18.04 (with workaround to disable some 10-bit formats because libva is too old))
    * ARM64 is not tested
    * Currently doesn’t work with Wayland or NVidia hardware

    Other options for Ubuntu: saiarcot895 ppa (needs GOOGLE_API_KEY which can be extracted from sources of this or “staging” ppa), Brave, ungoogled-chromium.

    In order to avoid installation of snap package on Ubuntu 20.04, you can “pin” this PPA with a command bellow:

    cat <<EOF | sudo tee /etc/apt/preferences.d/pin-xalt7x-chromium-deb-vaapi
    Package: *
    Pin: release o=LP-PPA-xalt7x-chromium-deb-vaapi
    Pin-Priority: 1337
    EOF
    More info: https://launchpad.net/~xalt7x/+archive/ubuntu/chromium-deb-vaapi
    Press [ENTER] to continue or Ctrl-c to cancel adding it.

    Get:1 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal InRelease [18.1 kB]
    Hit:2 http://ports.ubuntu.com focal InRelease
    Get:3 http://ports.ubuntu.com focal-security InRelease [109 kB]
    Get:4 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal/main arm64 Packages [1,793 B]
    Get:5 http://ports.ubuntu.com focal-updates InRelease [114 kB]
    Ign:6 https://dl.khadas.com/repos/ focal InRelease
    Get:7 http://ports.ubuntu.com focal-backports InRelease [101 kB]
    Get:8 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal/main armhf Packages [601 B]
    Err:9 https://dl.khadas.com/repos/ focal Release
    404 Not Found [IP: 54.197.197.165 443]
    Get:10 http://ports.ubuntu.com focal-security/universe arm64 Packages [585 kB]
    Get:11 http://ports.ubuntu.com focal-security/universe armhf Packages [455 kB]
    Get:12 http://ports.ubuntu.com focal-security/main arm64 Packages [359 kB]
    Get:13 http://ports.ubuntu.com focal-security/main armhf Packages [340 kB]
    Get:14 http://ports.ubuntu.com focal-updates/universe armhf Packages [681 kB]
    Get:15 http://ports.ubuntu.com focal-updates/universe arm64 Packages [813 kB]
    Get:16 http://ports.ubuntu.com focal-updates/main arm64 Packages [728 kB]
    Get:17 http://ports.ubuntu.com focal-updates/main armhf Packages [706 kB]
    Reading package lists… Done
    E: The repository 'https://dl.khadas.com/repos/ focal Release' does not have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
    khadas@Khadas:~$ cat < Package: *
    > Pin: release o=LP-PPA-xalt7x-chromium-deb-vaapi
    > Pin-Priority: 1337
    > EOF
    Package: *
    Pin: release o=LP-PPA-xalt7x-chromium-deb-vaapi
    Pin-Priority: 1337
    khadas@Khadas:~$ sudo apt update
    Hit:1 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal InRelease
    Hit:2 http://ports.ubuntu.com focal InRelease
    Hit:3 http://ports.ubuntu.com focal-security InRelease
    Hit:4 http://ports.ubuntu.com focal-updates InRelease
    Hit:5 http://ports.ubuntu.com focal-backports InRelease
    Ign:6 https://dl.khadas.com/repos/ focal InRelease
    Err:7 https://dl.khadas.com/repos/ focal Release
    404 Not Found [IP: 54.197.197.165 443]
    Reading package lists… Done
    E: The repository ‘https://dl.khadas.com/repos/ focal Release’ does not have a Release file.
    N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.
    khadas@Khadas:~$ sudo apt install chromium-browser chromium-codecs-ffmpeg-extra
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following additional packages will be installed:
    libfile-basedir-perl libfile-desktopentry-perl libfile-mimeinfo-perl
    libio-stringy-perl libipc-system-simple-perl libx11-protocol-perl xdg-utils
    Suggested packages:
    webaccounts-chromium-extension unity-chromium-extension adobe-flashplugin
    Recommended packages:
    chromium-browser-l10n
    The following NEW packages will be installed:
    chromium-browser chromium-codecs-ffmpeg-extra libfile-basedir-perl
    libfile-desktopentry-perl libfile-mimeinfo-perl libio-stringy-perl
    libipc-system-simple-perl libx11-protocol-perl xdg-utils
    0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
    Need to get 69.9 MB of archives.
    After this operation, 244 MB of additional disk space will be used.
    Do you want to continue? [Y/n] y
    Get:1 http://ports.ubuntu.com focal-security/main arm64 xdg-utils all 1.1.3-2ubuntu1.20.04.1 [61.5 kB]
    Get:2 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal/main arm64 chromium-codecs-ffmpeg-extra arm64 85.0.4183.121-0ubuntu0.18.04.1~vaapi [1,042 kB]
    Get:3 http://ports.ubuntu.com focal/main arm64 libipc-system-simple-perl all 1.26-1 [22.8 kB]
    Get:4 http://ports.ubuntu.com focal/main arm64 libfile-basedir-perl all 0.08-1 [16.9 kB]
    Get:5 http://ports.ubuntu.com focal/main arm64 libfile-desktopentry-perl all 0.22-1 [18.2 kB]
    Get:6 http://ports.ubuntu.com focal/main arm64 libfile-mimeinfo-perl all 0.29-1 [41.5 kB]
    Get:7 http://ports.ubuntu.com focal/main arm64 libio-stringy-perl all 2.111-3 [55.8 kB]
    Get:8 http://ports.ubuntu.com focal/main arm64 libx11-protocol-perl all 0.56-7 [149 kB]
    Get:9 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal/main arm64 chromium-browser arm64 85.0.4183.121-0ubuntu0.18.04.1~vaapi [68.5 MB]
    Fetched 69.9 MB in 10s (6,800 kB/s)
    Selecting previously unselected package xdg-utils.
    (Reading database … 126280 files and directories currently installed.)
    Preparing to unpack …/0-xdg-utils_1.1.3-2ubuntu1.20.04.1_all.deb …
    Unpacking xdg-utils (1.1.3-2ubuntu1.20.04.1) …
    Selecting previously unselected package chromium-codecs-ffmpeg-extra.
    Preparing to unpack …/1-chromium-codecs-ffmpeg-extra_85.0.4183.121-0ubuntu0.18
    .04.1~vaapi_arm64.deb …
    Unpacking chromium-codecs-ffmpeg-extra (85.0.4183.121-0ubuntu0.18.04.1~vaapi) ..
    .
    Selecting previously unselected package chromium-browser.
    Preparing to unpack …/2-chromium-browser_85.0.4183.121-0ubuntu0.18.04.1~vaapi_
    arm64.deb …
    Unpacking chromium-browser (85.0.4183.121-0ubuntu0.18.04.1~vaapi) …
    Selecting previously unselected package libipc-system-simple-perl.
    Preparing to unpack …/3-libipc-system-simple-perl_1.26-1_all.deb …
    Unpacking libipc-system-simple-perl (1.26-1) …
    Selecting previously unselected package libfile-basedir-perl.
    Preparing to unpack …/4-libfile-basedir-perl_0.08-1_all.deb …
    Unpacking libfile-basedir-perl (0.08-1) …
    Selecting previously unselected package libfile-desktopentry-perl.
    Preparing to unpack …/5-libfile-desktopentry-perl_0.22-1_all.deb …
    Unpacking libfile-desktopentry-perl (0.22-1) …
    Selecting previously unselected package libfile-mimeinfo-perl.
    Preparing to unpack …/6-libfile-mimeinfo-perl_0.29-1_all.deb …
    Unpacking libfile-mimeinfo-perl (0.29-1) …
    Selecting previously unselected package libio-stringy-perl.
    Preparing to unpack …/7-libio-stringy-perl_2.111-3_all.deb …
    Unpacking libio-stringy-perl (2.111-3) …
    Selecting previously unselected package libx11-protocol-perl.
    Preparing to unpack …/8-libx11-protocol-perl_0.56-7_all.deb …
    Unpacking libx11-protocol-perl (0.56-7) …
    Setting up chromium-codecs-ffmpeg-extra (85.0.4183.121-0ubuntu0.18.04.1~vaapi) .
    ..
    Setting up libio-stringy-perl (2.111-3) …
    Setting up libipc-system-simple-perl (1.26-1) …
    Setting up xdg-utils (1.1.3-2ubuntu1.20.04.1) …
    Setting up libx11-protocol-perl (0.56-7) …
    Setting up libfile-basedir-perl (0.08-1) …
    Setting up libfile-desktopentry-perl (0.22-1) …
    Setting up chromium-browser (85.0.4183.121-0ubuntu0.18.04.1~vaapi) …
    Setting up libfile-mimeinfo-perl (0.29-1) …
    Processing triggers for mime-support (3.64ubuntu1) …
    Processing triggers for hicolor-icon-theme (0.17-2) …
    Processing triggers for gnome-menus (3.36.0-1ubuntu1) …
    Processing triggers for man-db (2.9.1-1) …
    Processing triggers for desktop-file-utils (0.24-1ubuntu3) …

  34. I’ve just updated Chromium to the latest version (87.0.4280.88) and everything works fine. Thank you very much!

  35. Hi, Evgen, will you update the arm64 version of Chromium? Because it’s outdated for arm. Ubuntu 20.04

  36. Hi,

    An innocent question. Does the above PPA and commands install Chromium 87 on Debian Buster?

    • sudo apt-get install chromium-browser=87.0.4280.88-0ubuntu0.20.04.1.1~vaapi chromium-browser-l10n=87.0.4280.88-0ubuntu0.20.04.1.1~vaapi codecs-ffmpeg-extra=87.0.4280.88-0ubuntu0.20.04.1.1~vaapi

  37. Evgen released a brief statement…

    ==NOTICE==
    This PPA was abandoned at the end of 2020 and probably won’t be updated anymore.
    Recommended alternatives: Google Chrome or Mozilla Firefox