"Doctor, it hurts when I do this!"abushcrafter wrote:It works without the sandbox.DMcCunney wrote:What happens if you don't have the sandbox enabled?abushcrafter wrote:I get these errors with the sandbox enabled:
"So don't do that!"
Don't use the sandbox.
I think the "Cannot chdir to / after chroot: Stale NFS file handle " is the problem, and the rest stems from that. As mentioned, the sandbox is Windows specific. I wouldn't expect it to work under Linux. I'm not particularly concerned about vulnerabilities because I am using Linux, and the majority of the bad stuff the sandbox is intended to ward against targets Windows and won't work on Linux.My flash drive and pupsave are ok. With the sandbox enabled here are the errors after trying it again:Code: Select all
# ./google-chrome ./google-chrome: /lib/libz.so.1: no version information available (required by ./google-chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome) Cannot chdir to / after chroot: Stale NFS file handle [25045:25045:1368716958:ERROR:/usr/local/google/b/slave/chrome-official-linux/build/src/chrome/browser/zygote_main_linux.cc(528)] Failed to read from chroot pipe: 0 [25045:25045:1368717157:FATAL:/usr/local/google/b/slave/chrome-official-linux/build/src/chrome/browser/zygote_main_linux.cc(621)] Failed to enter sandbox. Fail safe abort. (errno: 0) <I killed it here as it does not do any thing. Waited around 10mins to see if it did any thing but it did not do any thing.> #
______
Dennis