-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
[Bug]: Right click does not work or crashes VS code 1.96 (macOS) #178
Comments
Can confirm, issue appears to be macOS-only, managed to capture this exception using Debugtron:
I'll block installation on macOS VSCode 1.96.x for now. |
please update on fix |
I have the same bug in MaOS! |
I got an error, too MaOS! 1.96.0 |
Everyone on macOS with VSCode 1.96.0 and newer is currently experiencing this issue, no need to +1 unless you have something to add to the discussion.Recommended solution for now is to downgrade to 1.95.3 and disable auto-updates: https://update.code.visualstudio.com/1.95.3/darwin-universal/stable |
I've temporarily downgraded to 1.95.3 as recommended, and it's working fine. when can we expect a stable release that safely addresses the problem so we can upgrade to the latest version? |
version vs code 1.96.1, Enable vibrancy command resulted in an error: Vibrancy does not work with VSCode 1.96.x on macOS, see here for more info. |
@AdiStar350 please do not +1 unless you have something to add, I ask for this so that people can subscribe to this issue and stay up-to-date without unnecessary noise. This is a community-led project, and while I try to make fixes where I can, I have limited time to work on the more complex issues such as this one. Pull requests are most welcome if you'd like to see this fixed sooner. |
Update, I've discovered that this is an Electron bug that appears to be specific to Electron 32.2.6, we'll have to wait until VSCode updates their Electron version as the This is currently the version being used in latest stable VSCode and VSCode Insiders. It is also possible to create a custom VSCode build with updated Electron, though it'll be the OSS edition of VSCode, so I'm not sure if that's something that people would be interested in. Either way, I'll update the blocking code to check the Electron version instead, so as soon as VSCode updates it, Vibrancy will start working again. |
I've created a bug report for VSCode to update the Electron version, if this issue is affecting you then please follow this link and give the issue a 👍 reaction: microsoft/vscode#236772 Edit: the fix is set to release in January 2025 |
Any alternate extension that everyone is using? |
Any updates for this? 🥺 |
Same question! Will this fix both MacOS and Windows? |
Windows is not affected by this issue, fix is scheduled to be released in a VSCode update by the end of January, you can track progress here: microsoft/vscode#236772 |
Small update, VSCode Insiders v1.97 has already updated Electron to 32.2.7 and I can confirm that the extension works there without any issues. As soon as it's released to the public, Vibrancy will start working again in mainline VSCode. |
is it fixed ? |
According to Microsoft's next release info, VSCode 1.97 is planned to release on 5th of February: microsoft/vscode#238813 |
VSCode 1.97 is released, no issues with Vibrancy observed, everyone affected by this can go ahead and re-enable auto-updates 🎉 |
I updated to VSCode 1.97, right click still doesn't work. |
Does the problem still occur if you turn off all extensions via the triple dot menu in Extensions sidebar? Also, please go to About VSCode and copy-paste the full version info here. |
Is there an existing issue for this?
Current Behavior
In the current version of VS code 1.96, a right click either crashes VS code or does not open any menus.
Expected Behavior
VS code should not crash and the corresponding menus should be opened
Steps To Reproduce
Environment
Anything else?
No response
Update
A bug report for VSCode has been created to update the Electron version, if this issue is affecting you then please go to that issue and give it a 👍 reaction: microsoft/vscode#236772
The fix has been merged and is set to release in a VSCode update in January 2025
Edited by @illixion
The text was updated successfully, but these errors were encountered: