Vscodium: Permissions wrong after brew cask install (~/.vscode-oss)

Created on 25 Apr 2020  路  3Comments  路  Source: VSCodium/vscodium

Describe the bug
I am unable to install packages. When I click "install" on a package in the sidebar, a dialog pops up in the bottom right that says, for example, "Failed to install 'pkief.material-icon-theme'."

Please confirm that this problem is VSCodium-specific

  • [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

  • [x] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

  1. Go to extensions sidebar
  2. Search for any extension
  3. Click install
  4. See error

Expected behavior
I expected the package to install

Screenshots
Screen Shot 2020-04-23 at 9 18 59 AM

Desktop (please complete the following information):
Screen Shot 2020-04-23 at 9 19 17 AM
Screen Shot 2020-04-23 at 9 20 24 AM

Additional context
Let me know if any debug logs would be helpful :~)

Most helpful comment

I was just able to fix this after running a chown of the extension directory, but I'm unsure what caused the permissions to be incorrect in the first place. I certainly haven't touched the permissions until now.

I ran:

sudo chown -R myusername ~/.vscode-oss/extensions/

All 3 comments

I was just able to fix this after running a chown of the extension directory, but I'm unsure what caused the permissions to be incorrect in the first place. I certainly haven't touched the permissions until now.

I ran:

sudo chown -R myusername ~/.vscode-oss/extensions/

@sdaitzman Thanks for the answer. Fixed.

I installed the VScodium through brew cask install vscodium command as suggested in the website.

I had few files with root user ownership in this folder ~/.vscode-oss/extensions/,

When I tried to watch all the installed extensions then the main file causing the issue was ~/.vscode-oss/extensions/.obselete again with the root user ownership.

with your command, I change the ownership to my user and it worked.

@fahid-aiond 鈽猴笍

Okay, so now that this is confirmed: seems like a next step would be trying to figure out what causes those permissions to be configured like that.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wmhilton picture wmhilton  路  30Comments

JL2210 picture JL2210  路  55Comments

penyuan picture penyuan  路  26Comments

sdaitzman picture sdaitzman  路  40Comments

hypercube33 picture hypercube33  路  22Comments