Bug#772471: closed by Michael Gilbert mgilb...@debian.org (Re: Bug#772471: chromium crash on startup)
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.] thanks, --jack - Original Message - From: Debian Bug Tracking System ow...@bugs.debian.org To: js jsh...@yahoo.com Cc: Sent: Friday, December 19, 2014 7:45 PM Subject: Bug#772471 closed by Michael Gilbert mgilb...@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 mgilb...@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 mgilb...@debian.org by replying to this email. -- 772471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772471 Debian Bug Tracking System Contact ow...@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, Mike 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=439795thanks=439795ts=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: ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772471: chromium crash on startup
The full cause of this chromium crash on 32 bit linux (while the corresponding google-chrome-stable version worked fine) was found as issue 439795 on https://code.google.com/p/chromium/ 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. The full details are in the link below and comment 50 (below) summarizes the issue. thanks, --jack https://code.google.com/p/chromium/issues/detail?can=2start=0#=100q=colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modifiedgroupby=sort=id=439795 #50 ric...@chromium.org Hm, I'm not sure why chromium 39.0.2171.71 would include the new syscall check. From what what I can tell, that version does not have the check for the seccomp syscall: https://chromium.googlesource.com/chromium/src.git/+/39.0.2171.71/sandbox/linux/seccomp-bpf/sandbox_bpf.cc Compare that to https://chromium.googlesource.com/chromium/src.git/+/master/sandbox/linux/seccomp-bpf/sandbox_bpf.cc, which has the KernelSupportsSeccompTsync function. You'd probably need to check with whoever built the package you're using to figure out how it managed to include that code. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772471: chromium crash on startup with error: FATAL:sandbox_bpf.cc(502)] Check failed: -1 == rv (-1 vs. 354)
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=439795thanks=439795ts=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 libc62.19-13 ii libcairo21.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 libexpat12.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-keyring03.12.0-1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b0.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 libspeex11.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-utils7.7+2 ii xdg-utils1.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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772471: chromium crash on startup
control: tag -1 moreinfo control: severity -1 minor control: retitle -1 chromium: sandbox issue with nvidia driver Kernel: Linux 3.14-1-686-pae (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Shell: /bin/sh linked to /bin/dash Not sure if it matters, but your kernel is quite out of date. jessie currently has 3.16.0-4, so you could try updating. Also, since this was with the proprietary driver please try nouveau instead. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772471: chromium crash on startup
Thanks for the quick reply. As you saw, I've also submitted this issue to http://code.google.com/p/chromium/issues/detail?id=439795thanks=439795ts=1417965276 I need the hardware acceleration that is provided by the nvidia driver so couldn't lose that just to use a new version of chromium. At some point I'll upgrade the kernel but this is a significant issue when using the nvidia driver;if this problem continues until then and is solved by the kernel upgrade, I'll update the bug. I think there are two issues to consider: 1. this problem did not arise with chromium 38.0.2125.101-2, to which I have now reverted 2. this problem does not arise with google-chrome-stable 39.0.2171.71-1, the same version as the chromium in this bug report. These two issues indicate that related software works with the nvidia driver and kernel 3.14,so more likely is caused by changes that are specific to just this new version of chromium. thanks,--jack From: Michael Gilbert mgilb...@debian.org To: 772...@bugs.debian.org; 772471-submit...@bugs.debian.org Sent: Sunday, December 7, 2014 6:14 PM Subject: Bug#772471: chromium crash on startup control: tag -1 moreinfo control: severity -1 minor control: retitle -1 chromium: sandbox issue with nvidia driver Kernel: Linux 3.14-1-686-pae (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Shell: /bin/sh linked to /bin/dash Not sure if it matters, but your kernel is quite out of date. jessie currently has 3.16.0-4, so you could try updating. Also, since this was with the proprietary driver please try nouveau instead. Best wishes, Mike
Bug#772471: chromium crash on startup
Thanks for the quick reply. As you saw, I've also submitted this issue to http://code.google.com/p/chromium/issues/detail?id=439795thanks=439795ts=1417965276 I need the hardware acceleration that is provided by the nvidia driver so couldn't lose that just to use a new version of chromium. At some point I'll upgrade the kernel but this is a significant issue when using the nvidia driver; if this problem continues until then and is solved by the kernel upgrade, I'll update the bug. I think there are two issues to consider: 1. this problem did not arise with chromium 38.0.2125.101-2, to which I have now reverted 2. this problem does not arise with google-chrome-stable 39.0.2171.71-1, the same version as the chromium in this bug report. These two issues indicate that related software works with the nvidia driver and kernel 3.14, so more likely is caused by changes that are specific to just this new version of chromium. thanks, --jack From: Michael Gilbert mgilb...@debian.org To: 772...@bugs.debian.org; 772471-submit...@bugs.debian.org Sent: Sunday, December 7, 2014 6:14 PM Subject: Bug#772471: chromium crash on startup control: tag -1 moreinfo control: severity -1 minor control: retitle -1 chromium: sandbox issue with nvidia driver Kernel: Linux 3.14-1-686-pae (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Shell: /bin/sh linked to /bin/dash Not sure if it matters, but your kernel is quite out of date. jessie currently has 3.16.0-4, so you could try updating. Also, since this was with the proprietary driver please try nouveau instead. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
