Closed ZhenyaGoroh closed 1 week ago
It seems to disrupt all the text in the extension section.
Could reproduce in 1.95.1
@ZhenyaGoroh Try this two ways to make a fix: how-to-uninstall , vscode-crashes
@comradez @Zylsjsp Have you also encountered it and is it also on Ubuntu?
same problem on fedora 40
OK, I found a machine and will investigate the cause
@shalldie I'm on Archlinux, using AUR package. The issue should be reproduced on any linux installation. I'll try reinstalling the plugin to see if the issue also reproduces on Mac.
On a new Mac universal installation v1.95.1 it's OK.
Ubuntu 24.04.1 LTS
, I've tested it in vscode 1.95.1
which installed by .deb
.Ubuntu 24.04.1 LTS
, also works fine with vscode 1.95.0
, #485 vscode of binary version
is not supported. #408
Snap
is not supported. #382
The above are some of the issues I have summarized, which will be added to the Common Issue. There are too many Linux distributions for me to test one by one. I hope everyone can give some suggestions when they have time.
Edit: vscode of binary version is supported.
I have the same issue on VSCodium 1.95.1, Fedora 41 (not binary version).
By the way, it's not just not working, but break all strings in VSCode (like this)
I'm using Ubuntu 24.04.1 LTS
, and I installed my vscode via the .deb
file from the vscode site using apt-get
. Still experiencing the same problems.
I tried to uninstall the extension and install again, to no avail. It seems like the newest vscode update broke the extension. You should look into it.
.deb package
sudo apt install ./<file>.deb
@vbuchara Is this your way to install vscode? Which .deb do you choose, x64 、Arm32 or Arm64 ?
- Download the
.deb package
- And run
sudo apt install ./<file>.deb
@vbuchara Is this your way to install vscode? Which .deb do you choose, x64 、Arm32 or Arm64 ?
Amd64. I can say that's it's probably something that vscode changed on 1.95 that is causing the issue. I rolled back to 1.94, and everything is working fine.
@shalldie It's not a distribution-specified issue, fix on any distribution will benefit all other distributions.
The extension ruins the whole vscode
As @ZhenyaGoroh indicated, the extension seems corrupted css files. I have a post-install script for my VSCode to substitute VSCode logo in blank page with customized one. It is implemented in Python with built-in re
module, and works well still in 1.95.x.
You should be able to reproduce the issue through a brand-new installation of linux VSCode, getting this extension clearly uninstalled and removed, then install again.
EDIT: I'm not so familiar with Node.js, so maybe it would take long before I could figure out the reason and maybe have a fix.
@Zylsjsp It will edit the js file since v2.
It's not always reproducible, at least in my case ... Some users are also using Ubuntu normally.
I have tried Ubuntu 24.04.1 LTS (amd6)
, Fedora 40 (arm64)
in a vm, and It works fine.
I am still trying =。=
又尝试了 Ubuntu 24.04 LTS (aarch64)
无果。
感觉可能是我的某个姿势不太对,方便加个Q进一步沟通吗?在你有空的时候 @Zylsjsp
qq**
@Zylsjsp It will edit the js file since v2.
It's not always reproducible, at least in my case ... Some users are also using Ubuntu normally.
I have tried
Ubuntu 24.04.1 LTS (amd6)
,Fedora 40 (arm64)
in a vm, and It works fine. I am still trying =。=
Perhaps it is language dependent? What language are you setting on the vscode? It doesn't help I've never seen an error like this before, so I understand the struggle.
Perhaps it is language dependent? What language are you setting on the vscode? It doesn't help I've never seen an error like this before, so I understand the struggle.
@vbuchara I tried both default English(en) and zh-cn.
Two question:
OUTPUT
of Extension Host
?I don't know if it's related to my use of virtual machines
Perhaps it is language dependent? What language are you setting on the vscode? It doesn't help I've never seen an error like this before, so I understand the struggle.
@vbuchara I tried both default English(en) and zh-cn.
Two question:
- Have you ever seen some error or strange msg in
OUTPUT
ofExtension Host
?- Once uninstall the extension, vscode restored to normal?
I don't know if it's related to my use of virtual machines
I will see later if something odd appears on the ouput channel.
I have upgraded my system to Fedora 41, and the bug was fixed, everything seems to work fine ... 🤔
@shalldie Only thing that caught my eye was this, after I let the extension use sudo to execute the JS to change the background.
@shalldie Only thing that caught my eye was this, after I let the extension use sudo to execute the JS to change the background.
After some digging, this doesn't seem related to the current issue, but you did leave here a piece of throw-able code untreated. It doesn't stop the background from working, but it makes so the "Background has changed!" notification doesn't go through, because the code stopped at the exception.
As far as I could see, the problem seems to be with the new workbench.desktop.main.js
generated by the extension, but I'm not sure what exactly.
I managed to get its contents, copied the portion appended by the extension, pasted on the old workbench.desktop.main.js
(Before the extension altered it with the sudoExec(cmdarg, { name: 'Background Extension' })
), and everything seems to be fine.
@vbuchara Thanks a lot ! Because I cannot reproduce it here, it is very difficult to find the reason for it.
sudoExec
I managed to get its contents, copied the portion appended by the extension, pasted on the old workbench.desktop.main.js
What's the difference between these two files? Or can you send out the file?
Same problem here, all the buttons on vscode seem to be text-corrupted until I reinstall vscode.
@vbuchara Thanks a lot ! Because I cannot reproduce it here, it is very difficult to find the reason for it.
- New workbench.desktop.main.js generated by the extension, after
sudoExec
I managed to get its contents, copied the portion appended by the extension, pasted on the old workbench.desktop.main.js
What's the difference between these two files? Or can you send out the file?
I don't know, I skimmed over both files, I didn't spot a huge difference. It doesn't help it's a big minified file, so it's hard to spot anything.
I can also say that this diference is weird, since your code just reads from the original file and adds to it. Maybe try to use fs or some other command to append to it? Instead of reading the contents and creating a new file.
Same problem on Nobara 40 (modified version of Fedora). It only happens on version 1.95.0 and later of VSCode, version 1.94.2 is ok. I didn't see anyone sharing this warning message, I get it every time I start VSCode after activating the extension with sudo/admin:
I didn't see anyone sharing this warning message, I get it every time I start VSCode after activating the extension with sudo/admin:
This is just the "Your VSCode installation is corrupt" message but with screwed up localization
/usr/share/code
、/opt/visual-studio-code
), then install again./usr/share/code
、/opt/visual-studio-code
), 重装。Fixed in v2.0.2
Summary | 概述
The extension ruins the whole vscode
Versions