vscode snap version fails to encrypt using the encryptionService #116690
Comments
weinand
added
the
freeze-slow-crash-leak
|
Can you please follow the steps in https:/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks! |
Any idea how I can send you the .dmp file @bpasero? GitHub won't accept it, I can send it via email as the link you provided suggests. |
|
@controldev GH will accept it if you first create a zip archive, but mail is also fine. |
|
Hi i have exactly the same issue, i'm attaching you the crash dmp file, can you please help me? I'm using Pop!_OS 20.10 |
|
@deepak1556 can you work your magic to symbolify? |
|
Hey guys I'm having the same issue with VSCode(non snap version) crashing upon start in a new install of Ubuntu 20.04. Snap version works fine but also takes about 1 minute to open on the very first time after a system restart. Here are my logs for the crash vscode_crash_logs_Ubuntu_20.04.zip |
|
Both the reports point to |
deepak1556
added
linux
|
Hello, I think I am having the same issue and I may have some useful debug info. I am running vscode 1.53.2 on two Kubuntu 20.10 machines, a laptop and a desktop. It works fine on the desktop, but not on the laptop. I can think of one thing that I did differently on these two machines: on the laptop, I used to have the snap package and switched to the apt package; on the desktop, I never installed the snap package. The snap package still works on the laptop, but the apt package does not (just like @inc0der reported). Additionally, the code-insiders apt package works just fine on the laptop. The fact that I am not having any issues on the desktop makes me wonder if some configuration was changed when the snap package was installed that is preventing the apt package from running correctly. Anyways, I have attached my crash report as well. Hope this helps. |
|
Symbolicated trace |
|
Can everyone check if you have entries in login keyring under either of the service named |
I had an entry for |
|
Thanks for checking, at this point I don't have a good way to analyze the issue because that involves inspecting the stored value or having a reliable repro both of which aren't possible. It would help if we have a repro. @RMacfarlane will add some logs to atleast narrow down which extension is triggering this. From the user end, if possible can you check if the values under those keys are valid base64 strings ? |
|
The startup crash is now fixed in latest insiders and will also be fixed in next stable release |
Fixes #116690 vscode-encrypt fails to load with GLIBC_2.25 not found error. ldd vscode-encrypt.node libstdc++.so.6 => /snap/core/current/usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fc887a3a000) libgcc_s.so.1 => /snap/core/current/lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc887824000) libpthread.so.0 => /snap/core/current/lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc887607000) libc.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libc.so.6 (0x00007fc88723d000) libm.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libm.so.6 (0x00007fc886f34000) /lib64/ld-linux-x86-64.so.2 (0x00007fc8882bc000) libc.so.6 from ubuntu16.04 core is not sufficient for support. Switching to core18 matches with the build environment used for the native module https:/microsoft/vscode-linux-build-agent/blob/main/bionic-x64/Dockerfile
Fixes #116690 vscode-encrypt fails to load with GLIBC_2.25 not found error. ldd vscode-encrypt.node libstdc++.so.6 => /snap/core/current/usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fc887a3a000) libgcc_s.so.1 => /snap/core/current/lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc887824000) libpthread.so.0 => /snap/core/current/lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc887607000) libc.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libc.so.6 (0x00007fc88723d000) libm.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libm.so.6 (0x00007fc886f34000) /lib64/ld-linux-x86-64.so.2 (0x00007fc8882bc000) libc.so.6 from ubuntu16.04 core is not sufficient for support. Switching to core18 matches with the build environment used for the native module https:/microsoft/vscode-linux-build-agent/blob/main/bionic-x64/Dockerfile
Fixes #116690 vscode-encrypt fails to load with GLIBC_2.25 not found error. ldd vscode-encrypt.node libstdc++.so.6 => /snap/core/current/usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fc887a3a000) libgcc_s.so.1 => /snap/core/current/lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc887824000) libpthread.so.0 => /snap/core/current/lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc887607000) libc.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libc.so.6 (0x00007fc88723d000) libm.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libm.so.6 (0x00007fc886f34000) /lib64/ld-linux-x86-64.so.2 (0x00007fc8882bc000) libc.so.6 from ubuntu16.04 core is not sufficient for support. Switching to core18 matches with the build environment used for the native module https:/microsoft/vscode-linux-build-agent/blob/main/bionic-x64/Dockerfile
|
/closedWith bebab7e |
and others
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
VS code automatically crashes and closes a few seconds after start up, with no popup or other information provided.
I tried purging (including all settings), reinstalling (both through snap and apt), but no luck.
Below are the only logs visible after running Code with
code --disable-extensionsI wanted to try changing
git.enabledtofalseinsettings.json, but the path indicated in the official docs (https://code.visualstudio.com/docs/getstarted/settings) does not containsettings.json.The text was updated successfully, but these errors were encountered: