Skip to content
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

'VSCodium's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VSCodium.' #1809

Closed
1 of 2 tasks
secondl1ght opened this issue Feb 22, 2024 · 26 comments
Labels
bug Something isn't working

Comments

@secondl1ght
Copy link

Describe the bug
After just updating VSCodium I opened the application and got the following error:

VSCodium's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VSCodium.

Please confirm that this problem is VSCodium-specific

  • 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

To Reproduce
Steps to reproduce the behavior:

  1. Update version
  2. See error on startup

Expected behavior
No error.

Screenshots
image

Desktop (please complete the following information):

  • Ubuntu
  • VSCodium v1.86.2

Additional context
Thanks

@secondl1ght secondl1ght added the bug Something isn't working label Feb 22, 2024
@ToMattBan
Copy link

Yup. Happens here too, and just in the last version "1.86.2"
In the previous version "1.85.2" it don't happen.

Going a little deeper into this, I discovered that the error is about the TS extension not founding this file here: "/usr/share/codium/resources/app/extensions/node_modules/typescript/lib/typescript.js". In fact, the 1.86.2 don't even have the "node_modules" folder, so it can't find the typescript stuff.

Hope it helps you guys to solve this problem!

@daiyam
Copy link
Member

daiyam commented Feb 22, 2024

oh!

@daiyam
Copy link
Member

daiyam commented Feb 22, 2024

I will have to check it...

@daiyam
Copy link
Member

daiyam commented Feb 22, 2024

I'm pretty sure it's due to that line:

tar -cz --exclude='.build/node' --exclude='**/node_modules' -f vscode.tar.gz vscode

(done so we can support glibc2.17)

@ToMattBan
Copy link

@daiyam if you need someone to test, just let me know.

@daiyam
Copy link
Member

daiyam commented Feb 22, 2024

@ToMattBan will do

@alsongard
Copy link

Same issue
O.S : Kali Rolling
Version: 2024.1
@daiyam Great Software

@yttiiz
Copy link

yttiiz commented Feb 22, 2024

Hello @daiyam, i've got the same error after updating VSCodium 1.85.2 to 1.86.2
OS: Ubuntu 22.04.4 LTS
Thanks for your work frérot.

edit :
I have also a Volar (Vue) extention installed and it try to find out typescript.js file but can't.
[Error - 22:49:51] Server initialization failed. Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /usr/share/codium/resources/app/extensions/node_modules/typescript/lib Code: -32603
I think that it will affect any extention that depends on this file.

@f-fusco
Copy link

f-fusco commented Feb 22, 2024

I'm having the same issue on v1.86.2.

@daiyam
Copy link
Member

daiyam commented Feb 23, 2024

@ToMattBan and others, a test version is available at https://github.com/VSCodium/vscodium/actions/runs/8012468841 (in the artifact bin-x64)
First of all, do you have access? Can you test it? Thx

And, for me, the typescript service is now correctly working.

@nsoolo
Copy link

nsoolo commented Feb 23, 2024

Same error for me, downgrading made the job for now.

image

@0xca551e
Copy link

@daiyam I was able to access the test version. I tested the AppImage from the bin-x64 artifact and it works fine 👍

@daiyam
Copy link
Member

daiyam commented Feb 23, 2024

1.86.2.24054 is out and fix the issue.

@nsoolo
Copy link

nsoolo commented Feb 23, 2024

Amazing, Thanks very much

@yttiiz
Copy link

yttiiz commented Feb 23, 2024

Works fine now. Thanks so much for your reactivity @daiyam, you the best !

@daiyam daiyam closed this as completed Feb 23, 2024
@ToMattBan
Copy link

Thank you @daiyam .
The new version works like a charm! I tested with some extensions that were bugging but now everything are working as expected!

@bitstein
Copy link

Thank you @daiyam. How long does this usually take to enter the debs repository?

@daiyam
Copy link
Member

daiyam commented Feb 23, 2024

to enter the debs repository

What do you mean?

@bitstein
Copy link

to enter the debs repository

What do you mean?

This: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo

I currently cannot downgrade using it, so I will have to wait until it is updated. It’s not an issue, per se, so I thought it might be okay to ask here in this thread.

@ToMattBan
Copy link

@bitstein I just installed using the deb in the release section for now. It should update itself when launching new versions. No need to wait to install from the deb repos

@daiyam
Copy link
Member

daiyam commented Feb 23, 2024

@ToMattBan No, on Linux, the automatic updates are disable due to some users clicking on the update (which resulted to other issues) when they should use the app manager. I've also assumed that those who are using the .deb, known how to update it themself.

@ToMattBan
Copy link

@daiyam Sorry, I build my sentence wrong. Didn't mean automatic update, but automatic search for updates. At least here, when I downgraded I got a update request in my update manager.

@martinbarilik
Copy link

to enter the debs repository

What do you mean?

This: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo

I currently cannot downgrade using it, so I will have to wait until it is updated. It’s not an issue, per se, so I thought it might be okay to ask here in this thread.

i guess we'll have to wait ....

@daiyam
Copy link
Member

daiyam commented Feb 24, 2024

Sorry, I didn't understand the issue.
There is the error when building the repo: ERROR: Uploading artifacts as "archive" to coordinator... 413 Payload Too Large id=6239193797 responseStatus=413 Payload Too Large status=413 token=glcbt-65
@paulcarroty, maybe the Insiders version isn't needed in the repo? What do you think?

@daiyam
Copy link
Member

daiyam commented Feb 26, 2024

It has been fixed.

For reference: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/issues/98

@bitstein
Copy link

Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

10 participants