New issue
Advanced search Search tips

Issue 847896 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

nassh: 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

Project Member Reported by wfh@chromium.org, May 30 2018 
Chrome Version: 69.0.3445.0 (Official Build) canary (64-bit) (cohort: Clang-64)
OS: Windows 10

What steps will reproduce the problem?
(1) Launch Secure Shell App 0.8.43
(2)
(3)

What is the expected result?

Launches

What happens instead?

Does not launch


Please use labels and text to provide additional information.

In the terminal window it says:

Welcome to Secure Shell App version 0.8.43.
Answers to Frequently Asked Questions: https://goo.gl/muppJj (ctrl+click on links to open)
ChangeLog/release notes: https://goo.gl/YnmXOs

Random Pro Tip #8: Chat with fellow hterm/Secure Shell users via chromium-hterm@chromium.org: https://goo.gl/RYHiK

An unexpected error occurred, please check the JavaScript console for more details.

The log from console is attached.
pnhechapfaindjhompbnflcldabbghjo-1527697875374.log
972 bytes View Download

Comment 1 by vapier@chromium.org, May 30 2018

Status: Available (was: Untriaged)
Summary: nassh: 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 (was: hterm fails to initialize)
nassh_deps.concat.js:19475 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

unfortunately, every time we've seen this failure, it seems to be a problem with Chrome, and people workaround it by:
- backing up their preferences
- uninstalling the extension
- installing the extension
- restore the preferences

or if they're on a Chromebook, removing their account and creating it again.

Comment 2 by wfh@chromium.org, Jun 4 2018

Status: WontFix (was: Available)
Hmm, this just went away on its own. not sure why. I did have to re-verify all the hosts though

The authenticity of host 'xxxxx' can't be established.
RSA key fingerprint is SHA256:xxx

So perhaps something wiped this storage and reinitialized it. I did not lose my host definitions.

Either way, this sounds like WontFox (unreproducible).
►

Sign in to add a comment