[BUG] Atom update 1.40.1 did not rectify ink installation failure issue for me

[Gwango]

I had not used Atom/Juno on this machine since May, and recently was trying to get it back into working condition to begin coding again. I walked through several issues (beginning with Juno's #391 then #397) before hitting what appeared to be #234, receiving a simple Error: Installing “[email protected]” failed. when booting up Atom after installing uber-juno. I have read that Atom 1.40.1 addressed this issue, however while it has fixed this issue for another machine in my lab, it does not seem to have addressed the issue for mine; what's stranger, rolling back to Atom 1.39.1 does not fix the issue here either. As I was simultaneously debugging a MiKTeX issue while attempting this (and not thinking the bug would be a significant roadblock), I am a bit uncertain as to all the steps I took to get where I am, but here is a summary of where I am/what I've tried currently:

• Atom: 1.39.1, 1.40.0, and 1.40.1
• OS: Ubuntu 18.04.3 LTS
• apm -v:
  • apm 2.2.4
  • npm 6.2.0
  • node 8.9.3 x64
  • atom 1.39.1
  • python 2.7.15+
  • git 2.17.1

Each attempt, I am:

1. Uninstalling all of the installed packages in Atom
2. Removing Atom via sudo apt-get --purge remove atom
3. Downloading the .deb (again, I've tried 1.39.1, 1.40.0, and 1.40.1)
4. Installing with the software manager
5. Installing uber-juno via sudo apm install uber-juno
6. Booting up Atom via sudo atom

Step 6 brings up another data point: if I attempt to start atom without sudo, I get a very bare Atom gui with the following error:

Error: EACCES: permission denied, open '/usr/local/home/mjg6y5/.atom/compile-cache/less/df1b7fbc57dbeed23a8f1f8de95b4dfebcc06066/imports.json'
at Object.fs.openSync (fs.js:577)
at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:166:20)
at Object.fs.writeFileSync (fs.js:1321)
at Proxy.writeFileSync (/usr/share/atom/resources/app/static/:11)
at LessCache.writeJson (/usr/share/atom/resources/app/static/:14)
at LessCache.setImportPaths (/usr/share/atom/resources/app/static/:14)
at new LessCache (/usr/share/atom/resources/app/static/:14)
at new LessCompileCache (/usr/share/atom/resources/app/static/:14)
at ThemeManager.loadLessStylesheet (/usr/share/atom/resources/app/static/:11)
at ThemeManager.loadStylesheet (/usr/share/atom/resources/app/static/:11)
at ThemeManager.requireStylesheet (/usr/share/atom/resources/app/static/:11)
at ThemeManager.reloadBaseStylesheets (/usr/share/atom/resources/app/static/:11)
at ThemeManager.loadBaseStylesheets (/usr/share/atom/resources/app/static/:11)
at AtomEnvironment.initialize (/usr/share/atom/resources/app/static/:1)
at t.exports (/usr/share/atom/resources/app/static/:1)
at setupWindow (index.js:163)
at window.onload (index.js:105)

This may be due to permission restrictions (this is a university machine), but I also never needed to use sudo in the past.

Let me know if I've omitted any info you are curious in.