We have an upstream bug about this here: http://code.google.com/p/chromium/issues/detail?id=62248
Note that removing the sandbox makes Chromium on a guest account *less secure* than Chromium in a normal account. A sandboxed Chromium does all of the page processing (HTML interpretation, running JavaScript) in a process that doesn't have access to the network or disk; by contrast, an apparmor-wrapper Chromium without a sandbox runs all of that at the same privilege as a normal app. ** Bug watch added: code.google.com/p/chromium/issues #62248 http://code.google.com/p/chromium/issues/detail?id=62248 -- chromium-browser fails to start (guest account, OpenVZ): "Failed to move to new PID namespace: Operation not permitted" https://bugs.launchpad.net/bugs/577919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
