This bug was fixed in the package chromium-browser - 79.0.3945.130-0ubuntu0.16.04.1
--------------- chromium-browser (79.0.3945.130-0ubuntu0.16.04.1) xenial; urgency=medium * Upstream release: 79.0.3945.130 - CVE-2020-6378: Use-after-free in speech recognizer. - CVE-2020-6379: Use-after-free in speech recognizer. - CVE-2020-6380: Extension message verification error. * debian/control: remove libgnome-keyring-dev build dependency (LP: #1828192) * debian/rules: build with use_gnome_keyring=false * debian/known_gn_gen_args-*: change use_gnome_keyring build flag to false -- Olivier Tilloy <olivier.til...@canonical.com> Mon, 27 Jan 2020 17:44:47 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1828192 Title: Please stop build-depending on libgnome-keyring Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Xenial: Fix Released Status in chromium-browser source package in Bionic: Fix Released Status in chromium-browser source package in Disco: In Progress Bug description: libgnome-keyring is not maintained anymore, but chromium build-depends on it. It should be using libsecret instead. The generated binaries depend on neither library, which is a bit confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1828192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp