Unable to reproduce this issue on Windows 7,Mac 10.11.4, Linux Ubuntu 14.04 with Chrome  stable -54.0.2840.59 and latest Canary-56.0.2889.0.

Please find the attached screencast for reference & let us know if anything required to reproduce the issue.

Deleted: 655746-Linux 1.5 MB

655746-Linux 1.5 MB View Download

Jamie, our team was unable to reproduce this bug, do you have someone to take a look?

Encountered multiple reports for current stable release - 54.0.2840.59 

Can you send us the client logs? To find them:

* With the app running, visit chrome://extensions
* Ensure that the "Developer Mode" checkbox at the top right of the page is checked.
* Scroll down to the Chrome Remote Desktop extension.
* Click the main.html link
* Select the Console tab.

Just copy/paste the logs from an unsuccessful connection into this bug.

Hey team, 

An Enterprise customer provided logs while running CRD from the terminal:

Chrome version: Chrome 54.0.2840.59, 53.0.2785.144 
OS Version: Arch Linux, Ubuntu, Chromium Arch 

[2747:2747:1011/215419:ERROR:display_info_provider_aura.cc(31)] Not 
implemented reached in virtual void 
extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const 
display::Display &, extensions::api::system_display::DisplayUnitInfo *) 
[2747:2826:1011/215437:ERROR:native_process_launcher.cc(137)] Can't find 
manifest for native messaging host com.google.chrome.remote_desktop 
[2747:2769:1011/215438:ERROR:native_process_launcher.cc(137)] Can't find 
manifest for native messaging host com.google.chrome.remote_desktop 
[2747:2769:1011/215438:ERROR:native_process_launcher.cc(137)] Can't find 
manifest for native messaging host com.google.chrome.remote_desktop 
[3,2706066304 <(270)%20606-6304>:04:54:38.462677] Native Client module will 
be loaded at base address 0x000017be00000000 
[3,2706066304 <(270)%20606-6304>:04:54:38.466335] NaClHostDescMap: mprotect 
to turn on PROT_EXEC failed, errno 13 
POST-ABORT: LOG_FATAL abort exit 

** Signal 6 from trusted code: pc=7fcea019e04f 
[2747:2775:1011/215438:ERROR:nacl_process_host.cc(337)] NaCl process exited 
with status 64000 (0xfa00) 
[5,2706066304 <(270)%20606-6304>:04:54:48.915573] Native Client module will 
be loaded at base address 0x000076ba00000000 
[5,2706066304 <(270)%20606-6304>:04:54:48.917825] NaClHostDescMap: mprotect 
to turn on PROT_EXEC failed, errno 13 
POST-ABORT: LOG_FATAL abort exit 

Additional notes: 
Both client and host user account are the same. 
CRD will work using a Windows 7 computer as a client. Using CRD with a Windows 7 device as the host and a Linux machine as the client means being unable to connect. Issue seems to be isolated to the native client for Linux. 
Likewise connecting from an Android device works. 
Multiple networks checked including the one the Windows 7 machine used to act as client. Networking does not seem to be the problem. 
Opening Chrome with no sandboxing failed to resolve the issue.

As per the log, below is the only latest CL from native_process_launcher.cc which could have impacted this issue, but not sure though.

https://codereview.chromium.org/1573843002

I am looping to the CL owner an well as- //src/chrome/browser/extensions/api/messaging/OWNERS for further inputs.

+sergeyu for nativeMessaging.

Is this an official Chrome build (as opposed to an open-source Chromium build)? I see "Chromium Arch" in the logs, which makes me wonder.

It was chrome 53/54, not chromium. I did install chromium from the official arch repo and had the same issue, but that was a while ago (53). I can try again and report back. 

Can you try installing the PNaCl examples app from https://chrome.google.com/webstore/detail/pnacl-examples/mblemkccghnfkjignlmgngmopopifacf/related and let us know if you encounter the same problem? If not, try removing and reinstalling the Chrome Remote Desktop app

I've added/removed the app about a dozen times. Including removing the profile and clearing the profile completely multiple times. I'll try the pnacl examples app in a little bit. 

To be clear, CRD behaves slightly differently for me than in the bug.

