Your message dated Thu, 21 Jun 2012 08:00:14 +0200
with message-id <1340258414.10349.10.camel@scapa>
and subject line Re: chromium: seccomp sandbox broken
has caused the Debian Bug report #677892,
regarding chromium: seccomp sandbox broken
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.)
--
677892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677892
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 20.0.1132.27~r140692-2
Severity: normal
Hi,
it seems that running with --enable-seccomp-sandbox breaks current
chromium:
chromium --enable-seccomp-sandbox
[29215:29215:267349211749:FATAL:zygote_host_impl_linux.cc(206)] Check failed:
pid_ > 0. Did not find zygote process (using sandbox binary
/usr/lib/chromium/chromium-sandbox)
[1] 29215 abort chromium --enable-seccomp-sandbox
Unfortunately, I can't report it upstream because it wants me to login
to Google.
Regards,
--
Yves-Alexis
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 20.0.1132.27~r140692-2
ii gconf-service 3.2.5-1
ii libasound2 1.0.25-3
ii libatk1.0-0 2.4.0-2
ii libbz2-1.0 1.0.6-3
ii libc6 2.13-33
ii libcairo2 1.12.2-2
ii libcups2 1.5.3-1
ii libdbus-1-3 1.6.0-1
ii libevent-2.0-5 2.0.19-stable-3
ii libexpat1 2.1.0-1
ii libflac8 1.2.1-6
ii libfontconfig1 2.9.0-6
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.1-1
ii libgconf-2-4 3.2.5-1
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.10-1
ii libjpeg8 8d-1
ii libnspr4 2:4.9.1-1
ii libnss3 2:3.13.5-1
ii libnss3-1d 2:3.13.5-1
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1
ii libpulse0 2.0-3
ii libspeex1 1.2~rc1-6
ii libstdc++6 4.7.1-1
ii libudev0 175-3.1
ii libwebp2 0.1.3-3
ii libx11-6 2:1.5.0-1
ii libxcomposite1 1:0.4.3-2
ii libxext6 2:1.3.1-2
ii libxfixes3 1:5.0-4
ii libxml2 2.8.0+dfsg1-4
ii libxrender1 1:0.9.7-1
ii libxslt1.1 1.1.26-12+rebuild1
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-6
ii zlib1g 1:1.2.7.dfsg-11
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- Configuration Files:
/etc/chromium/default changed:
CHROMIUM_FLAGS="--password-store=detect"
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20.0.1132.34~r141824-1
On dim., 2012-06-17 at 09:46 -0500, Jonathan Nieder wrote:
> Yves-Alexis Perez wrote:
>
> > it seems that running with --enable-seccomp-sandbox breaks current
> > chromium:
> >
> > chromium --enable-seccomp-sandbox
> > [29215:29215:267349211749:FATAL:zygote_host_impl_linux.cc(206)] Check
> > failed: pid_ > 0. Did not find zygote process (using sandbox binary
> > /usr/lib/chromium/chromium-sandbox)
> > [1] 29215 abort chromium --enable-seccomp-sandbox
>
> Gah. Thanks.
>
> > Unfortunately, I can't report it upstream because it wants me to login
> > to Google.
>
> The easiest way to reach real people is probably #chromium on freenode.
>
Seems fixed with 20.0.1132.34~r141824-1.
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
--- End Message ---
