This bug was fixed in the package chromium-browser -
59.0.3071.109-0ubuntu0.17.04.1360
---------------
chromium-browser (59.0.3071.109-0ubuntu0.17.04.1360) zesty; urgency=medium
* Upstream release: 59.0.3071.109
-- Olivier Tilloy <olivier.til...@canonical.com> Wed, 21 Jun 2017
06:37:28 +0200
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
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/1669100
Title:
Please disable gconf in chromium-browser
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
gconf has been deprecated for years and I'd like to remove it from my
computer. (It's not used by Unity or unity-settings-daemon or core
GNOME at all.)
Ubuntu's debian/rules has use_gconf=true but Debian has
use_gconf=false. Please follow Debian here.
I see that the apport script also tries to use gconf so that should be
dropped too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1669100/+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
