Hi,
commit 64b895bf23943f8c72a49216d24e36b128213167
Author: Giuseppe Iuculano iucul...@debian.org
Date: Mon Oct 21 13:05:14 2013 +0200
Move chrome_sandbox to chrome-sandbox, chromium reads that file
Your -2 uploads didn't contain my -1 changes. Michael, please, please,
update your
Your -2 uploads didn't contain my -1 changes. Michael, please, please,
update your local git copy *before* any future uploads.
My clone was actually up to date, but I had local changes to the
sandbox path that I forgot to remove before building.
Anyway it was a mistake on my part. Apologies.
For me the solution pointed by Wolfgang Walter solves the issue:
ln -s /usr/lib/chromium/chromium-sandbox /usr/lib/chromium/chrome-sandbox
--
Sergio Fernández ser...@wikier.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Package: chromium-browser
Version: chromium
Followup-For: Bug #728823
Dear Maintainer,
Some extra info for you:
This bug appeared in a running version of chromium during my last upgrade.
Upgrade log is below.
2013-11-06 20:08:00 startup archives unpack
2013-11-06 20:08:00 upgrade
Package: chromium
Version: 30.0.1599.101-2
Severity: grave
File: /usr/bin/chromium
After the latest upgrade, trying to start chromium results in
$ chromium
[19832:19832:1105/225629:FATAL:browser_main_loop.cc(160)] Running
without the SUID sandbox! See
same problem here. A workaround is to make a symlink
ln -s chromium-sandbox /usr/lib/chromium/chrome-sandbox
--
Wolfgang Walter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
6 matches
Mail list logo