-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Signature: UnknownError #164726
Comments
The server console also shows
|
Installing
|
CC @dtivel This is in linux arm 32 platform |
My last comment was too optimistic. Seeing this again with the next extension:
|
A few others now worked. |
Confusing, other worked just like that? May I know which extensions worked and which do not? |
@isidorn Is this being worked on or shall I move this to next milestone? |
@sandy081 it is being worked on. There is an email thread between Damon, Christof and you with more details. |
Workaround set |
Workaround did not help:
Version: 1.74.0-insider |
You might need to reload VS Code. |
Tried both reloading and explicit restarting. No luck. |
I'm having the same problem Versão: 1.74.0-insider |
@ViniciusRed I have an identical error log. Haven't been able to find a fix. This started within the last day or two for me. |
i put that into my devcontainer.json's setting object instead of settings.json and it worked for me |
Ivan |
Any update? The workaround does not work for me and as a result most of my key extensions are now out-of-date. |
@manastalukdar are you sure you applied the |
@brubrant I tried but no avail |
I install and update VSCO de using the following command:
pamac build visual-studio-code-insiders-bin
Em sáb., 10 de dez. de 2022 15:42, hypeit ***@***.***>
escreveu:
… extensions.verifySignature
What version are you using on manjaro?
I tried
[image: image]
<https://user-images.githubusercontent.com/47086634/206870515-bd9977ac-5cdc-4b7d-b28c-63449e37cf8b.png>
but no avail
—
Reply to this email directly, view it on GitHub
<#164726 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFM4QHS7YGXYA4AKRYQSTWMTFLBANCNFSM6AAAAAARPGKFCY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Update worked by adding Versão: 1.75.0-insider |
I started getting the same error a few days ago:
Version: 1.75.0-insider |
I had the same issue today. Setting to All debug infoAbout
System info
Enabled extensions
A/B experiment info
|
Sorry that, we are not clear with our instructions for the workaround. This setting has to be placed in two different files, based on your set up:
|
|
It is an internal setting and thats why it is shown unknown. That's not an issue. |
I don't understand. |
It means you can use it, but the settings editor doesn't explicitly show it as a setting you can use. But if you type it in and save it, it should work. |
After setting the |
Thanks now i understand and it works for me |
Thanks, I was only using the command palette, I thought it would have been enough. |
|
Did you put it in the user settings or the workspace settings? I put it initially in the workspace settings and it didn't work, then put it in the user sittings which did the trick. |
I've had this exact problem for at least a week now. Acting on the suggestions above, I edited |
Thanks for everybody that provided feedback here - we really appreciate it. For those that have added |
I'm running: Version: 1.75.0-insider In my User/settings.json file, I commented-out the extensions.verifySignature setting and restarted VSCode. I had to wait for some extension updates to become available and eventually a few MS+Python-related ones came up. Upon trying to apply the updates, I'm getting the "[error] UnknownError: Signature: UnknownError" message in the logs and seeing error popups in the UI again. Does this Snap not have the fix in it? If so, what would be the least-painful way of getting a build with the fix? |
@Nexus6 that snap does not have a fix in it. I suggest to just get an insiders build from this year 2023 and you should be good. It should be available from our site. |
Testing #164452
(Using VS Code Server armhf build in a Docker container with armhf hardware emulation.)
The text was updated successfully, but these errors were encountered: