Issue metadata
Sign in to add a comment
|
NaCL fails to load gnubby |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 53.0.2773.0 (Official Build) dev (64-bit) Revision ced2fcee2c85702055d028f4e3e48c5a75a7e41c-refs/heads/master@{#400610} Platform 8481.0.0 (Official Build) dev-channel panther Blink 537.36 (@ced2fcee2c85702055d028f4e3e48c5a75a7e41c) JavaScript V8 5.3.256 Flash 22.0.0.192-r1 To reproduce: Connect gnubby Open a web page that requires gnubby touch Verify web page accepts gnubby touch Open secure shell Expected behavior: gnubby requests touch Actual behavior: Failure with code 255 Notes: Logs from secure shell: Loading NaCl plugin... done. 0706 11:52:09.208000: SSH forward helper not installed: 0706 11:52:09.218000: Specified native messaging host not found. 0706 11:52:09.471000: onMessageExternal listener: STATUS 0706 11:52:09.475000: request 0706 11:52:09.480000: sender 0706 11:52:09.529000: Enumerated 0 gnubbies 0706 11:52:09.530000: Enumerated 2 gnubbies 0706 11:52:13.436000: onMessageExternal listener: OPTIONS 0706 11:52:13.437000: request 0706 11:52:13.438000: sender 0706 11:52:13.674000: onMessageExternal listener: STATUS 0706 11:52:13.675000: request 0706 11:52:13.679000: sender 0706 11:52:13.693000: Enumerated 0 gnubbies 0706 11:52:13.696000: Enumerated 2 gnubbies 0706 11:54:10.855000: onMessageExternal listener: OPTIONS 0706 11:54:10.856000: request 0706 11:54:10.857000: sender 0706 11:54:11.001000: onMessageExternal listener: STATUS 0706 11:54:11.001000: request 0706 11:54:11.002000: sender 0706 11:54:11.003000: Enumerated 0 gnubbies 0706 11:54:11.004000: Enumerated 1 gnubbies 0706 11:54:11.017000: openDevice got lastError: 0706 11:54:11.017000: Failed to open device. 0706 11:54:11.017000: failed to open device. permissions issue? 0706 11:54:14.622000: onMessageExternal listener: GET_LOG 0706 11:54:14.623000: request 0706 11:54:14.624000: sender ssh_exchange_identification: Connection closed by remote host NaCl plugin exited with status code 255. I have also noticed that the gnubby app has problems and have filed bug b/29943535
,
Jul 7 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 7 2016
I was wrong, I do this did break on chell. Rolling back to beta-channel fixed it. Google Chrome 52.0.2743.65 (Official Build) beta (64-bit) Revision 388aa6dc38681ee43a78b53b352dcab213beda6e-refs/branch-heads/2743@{#576} Platform 8350.50.0 (Official Build) beta-channel chell Blink 537.36 (@388aa6dc38681ee43a78b53b352dcab213beda6e) JavaScript V8 5.2.361.34 Flash 22.0.0.192-r1
,
Jul 19 2016
krisr@ do we have a fix? What is the CL?
,
Jul 20 2016
krisr@ can you please update the bug with any updates?
,
Jul 22 2016
Ok after a wipe it is now fixed: Google Chrome 53.0.2785.23 (Official Build) dev (64-bit) Revision 054b2180d14203fa3bbe22628b85ef13a4ecc452-refs/branch-heads/2785@{#241} Platform 8530.24.0 (Official Build) dev-channel panther Blink 537.36 (@054b2180d14203fa3bbe22628b85ef13a4ecc452) JavaScript V8 5.3.332.19 Flash 22.0.0.209-r1 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krisr@chromium.org
, Jul 6 2016