Bugzilla – Bug 965308
chromium doesn't start after kernel update, Check failed: NamespaceUtils::WriteToIdMapFile("/proc/self/gid_map", gid_)
Last modified: 2016-02-22 11:12:13 UTC
chromium (same for google-chrome) doesn't start after applying the latest maintenance kernel-desktop-3.16.7-32.1.x86_64. Error message (from a console): Check failed: NamespaceUtils::WriteToIdMapFile("/proc/self/gid_map", gid_) Found some pointers that suspect a "incomplete backport of the fix for CVE-2014-8989", see https://code.google.com/p/chromium/issues/detail?id=480017
just to add to Robert's original report: Also get this error, can launch Chromium (version 48.0.2564.82-67.1-x86_64) successfully when booted using previous kernel (3.16.7-29-desktop).
duypo of 965356 (likely related to userns security fixes) *** This bug has been marked as a duplicate of bug 965356 ***
openSUSE-SU-2016:0537-1: An update that solves two vulnerabilities and has three fixes is now available. Category: security (important) Bug References: 907378,961500,963767,965308,965356 CVE References: CVE-2016-0723,CVE-2016-2069 Sources used: openSUSE 13.2 (src): bbswitch-0.8-3.17.1, cloop-2.639-14.17.1, crash-7.0.8-17.1, hdjmod-1.28-18.18.1, ipset-6.23-17.1, kernel-debug-3.16.7-35.1, kernel-default-3.16.7-35.1, kernel-desktop-3.16.7-35.1, kernel-docs-3.16.7-35.2, kernel-ec2-3.16.7-35.1, kernel-obs-build-3.16.7-35.2, kernel-obs-qa-3.16.7-35.1, kernel-obs-qa-xen-3.16.7-35.1, kernel-pae-3.16.7-35.1, kernel-source-3.16.7-35.1, kernel-syms-3.16.7-35.1, kernel-vanilla-3.16.7-35.1, kernel-xen-3.16.7-35.1, pcfclock-0.44-260.17.1, vhba-kmp-20140629-2.17.1, virtualbox-4.3.36-43.2, xen-4.4.3_08-40.1, xtables-addons-2.6-17.1