Your message dated Fri, 19 Dec 2014 19:40:47 -0500 with message-id <CANTw=mnk8p9kxdmfxcbyrkcfrppmc-0xeegtrw88cm58ak-...@mail.gmail.com> and subject line Re: Bug#772471: chromium crash on startup has caused the Debian Bug report #772471, regarding chromium: sandbox issue with nvidia driver to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 772471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772471 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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: http://code.google.com/p/chromium/issues/detail?id=439795&thanks=439795&ts=1417965276 ========================================================================= -- 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: ii libasound2 1.0.28-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libcap2 1:2.24-6 ii libcups2 1.7.5-5 ii libdbus-1-3 1.8.12-1 ii libexpat1 2.1.0-6 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.9.1-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-1 ii libgnome-keyring0 3.12.0-1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b 0.9.35-1 ii libjpeg62-turbo 1:1.3.1-10 ii libnspr4 2:4.10.7-1 ii libnspr4-0d 2:4.10.7-1 ii libnss3 2:3.17.2-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpci3 1:3.2.1-1 ii libspeechd2 0.8-5 ii libspeex1 1.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1 ii libstdc++6 4.9.1-1 ii libudev1 204-6 ii libx11-6 2:1.6.2-1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-1 ii libxi6 2:1.7.4-1 ii libxml2 2.9.1+dfsg1-3 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxslt1.1 1.1.28-2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1 ii x11-utils 7.7+2 ii xdg-utils 1.1.0~rc1+git20111210-7.1 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-inspector 39.0.2171.71-2 ii chromium-l10n 39.0.2171.71-2 -- Configuration Files: /etc/chromium.d/README changed: -- no debconf information
--- End Message ---
--- Begin Message ---On 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, Mike
--- End Message ---
