It is happening (suddenly) in OpenVZ for me, too, after having updated the OpenVZ kernel (linux-image-openvz-amd64 2.6.32+28 from Debian testing) and chromium-browser itself (chromium-browser 6.0.472.36~r55963-0ubuntu1~ucd1~hardy).
The workaround appears to be using "--no-sandbox". Unfortunately this adds a warning/note during startup and is therefore not a good solution for my use case (browsershots.org instances). ** Bug watch added: code.google.com/p/chromium/issues #31077 http://code.google.com/p/chromium/issues/detail?id=31077 ** Also affects: chromium-browser via http://code.google.com/p/chromium/issues/detail?id=31077 Importance: Unknown Status: Unknown -- 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 Registry Administrators, which is the registrant for OpenVZ kernel. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
