Chrome SSH extension just showing a black box, never loads

[Chris Williams]

I'm having an issue with the Chrome SSH extension.  This appears to be happening on all of my ChromeOS devices (Acer CB315, Pixel Slate, Lenovo 100e MTK).  When I click on the extension icon, I just see a little square that I can't interact with at all.  I've tried uninstalling/reinstalling the extension and also Powerwashing with no luck.  All of my devices are running the current stable version of ChromeOS (93.0.4577.95).

If I go into Manage Extensions to get the extension ID and try to manually go to chrome-extension://[ID]/html/nassh.html , it still only ever shows a black screen.  I'm not sure what other troubleshooting steps I can even take.  How can I get this working again?

[Mike Frysinger]

hit Ctrl+Shift+J to bring up the console and copy & paste any errors you see

-mike

On Thu, Oct 7, 2021 at 6:01 PM Chris Williams <cjw...@gmail.com> wrote:

I'm having an issue with the Chrome SSH extension.  This appears to be happening on all of my ChromeOS devices (Acer CB315, Pixel Slate, Lenovo 100e MTK).  When I click on the extension icon, I just see a little square that I can't interact with at all.  I've tried uninstalling/reinstalling the extension and also Powerwashing with no luck.  All of my devices are running the current stable version of ChromeOS (93.0.4577.95).

If I go into Manage Extensions to get the extension ID and try to manually go to chrome-extension://[ID]/html/nassh.html , it still only ever shows a black screen.  I'm not sure what other troubleshooting steps I can even take.  How can I get this working again?

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/a185a9d0-36a9-4630-b563-31ce07ab5120n%40chromium.org.

[Chris Williams]

Looks like there are 3 errors:

1. X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.

2. Unchecked runtime.lastError: accept-languages is empty.

3. Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')

    at new lib.MessageManager (nassh_deps.concat.js:2234)
    at nassh_deps.concat.js:5227
    at async Object.lib.init (nassh_deps.concat.js:113)

[Mike Frysinger]

the first one is fine.  annoying, but to be expected.

the 2nd one is interesting, but shouldn't be a problem by itself ...

but that leads us to the 3rd which def shouldn't be happening.

can you double check & confirm which version of Secure Shell you're using ?  and which [ID] it is ?  you should be able to look these up via chrome://extensions/.

-mike

[Chris Williams]

Version: 0.42

ID: iodihamcpbpeioajjeobimgagajmlibd

[Mike Frysinger]

thanks, that lets me trace the generated code precisely

looks like the 2nd error is leading directly to the 3rd error you showed.  i assume you're using a Chromebook from/in the US, and just with English as a configured language ?

in that JS console you opened, please try running this.  i formatted it so you can copy & paste it as a single line.

l=console.log;try{l('lib.i18n.browser_',lib.i18n.browser_);}catch(e){l(e)};try{l('lib.i18n.browser_.getAcceptLanguages',lib.i18n.browser_.getAcceptLanguages);}catch(e){l(e)};try{l('lib.i18n.browser_.getAcceptLanguages()',lib.i18n.browser_.getAcceptLanguages(l));}catch(e){l(e)};try{l('chrome.i18n',chrome.i18n);}catch(e){l(e)};try{l('chrome.i18n.getAcceptLanguages',chrome.i18n.getAcceptLanguages);}catch(e){l(e)};try{l('chrome.i18n.getAcceptLanguages()',chrome.i18n.getAcceptLanguages(l));}catch(e){l(e)};

then copy & paste the output here.  the last few lines *should* look like ['en-US', 'en'], but if you aren't getting that, something is funky.

-mike

[Chris Williams]

It still came back saying it was empty.  I've attached a screenshot of that output.

It looks like I was able to mess around and fix this based on where you were steering me.  You are right about this just being US/English.  When I went into the Languages in Settings, you can see in the other screenshot that it had both English (United States) and English.  I tried to remove 'English', but it didn't do anything.  What I ended up doing was switching to English (Canada) and then switching back to English (United States).  It just seems fine now.

Thanks so much for your help.  Is there anything else I can try to gather that might help anything?

[Mike Frysinger]

thanks, that screenshot is perfect.

that said, what you saw is very weird.  your Chrome browser should never have gotten into this state.  can you file feedback with Alt+Shift+i (outside of Secure Shell) ?  that will gather system information and it might have enough for me to file a bug report.

in the meantime, we can improve Secure Shell to fallback to ['en'] if nothing shows up.

-mike

[Chris Williams]

I just sent in the report.

[Mike Frysinger]

thanks, i found it.  filed https://crbug.com/1258498 for it.  hopefully someone on the browser side can take a look or route to the right people.

-mike

[Mike Frysinger]

not that it super matters since you've recovered your system, but i've merged https://crrev.com/c/3216447 for the next release.  it would fallback to 'en' if your situation were hit again.

at least i think/hope that's what it'll do since i have no way of reproducing the exact behavior :).

-mike

[Chris Williams]

Thanks again for all your help with this.  I really appreciate it.