Chrome Version       : 56.0.2924.28
OS Version: 9000.29.0

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 9000.29.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36

A bit of a saga(TM) follows, apologies in advance:

I was fiddling with some MD-related flags the other day, when one of them caused the system to lock up, requiring a restart.  Business as usual.

Upon reboot, I found that two enterprise-pushed extensions, Secure Shell (pnhechapfaindjhompbnflcldabbghjo) and Gnubbyd (beknehfpfkghjoafdifaflglpjkojoco) were unusable, showing generic icons.

I tried to use Crosh to figure out what's going on, but unfortunately, Crosh uses Secure Shell's crosh.html, which was missing (file not found error screen).

I dropped into frecon and looked at ~/Extensions/pnhechapfaindjhompbnflcldabbghjo, and found that within 0.8.34.4_0, only metadata files remained.  Deleting the extension directory entirely and attempting to launch Secure Shell in the UI still resulted in file not found, instead of recreating the extension folder.

I created html/crosh.html with some junk in it, switched back to ui, and upon opening Crosh, the extension validator kicked in and created 0.8.34.4_1 with proper Secure Shell and everything worked.  I deleted the old 0.8.34.4_0 directory with the metadata and junk crosh.html and everything continues to behave normally.

Next, gnubbyd: there was no extension folder at all.  I attempted the same trick, creating beknehfpfkghjoafdifaflglpjkojoco/0.9.46_0/util.js with some junk in it and attempting to launch gnubbyd, but this didn't work.  I also tried to directly open the file using chrome-extension://, but that didn't work either.

I noticed on another machine that gnubbyd was actually 0.9.46_1, so I moved the directory to 0.9.46_1, and created symlinks of 0.9.46_0 and 0.9.46_2 all pointing to 0.9.46_1 and tried again.  Still no dice.

Finally, I copied the entire directory from the other machine to 0.9.46_1 and rebooted.  The gnubbyd app worked, but upon looking into beknehfpfkghjoafdifaflglpjkojoco, only the 0.9.46_0 symlink remained, pointing to a nonexistent 0.9.46_1.  I tried removing 0.9.46_0 and gnubbyd stopped launching again, although it's possible it would have not worked if I had tried it a second time without making any changes.  I then restored 0.9.46_1 and the 0.9.46_0 symlink, and gnubbyd worked (without rebooting/logging out).  I tried removing the 0.9.46_0 symlink and gnubbyd stopped working.  I added the symlink back and it worked again.


So it's possible there are two issues here:

1. A missing file does not appear to trigger the code that re-downloads an extension when it becomes corrupt/externally modified.
2. gnubbyd??? I can't even summarize.