New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 743075 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ sandeepkumars@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Secure Shell crash on start up. Error initializing filesystem

Reported by joe.bike...@gmail.com, Jul 14 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Install Secure Shell version 0.8.36.6.
2. Launch it
3. An error message appears and the app does not start correctly

What is the expected behavior?
The app should show the main menu from where it is possible to set up a new ssh connection.

What went wrong?
This is the java console log:

init: hterm
nassh_deps.concat.js:190 init: nassh
nassh_main.js:39 Did you know there is a dedicated options page?
No need to mess with term_ directly anymore!
chrome-extension://pnhechapfaindjhompbnflcldabbghjo/html/nassh_preferences_editor.html
nassh_deps.concat.js:14176 Unobserverd VT keystroke: "\r"
nassh_deps.concat.js:17940 Error initializing filesystem: InvalidStateError: An operation that depends on state cached in an interface object was made but the state had changed since it was read from disk. Object
(anonymous) @ nassh_deps.concat.js:17940
nassh_command_instance.js:110 FileSystem init failed: 
(anonymous) @ nassh_command_instance.js:110
nassh_deps.concat.js:4582 Uncaught TypeError: str.charCodeAt is not a function
    at Object.lib.encodeUTF8 (nassh_deps.concat.js:4582)
    at hterm.Terminal.IO.println.hterm.Terminal.IO.writelnUTF16 (nassh_deps.concat.js:14243)
    at nassh_command_instance.js:113
    at nassh_deps.concat.js:17942
nassh_deps.concat.js:14176 Unobserverd VT keystroke: "\u0003"

WebStore page: Secure Shell

Did this work before? Yes Pre-0.8.36.6

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 6.3
Flash Version:

Comment 1 by sandeepkumars@chromium.org, Jul 19 2017

Labels: Needs-Feedback
Unable to reproduce the issue using #59.0.3071.115 on Windows 8.1 as per the steps mentioned in comment #0.
Able to add and launch the Secure Shell.

@joe: Could you please find the attached screen cast and try creating a new profile from chrome://settings and check if you still face the issue?

Thanks!1
Jul 18 2017 10-17 PM.webm
2.9 MB View Download

Comment 2 by joe.bike...@gmail.com, Jul 21 2017 

Issue fixed by completely remove Secure Shell add-on and reinstall it.
Using as reference the screen cast provided, it works correctly.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 21 2017

Cc: sandeepkumars@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by hdodda@chromium.org, Jul 24 2017

Status: WontFix (was: Unconfirmed)
Based on comment #2 , marking this as wontfix as this issue no longer exists.

Please feel free to raise a new issue if any issues faced in latest chrome channels.

Thanks!
►

Sign in to add a comment