Please disable gconf in chromium-browser

Bug #1669100 reported by Jeremy Bicha on 2017-03-01
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Olivier Tilloy

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.

Chad Miller (cmiller) on 2017-03-02
Changed in chromium-browser (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Chad Miller (cmiller)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package chromium-browser - 58.0.3029.81-0ubuntu0.14.04.1172

chromium-browser (58.0.3029.81-0ubuntu0.14.04.1172) trusty; urgency=medium

  * Upstream release: 58.0.3029.81
    - CVE-2017-5057: Type confusion in PDFium.
    - CVE-2017-5058: Heap use after free in Print Preview.
    - CVE-2017-5059: Type confusion in Blink.
    - CVE-2017-5060: URL spoofing in Omnibox.
    - CVE-2017-5061: URL spoofing in Omnibox.
    - CVE-2017-5062: Use after free in Chrome Apps.
    - CVE-2017-5063: Heap overflow in Skia.
    - CVE-2017-5064: Use after free in Blink.
    - CVE-2017-5065: Incorrect UI in Blink.
    - CVE-2017-5066: Incorrect signature handing in Networking.
    - CVE-2017-5067: URL spoofing in Omnibox.
    - CVE-2017-5069: Cross-origin bypass in Blink.
  * debian/patches/arm.patch: removed, no longer needed
  * debian/patches/gtk-ui-stdmove: removed, no longer needed (upstreamed)
  * debian/patches/screen_capturer: removed, no longer needed (upstreamed)
  * debian/patches/default-allocator: refreshed
  * debian/patches/disable-sse2: refreshed
  * debian/patches/enable-chromecast-by-default: refreshed
  * debian/patches/fix_building_widevinecdm_with_chromium.patch: refreshed
  * debian/patches/search-credit.patch: refreshed
  * debian/patches/snapshot-library-link: refreshed
  * debian/patches/title-bar-default-system.patch-v35: refreshed
  * debian/patches/fix-gn-bootstrap.patch: added
  * debian/rules: disable the use of Vulcanize, the required node.js modules
    are not readily available

 -- Olivier Tilloy <email address hidden> Mon, 24 Apr 2017 11:56:01 +0200

Changed in chromium-browser (Ubuntu):
status: Confirmed → Fix Released
Jeremy Bicha (jbicha) wrote :

chromium-browser still depends on libgconf-2-4. I think you should drop the Build-Depends: libgconf2-dev and set use_gconf=false in debian/rules. Also, the apport script shouldn't try to use gconf either.

Changed in chromium-browser (Ubuntu):
status: Fix Released → Confirmed
assignee: Chad Miller (cmiller) → nobody
Olivier Tilloy (osomon) on 2017-04-26
Changed in chromium-browser (Ubuntu):
assignee: nobody → Olivier Tilloy (osomon)
importance: Low → Medium
Olivier Tilloy (osomon) on 2017-04-27
Changed in chromium-browser (Ubuntu):
status: Confirmed → In Progress
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 21 Jun 2017 06:37:28 +0200

Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers