[Pkg-chromium-maint] Bug#772471: closed by Michael Gilbert <mgilbert at debian.org> (Re: Bug#772471: chromium crash on startup)

JS jshaio at yahoo.com
Sat Dec 20 15:20:07 UTC 2014

I would say that there is still a problem with debian packaging in that it allows this chromium version

to be installed in a kernel earlier than 2.16, although the result is of no value since the new chromium

will not work.

Perhaps for versions 39.0.2171 and higher of chromium, the debian package should also require a

kernel version at least 3.16. This would be a rigorous way of implementing the requirement that

people running into this problem should upgrade their kernel.

[ I was able to avoid this issue by patching the debian source to avoid this check, as it currently

does in chromium.org for this version, and rebuilding on my 32 bit linux with the additional flags:

defines+= remove_webcore_debug_symbols=1 \
              component=shared_library \

although at some later point will have to upgrade my kernel to 3.16.]


----- Original Message -----
From: Debian Bug Tracking System <owner at bugs.debian.org>
To: js <jshaio at yahoo.com>
Sent: Friday, December 19, 2014 7:45 PM
Subject: Bug#772471 closed by Michael Gilbert <mgilbert at debian.org> (Re: Bug#772471: chromium crash on startup)

This is an automatic notification regarding your Bug report
which was filed against the chromium package:

#772471: chromium: sandbox issue with nvidia driver

It has been closed by Michael Gilbert <mgilbert at debian.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Michael Gilbert <mgilbert at debian.org> by
replying to this email.

772471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772471
Debian Bug Tracking System
Contact owner at bugs.debian.org with problemsOn Thu, Dec 18, 2014 at 8:35 AM, JS wrote:
> It was caused by including a check for error codes for non-existent system calls that is not in chromium; see below. This issue is in the debian 3.14 kernel and has been fixed in the 3.16 kernel.

Thanks a bunch for digging into this!

So the moral of the story is that chromium won't work on kernels
patched for CVE-2014-4508 and don't include a particular regression
bugfix.  The debian 3.16 and newer kernels are known to include that
bugfix, so users running into this problem should start there.

Best wishes,
Package: chromium
Version: 39.0.2171.71-2
Severity: important

Dear Maintainer,

After upgrade to chromium:i386 39.0.2171.71-2 from chromium:i386 38.0.2125.101-1,
chromium now crashes every time on startup with the error:
     FATAL:sandbox_bpf.cc(502)] Check failed: -1 == rv (-1 vs. 354)

Note that google-chrome-stable 39.0.2171.71-1  works correctly on the same computer.

I am also using the proprietary nvidia driver 340.46-1, which has been mentioned in
some chromium threads (see references in code.google.com bug report below), although
the 38.0.2125.101 chromium worked fine with this nvidia driver.

submitted chromium bug report:


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-686-pae (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chromium depends on:

More information about the Pkg-chromium-maint mailing list