-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choosing colors from the command pallette shows "Activating Extensions" in the notification bar, and doesn't ever change colors #511
Comments
Thank you @tcaruth for creating this issue! |
Version - v4.2.2 |
Under Help you can get to Developer Tools which can reveal some information but it can get pretty messy in there but might be useful. I would presume it is some kind of conflict with another extension so might be worth seeing which other extensions you have that do things with the .vscode/settings.json file |
Thanks @willpower232 I checked my settings.json file in the workspace and it looks like Peacock is the only thing that's written to it. I've used this extension for months, and only recently started a new workspace that I can't set colors to. New workspaces aren't getting a .vscode/settings.json file created when I choose a color, but one is generated when i use another extension that saves settings to the workspace (for example, https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker). Even after that other extension creates the file (and I assume sets permissions on it) Peacock isn't writing any of the color customizations to the file Current settings.json in an old workspace {
"workbench.colorCustomizations": {
"activityBar.activeBackground": "#005498",
"activityBar.background": "#005498",
"activityBar.foreground": "#e7e7e7",
"activityBar.inactiveForeground": "#e7e7e799",
"activityBarBadge.background": "#ff008d",
"activityBarBadge.foreground": "#e7e7e7",
"commandCenter.border": "#e7e7e799",
"sash.hoverBorder": "#005498",
"statusBar.background": "#003865",
"statusBar.foreground": "#e7e7e7",
"statusBarItem.hoverBackground": "#005498",
"statusBarItem.remoteBackground": "#003865",
"statusBarItem.remoteForeground": "#e7e7e7",
"titleBar.activeBackground": "#003865",
"titleBar.activeForeground": "#e7e7e7",
"titleBar.inactiveBackground": "#00386599",
"titleBar.inactiveForeground": "#e7e7e799"
},
"peacock.color": "#003865"
} |
Hi ! I had the exact same issue (version 4.2.2) and disabling the Live Share extension fixed it. |
Disabling Live Share extension works for me too 🙏 thx @maximedelvaux |
Can confirm, disabling live share fixed it. |
Thanks for opening this issue. I've had this issue for a while as well but only on a corporate protected laptop. I thought it was their fault... Disabling Live Share worked for me as well. But why?! |
Oh my... I've been having issues with live share, but I can't see how they might be related! |
+1 for me, too. anyone know why that is the case? or how to setup debugging in order to find out how... |
Disabling live share made it work for me too. Has anyone got any idea why this is happening? |
I'm not sure where to collect logs that might show what's going on any better. The "Activating Extensions" notitifaction only pops up when I run Peacock commands though, and doesn't seem to be actually doing anything.
The text was updated successfully, but these errors were encountered: