I'm surprised the ARM Chromebook shipped without any mechanism for indicating which apps in the Chrome Web Store are compatible with it (maybe they expected PNaCl to be completed?). Moreover, I had no idea what NaCl was until Secure Shell stalled and I tracked down the bug on a mailing list.

There's an enable "Portable Native Client" (PNaCl) in about:flags (dev. branch, at least), but I have little idea if this would fix the problem. This kind of troubleshooting is OK for power users, but seems at odds with the type of users ChromeOS wants to attract. Still love this machine, though.

I picked up a Samsung ARM Chromebook two weeks ago, installed both the latest Secure Shell and the Development version. Neither worked :-/