Closed mtomasz-chromium closed 5 years ago
Glad I found this via G+ / search - "me too" (v1.7.5):
Linux localhost 3.8.11 #1 SMP Thu Apr 2 00:21:50 PDT 2015 armv7l SAMSUNG EXYNOS5 (Flattened Device Tree) GNU/Linux
[84,3057790976:10:08:50.709372] Native Client module will be loaded at base address 0x0000000000000000
SftpInstance::SftpInstance
SftpInstance::SftpInstance End
SftpInstance::HandleMessage
SftpInstance::HandleMessage connect 0
SftpThread::SftpThread
SftpInstance::HandleMessage SftpThread instance created
SftpThread::ConnectAndHandshake
SftpThread::ConnectAndHandshake Thread started
SftpInstance::HandleMessage End
SftpThread::ConnectAndHandshakeImpl
SftpThread::InitializeLibssh2
SftpThread::InitializeLibssh2 rc=0
SftpThread::ConnectToSshServer
SftpThread::ConnectToSshServer sock=3
SftpThread::ConnectToSshServer sockaddr_in ready
** Signal 11 from untrusted code: pc=1e3314
[1920:2337:0421/110851:ERROR:nacl_process_host.cc(293)] NaCl process exited with status 62720 (0xf500)
[1920:2337:0421/110938:ERROR:channel.cc(305)] RawChannel read error (connection broken)
[101,3057790976:10:09:43.209976] Native Client module will be loaded at base address 0x0000000000000000
SftpInstance::SftpInstance
SftpInstance::SftpInstance End
SftpInstance::HandleMessage
SftpInstance::HandleMessage connect 0
SftpThread::SftpThread
SftpInstance::HandleMessage SftpThread instance created
SftpThread::ConnectAndHandshake
SftpThread::ConnectAndHandshake Thread started
SftpInstance::HandleMessage End
SftpThread::ConnectAndHandshakeImpl
SftpThread::InitializeLibssh2
SftpThread::InitializeLibssh2 rc=0
SftpThread::ConnectToSshServer
SftpThread::ConnectToSshServer sock=3
SftpThread::ConnectToSshServer sockaddr_in ready
** Signal 11 from untrusted code: pc=1e3314
[1920:2337:0421/110943:ERROR:nacl_process_host.cc(293)] NaCl process exited with status 62720 (0xf500)
Anything I can do to help debug/diagnose this, please let me know!
@yoichiro not sure if you noticed yet, but the behaviour changed in Chrome v42. It doesn't report a crash anymore on ARM, just hangs after Attempting to mount instance...
Don't know if that affects Intel chromebooks as well.
@stevedowe Thanks! I'll ask you when I want to test a new code.
@folbricht Hmm... I can't understand the detail situation, but I'm preparing a new code set which the new toolchain "clang-newlib". Testing for my Intel-based Chromebook was almost done.
I have just released the new version 1.7.6. This version includes the nexe files compiled by the new toolchain "clang-newlib". @yusukes san already tested this version on the ARM-based Chromebook. If you have ARM-based Chromebook, could you try the version 1.7.6 on your Chromebook? Then, if you find some issue, feel free to post the issue here.
It works - we're back in business!
Thank you very much for fixing this bug. This is such an important tool for me to maintain files on my kodi system.
Vijay
On Sun, Apr 26, 2015 at 9:32 AM, Yoichiro Tanaka notifications@github.com wrote:
I have just released the new version 1.7.6. This version includes the nexe files compiled by the new toolchain "clang-newlib". @yusukes https://github.com/yusukes san already tested this version on the ARM-based Chromebook. If someone has ARB-based Chromebook, could you try the version 1.7.6 on your Chromebook? Then, if you find some issue, feel free to post the issue here.
— Reply to this email directly or view it on GitHub https://github.com/yoichiro/chromeos-filesystem-sftp/issues/25#issuecomment-96378685 .
1.7.6 works for me too. Thanks for fixing it. I love this app.
1.7.6 is now working on my HP Chrombook 11. Thank you! Great app!
Works on my Samsung 303! Yay, and just in time for the 'Add New Services' option in the Files app which should be hitting Stable soon.
Quick question: If I remember right there used to be fields for both the SSH public and private keys but now there's just one for the private key. Does this mean the app wants a combo file in pem format?
@andmalc In my application, I recognize that only the private key is necessary, because the public key should be registered into the server you want to access.
Oops, all these years I thought the client presented the public key to the server which then somehow validated it against the private key.
Anyway, I found my problem: invalid characters from copying my private key out of the terminal.
1.7.6 works perfectly now on my HP 14 Chromebook. Thanks, yoichiro, for the hard work!
I tried to connect to my FTP account. The FTP volume is correctly mounted, but when I click on it in Files app, it shows spinner for around a minute, then the NaCL module crashes.