Native Client not running

Pierre Chicoine

unread,

Feb 18, 2011, 10:04:39 PM2/18/11

to native client

Dear Sirs

I can't get any nexe programs to run. I've upgraded to version 11.X of chrome as the 10.x had the same problem. I am on Linux Kubuntu 10.04.

I am, though, getting a strange error:

You are using an unsupported command-line flag: --enable-nacl. Stability and security will suffer.

I am not starting from a shell script and I try starting chrome directly from the /opt/google/chrome directory so I can't understand where I might be getting this error as I have tried starting with no options on the command line and still get this error.

The web server shows starting by using 'python httpd.py 5103' and it gives back the message: Starting local server on port 5103

I am using the latest SDK download for Pepper 2 which I have in folder: /home/pierre/native_client_sdk_0_1_721_0

I also tried --no-sandbox at the startup of chrome from a command line. I'm basically out of options.

Thanks in advance

David Michael

unread,

Feb 18, 2011, 10:30:39 PM2/18/11

to native-cli...@googlegroups.com, Pierre Chicoine

Hi Pierre, thanks for trying out NaCl!

You currently need to run with the --no-sandbox flag on Linux. Make sure you completely restart the browser, and make sure the version is correct by checking 'about:version'. (It sounds like you've done that, but I want to double-check). See below for some more suggestions:

On Sat, Feb 19, 2011 at 3:04 AM, Pierre Chicoine <pierre_...@yahoo.com> wrote:

Dear Sirs

I can't get any nexe programs to run. I've upgraded to version 11.X of chrome as the 10.x had the same problem. I am on Linux Kubuntu 10.04.

I am, though, getting a strange error:

You are using an unsupported command-line flag: --enable-nacl. Stability and security will suffer.

This is just a warning that appears because you turned on NaCl. We show a warning because it is a new feature with security implications. We'll almost certainly be removing the warning in the next release; you can safely ignore it.

I am not starting from a shell script and I try starting chrome directly from the /opt/google/chrome directory so I can't understand where I might be getting this error as I have tried starting with no options on the command line and still get this error.

The web server shows starting by using 'python httpd.py 5103' and it gives back the message: Starting local server on port 5103

That sounds right. Remember to use 'localhost:5103' for your URL (file:// URLs will not work). You can also check your version of Chrome against the example gallery:

http://code.google.com/chrome/nativeclient/docs/examples.html

I am using the latest SDK download for Pepper 2 which I have in folder: /home/pierre/native_client_sdk_0_1_721_0

This also sounds right.

I also tried --no-sandbox at the startup of chrome from a command line. I'm basically out of options.

Yes, that is currently necessary (but will be fixed in the next release).

Thanks in advance

No problem, I hope that helps.

-Dave M.

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To post to this group, send email to native-cli...@googlegroups.com.
To unsubscribe from this group, send email to native-client-di...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/native-client-discuss?hl=en.

Pierre Chicoine

unread,

Feb 18, 2011, 11:08:06 PM2/18/11

to native-cli...@googlegroups.com

David

Thanks for such a quick reply. I have started the browser several times and tried --no-sandbox with no luck. It looks like I've done everything right. There must be something I'm missing or maybe it's just the shock of the Nokia-Microsoft deal as I am a Qt developer.

My work of 16 years depends on this working, so I will do everything in my power to get it working.

Thanks again.

Pierre Chicoine

11.0.672.2 (Official Build 75134) dev

--- On Fri, 2/18/11, David Michael <dmic...@google.com> wrote:

David Michael

unread,

Feb 18, 2011, 11:21:04 PM2/18/11

to native-cli...@googlegroups.com, Pierre Chicoine

Hi Pierre,

Did you try the gallery?

http://code.google.com/chrome/nativeclient/docs/examples.html

If that doesn't work, it means something's going wrong in the Chrome side. If it does work, then the problem may be in the SDK or the SDK examples. In either case, you can turn on some debug output and restart Chrome by exporting some environment variables:

export PPAPI_BROWSER_DEBUG=1  # Turn on useful PPAPI plugin debugging logs.

export NACL_PLUGIN_DEBUG=1  # Turn on useful NaCl SRPC debugging logs.

export NACL_PPAPI_PROXY_DEBUG=1  # Turn on PPAPI-specific logging.

If you're still having trouble, please turn these on and send us your console output so we can try to diagnose the problem.