CRD opens and loads fine when I open the app. However, When I click on the computer I want to remote to (I've tried multiple hosts across a variety of operating systems, the result is the same, the Windows and Android clients work fine -- the issue is linux client side), it says "Connecting" and the spinner spins one or two times. At which point, it hangs. Indeed, all of Chrome more or less hangs and becomes nearly unresponsive. The "X" does not respond and allow closing. After a few minutes, the window says "A required component is missing"

The PNaCl extension is essentially non-functional. I believe clicking around it crashed one session. When I click on the sine wave generator (for example) neither play nor stop do anything, and the buttons do not even appear to depress. If I try to then click to a different example, the extension does not respond. All of Chrome is running slowly, much as it does with CRD. Just clicking between the different examples causes Chrome to hang for a second. It also occasionally says that the file cannot be found.

Sorry for all the comments, I cannot seem to edit previous comments.

Within each such example, it appears to be stuck with "Status: Creating embed: pnacl"

I called it from bash, and got the following throughout

[3328:3359:1026/153404:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153404:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153404:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153404:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153408:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153409:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3328:1026/153409:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *)
[360:360:1026/153410:ERROR:PlatformKeyboardEvent.cpp(93)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState()
[3328:3359:1026/153430:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/153502:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153610:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153613:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153613:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/153730:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154240:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154334:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/154336:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/154337:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/154340:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154448:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154504:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/154513:ERROR:ssl_client_socket_impl.cc(1168)] handshake failed; returned -1, SSL error code 1, net_error -117
[3328:3359:1026/154549:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154649:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154805:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/154906:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/155006:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/155111:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/155218:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)
[3328:3359:1026/155319:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 9 (0x9)

It's interesting that you're not getting the same level of error output as you got with Chromoting (in comment 5), but it looks like the problem is that NaCl is broken for you. I've updated the tags to bring it to the attention of the relevant team.

I got those, too when I tried CRD 

Is there anything else I can do/any other info you need?

Jim, who would be the best person to address this?  Could you maybe assign?

Copying +bradnelson who is likely the best person to track down NaCl issues.

Has there been any progress?

Thanks

Hi team,

Can we have an update in this report?

Thank you!

Derek's been looking into this yesterday or so.

For the record, this looks unrelated to what I've been looking at the last couple of days. But I'll see what I can find out. Just to clarify, this bug  appears to have 2 (maybe 3) separate reports on it, and from the logs it looks like they may not be the same problems. scott@, can you let me know what distro and version you are using? (also, are you the same reporter from comment #1 and/or comment #5?)

I am not #1. #5 appears to be from my conversation with G Suite/Chrome support.

I use Arch, but have had the issue on Ubuntu. In Arch, it has spanned multiple kernels from ~4.6-4.8, both with and without the grsecurity patchset.

I don't recall what Ubuntu, probably Xenial. In Chromium, the error is different than in Chrome. In Chromium, it says the native client isn't working and asks me to enable the native client in chrome://plugins.

My current Chrome is 54.0.2840.100-1
My current Chromium is 54.0.2840.100-1

I do not remember the first Chrome in which I encountered the issue. Probably around 52 or 53?

Thanks!
Scott

There is no native client listed in chrome://plugins, in case that wasn't clear.

Hm, interesting. What do chrome://nacl and chrome://components say?

About NaCl

Google Chrome 54.0.2840.100 () 
OS Linux 

Chrome:
NaCl plugin /opt/google/chrome/internal-nacl-plugin 

Portable Native Client (PNaCl) Enabled 
PNaCl translator path /home/scott/.config/google-chrome/pnacl/0.56.43.1616/_platform_specific/x86_64 
PNaCl translator version f7d719122cd7c2fe3ebc52e7c0b011c583bf3e9c 

Native Client (non-portable, outside web store) Disabled 


########################################

pnacl - Version: 0.56.43.1616
Status - Component not updated

I added the word chrome in the middle by accident, intended to make clear that's form Chrome, not Chromium.

Chromium:

chrome://nacl
This site can’t be reached

The webpage at chrome://nacl/ might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL

chrome://components
pnacl/nacl are not listed.

By the way, it's possible that Chromium (this is an Arch packaging of Chromium?) was built with NaCl support disabled entirely. Building chromium with NaCl is tricky if you aren't using all of Chromium's build infrastructure, and distros usually prefer to do it their own way; so sometimes they just disable NaCl.

Looks like I raced with you. Based on #31, I'm guessing that Chromium is indeed compiled without any NaCl support.

Chrome must include NaCl, so is there a reason that is not working?

This is an Arch packaging of Chromium.

I tried rebooting into a vanilla kernel, without any additional protections. PNaCL still does not load.

Error is the same.

[1289:1319:1122/125103:ERROR:nacl_process_host.cc(337)] NaCl process exited with status 64000 (0xfa00)
[5,1405078400:20:52:01.697738] Native Client module will be loaded at base address 0x00002de700000000
[5,1405078400:20:52:01.701271] NaClHostDescMap: mprotect to turn on PROT_EXEC failed, errno 13
POST-ABORT: LOG_FATAL abort exit

Just an update, no fix in 55

I also tried enabling the nacl in flags:
Support Native Client for all web applications, even those that were not installed from the Chrome Web Store. #enable-nacl

This had no effect. There are three flags in chrome://flags that pertain to nacl. Most seem to pertain to nacl rendering. I only tried the enable nacl one above.

Hey all, still waiting on a fix. I don't mean to keep bumping a thread. I sincerely appreciate the work the chromium team has provided. 

That said, I specifically reached out to Google for Chrome support, and they assured me that Googlers would jump in. That doesn't seem to be happening. I guess I need to keep on Google, not Chromium to actually fix the native client in linux.

Google asked that I recreate with logging enabled. Would this be helpful for you guys? 

In playing with the PNaCl app extension a bit more, this is the error:
loadstart
progress: Computing...
loadend
lastError: NaCl module load failed: PnaclCoordinator: Compile stream init failed: reply not received from PNaCl translator (it probably crashed)

Some Googling yields the conclusion that it likely means PNaCl is not seeing writable memory causing a crash:
https://groups.google.com/forum/#!msg/native-client-discuss/tcoLUE_ttSQ/Hky5qYfRHVEJ

This makes sense given the numerous mprotect errors I'm seeing in logs. 

When I check chrome://nacl, it seems nacl (non-portable) is disabled, which as I understand it, is the issue, and I cannot seem to get it to enable:

About NaCl

Google Chrome 55.0.2883.87 () 
OS Linux 

NaCl plugin /opt/google/chrome/internal-nacl-plugin 

Portable Native Client (PNaCl) Enabled 
PNaCl translator path /home/scott/.config/google-chrome/pnacl/0.57.44.2492/_platform_specific/x86_64 
PNaCl translator version 5dfe030a71ca66e72c5719ef5034c2ed24706c43 

Native Client (non-portable, outside web store) Disabled 

I've seen some places where folks saw this fixed if they ran chrome(ium) as root. Which seems to reinforce there being some privilege/memory write issue.

Chrome remote desktop has worked fine for months, but all of a sudden started failing in the same way as described in this bug.

I can reproduce the problem on a freshly powerwashed Chromebook on both the developer and the beta channel (e.g. 58.0.3007.0), but notably not on the release channel (56.0.2924.10).

chrome://nacl shows that PNaCl is enabled and native client is disabled for either of those three channels. So, I suspect that's a red herring.

I don't know how to collect additional log information on Chromebooks, but if I start Chrome from a command prompt on my Linux machine, I can see these error messages:

[1,2048911168:23:15:58.694360] Native Client module will be loaded at base address 0x0000604200000000
[1,2048911168:23:15:58.782224] NaClHostDescMap: mprotect to turn on PROT_EXEC failed, errno 13
POST-ABORT: LOG_FATAL abort exit

** Signal 6 from trusted code: pc=7f7878ebb428
[28665:28698:0302/151558.782729:ERROR:nacl_process_host.cc(260)] NaCl process exited with status 64000 (0xfa00)
[1,2048911168:23:16:00.973224] Native Client module will be loaded at base address 0x0000536100000000
[1,2048911168:23:16:00.973449] NaClHostDescMap: mprotect to turn on PROT_EXEC failed, errno 13
POST-ABORT: LOG_FATAL abort exit

** Signal 6 from trusted code: pc=7f7878ebb428
[28665:28698:0302/151600.973892:ERROR:nacl_process_host.cc(260)] NaCl process exited with status 64000 (0xfa00)

On Linux, this is reproducible across all publicly released channels (stable, beta, unstable); one good example would be 56.0.2924.87, which seems to be the current stable channel for me. In fact, that should help narrow down the point when the bug started showing up for me. It seems to be between 56.0.2924.10 and 56.0.2924.87.

I am not sure what other information I could collect, but just let me know and I'll try to get you what you need. Also, I'd more than happily bring my device(s) into either the SFO or MTV office. It's about time I visit the old team again :-)

@markus: So if I understand you correctly, you can reproduce this on both CrOS and Linux?

Can you post details about which chromebook you are using (They have different kernel versions, even for the same CrOS version), and also which Linux distro, its kernel version, etc.

I use a Samsung Chromebook Plus.

On the Linux side, I am running a pretty stock Ubuntu Xenial release (16.04.2 LTS with a 4.4.0-64 kernel).

I don't think this is actually related to Chromoting; comment #15 indicates that the same problem exists for the PNaCl samples app (https://chrome.google.com/webstore/detail/pnacl-examples/mblemkccghnfkjignlmgngmopopifacf/related)

I believe you might be onto something there.

I did a very quick test here. I tried the PNaCl demo both on my Linux laptop and on the Samsung Chromebook Plus (stable channel). Fails on the former, succeeds on the latter. That is exactly the same pattern as seen for the Chromoting failure.

This obviously isn't 100% conclusive proof, but certainly strong evidence.

Do you happen to know whether there already is an applicable PNaCl bug that this bug should be merged into?

Not that I know of. We should probably just rename the bug, because it seems to affect all NaCl processes.

FWIW I just installed a stock Xenial VM on my linux desktop and beta and dev channel seem to work fine, so it seems likely that it's related to distro kernel config somehow (which seems consistent with the error messages). Can you give more info about your distro and kernel? Maybe I'll try to install Arch or something.

(Just realized my install of Xenial has kernel 4.8.0-36-generic #36~16.04.1 so it doesn't match yours)

Ah, that was a useful hint. I was scratching my head what could be different between my machine and a stock Xenial installation. And I recalled one setting-change that every couple of months causes problems with some random app.

At boot time, I run "sudo mount -o remount,noexec /tmp"

And would you have guessed, yes, that fixes PNaCl on my Linux laptop. It still doesn't explain why Chromoting doesn't work on the beta and dev channel on my Chromebook, though. Unless Chromeos has recently hardened their system in the same fashion.

Also, it sounds as if this might be a more recent change in PNaCl, because I made /tmp non-executable a really long time ago. And Chromoting has definitely been working in the past until it broke somewhat recently for me.

So, we might still be looking at an independent bug on ChromeOS, but at least Linux is vindicated. Having said that, it would be nice if PNaCl didn't rely on an executable /tmp directory.

OK, good to know about Linux. Might also help the OP/others on this thread.
WRT CrOS, I've tested on a couple devices I have lying around, and it seems to work, so I'd definitely like to get more detail on your device.

OK, while the problem on Linux seems to be solved, the problem on my Samsung Chromebook Plus persists. Chromoting works fine on the stable channel, but doesn't work on the dev channel.

Interestingly though, the PNaCl Demo App works just fine on both the stable and the dev channel.

So, that would suggest we are looking at two different problems that can manifest with similar symptoms. If PNaCl is broken, then Chromoting gets broken as well. That seems to be what I managed to trigger on Ubuntu by removing executable permission from /tmp. It would be nice if this issue either got fixed or at least output an intelligible error message. But it's a lower-priority corner case.

But there apparently still is another unrelated bug that breaks Chromoting on newer versions of Chrome and for lack of good logging tools, its symptoms happen to look very similar. This is what happens to my Chromebook Plus when put onto the dev channel.

Here is some more data about my device (when on dev channel). Hopefully it allows you to narrow things down some more:

Google Chrome	58.0.3027.0 (Official Build) dev (32-bit)
Revision	0
Platform	9331.0.0 (Official Build) dev-channel kevin
Firmware Version	Google_Kevin.8785.157.0
Customization ID	SAMSUNG-KEVIN1
ARC	3778028
JavaScript	V8 5.8.297
Flash	24.0.0.221 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS aarch64 9331.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3027.0 Safari/537.36
Command Line	/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=24.0.0.221 --ui-prioritize-in-gpu-process --use-gl=egl --edge-touch-filtering --gpu-sandbox-failures-fatal=yes --gpu-sandbox-start-early --arc-availability=officially-supported --enable-features=PointerEvent,Pepper3DImageChromium,QuickUnlockPin --passive-listeners-default=true --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --num-raster-threads=1 --enable-drm-atomic --enable-hardware-overlays=single-fullscreen,single-on-top --login-profile=user --has-chromeos-keyboard --enable-touchview --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-prefixed-encrypted-media --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-manager --vmodule=screen_locker=2,webui_screen_locker=2,lock_state_controller=2,webui_login_view=2,power_button_observer=2,*/ui/display/manager/chromeos/*=1,*/ash/display/*=1,*/ui/ozone/*=1,*zygote*=1,*plugin*=2,auto_enrollment_controller=1,*chromeos/login/*=1,*arc/*=1
Executable Path	/opt/google/chrome/chrome
Profile Path	/home/chronos/u-66129b9bb5a899e4c46fdbec478be42647d918ee
Variations	6a89113b-a7aa8ed
16e0dd70-3f4a17df
da89714-6a61fa8e
241fff6c-ca7d8d80
1e528f0f-f23d1dea
ca05d627-3f4a17df
7c1bc906-f55a7974
2a33b90e-2845784c
cf558fa6-bb299ce2
5ca89f9-f23d1dea
f3499283-ca7d8d80
31362330-ca7d8d80
349d561b-3d47f4f4
811bc6bc-d93a0620
98be3390-d93a0620
2d2fd3f5-2d2fd3f5
9e201a2b-3f4a17df
6eb432aa-f23d1dea
5274eb09-3f4a17df
57f575bb-3f4a17df
858ecb94-3f4a17df
bcc907f7-3f4a17df
949c6e63-3f4a17df
b684f56f-3d47f4f4
b791c1b8-f23d1dea
9773d3bd-1410f10
b22b3d54-3f4a17df
2e109477-ca7d8d80
99144bc3-4da47e09
9e5c75f1-61fe30c4
f79cb77b-3f4a17df
27219e67-ca7d8d80
23a898eb-3f4a17df
62d3c5a9-f23d1dea
4ea303a6-8f6ce979
3a007b7-46180e7c
64224f74-5087fa4a
de03e059-e65e20f2
d2247fcb-5086b55e
69bf80fa-91c810ef
2697ea25-ca7d8d80
b2f0086-35a81a97
7fc902e8-f23d1dea
d747916f-d747916f
f11cb941-f11cb941
494d8760-3f4a17df
3ac60855-486e2a9c
f296190c-d0fe63d6
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-a5822863
e2b18481-6754d7b7
e7e71889-e1cc0f14
89b3132e-7c7ea110
644b8345-f23d1dea
61b920c1-40a57c04
828a5926-ca7d8d80

NaCl plugin /opt/google/chrome/internal-nacl-plugin 

Portable Native Client (PNaCl) Enabled 
PNaCl translator path /opt/google/chrome/pnacl 
PNaCl translator version 5dfe030a71ca66e72c5719ef5034c2ed24706c43 

Native Client (non-portable, outside web store) Disabled 


I see a couple of crashes on my device, but since I don't believe I currently have access to the crash server (as a xoogler Chromium member), I can't tell if any of these crashes are related to this bug. Feel free to investigate, though:

2fba666120000000, b35dda6120000000, 5b3937a480000000, 766bbb23c0000000, ...


Let me know if any of this helps. Again, my offer stands and I am happy to bring the device in, if you want to experiment with it.

I've got my hands on a Kevin device to test with, that I can wipe etc. When you say that chromoting is not working, which mode do you mean? And do you mean sharing the CrOS device, or using it to access another device?

Using kevin to access another device is what's broken.

OK, update to disentangle things, because this is now a couple of different issues.

First, the OP (and part of comment #45) was really about NaCl not working at all on desktop Linux under certain situations. As markus@ mentioned in #53, a non-executable /tmp will cause NaCl not to work, and is also consistent with the error messages reported in #5 and #35. Therefore I believe It's also the solution to the original bug report.

Secondly, the other issues from Comment 45 and #57 is about CRD not working on Samsung Chromebook Plus (aka Kevin) devices. We filed  bug 701974  and we believe there's a fix for that.

So, I'm going to mark this issue as fixed.

For scott@ and shetlandhouse@ if the /tmp fix doesn't fix the original issue from this bug, it can be reopened.
For markus@, if there are further issues with CRD on Kevin or other CrOS devices, you can add to  bug 701974  or open a new bug as appropriate.

And of course if there are other issues, those could be new bugs as well.
Thanks!

Issue 698053 has been merged into this issue.