live-share
live-share copied to clipboard
Live Share not doing anything on linux
Describe what happened: Live Share basically isn't doing anything. Although it's installed and shows in the left panel and command palette, the buttons in the left panel don't work and the command palette gives a "command liveshare.start not found". I've tried deleting misc stuff to no avail. What was your system configuration? Product and Version [VS/VSCode]: VS Code latest 1.66.2 OS Version[macOS/Windows]: Ubuntu 22.04 Live Share Extension Version: v1.0.5527 Target Platform or Language [e.g. Node.js]: Website, not relevant
Steps to Reproduce / Scenario: Not quite sure to put here? I guess I'll just restate
Although it's installed and shows in the left panel and command palette, the buttons in the left panel don't work and the command palette gives a "command liveshare.start not found".
Please attach logs to this issue: loggg.zip You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Screenshots
I think I captured a lot in this screenshot...
I have exactly the same issue on a fresh install of Ubuntu 22.04. Worked perfectly on 20.04. On 22.04 it's a new VS Code installation with all settings and extensions being synced from the 20.04 installation. The sync has been deactivated as of now.
Uninstalling and reinstalling the extension does nothing useful, nor does the "repair" command (which at least starts, though).
Perhaps Ubuntu 22.04 is the culprit?
I am also having this issue on Arch Linux as well.
Had exactly the same issue, comented on #180, try to install another libicu package, it might be the cause of the problem
(after a fresh install of my old libicu package it showed me this error, i had to install another one)
Had exactly the same issue, comented on #180, try to install another libicu package, it might be the cause of the problem
This doesn't seem to be the problem on Ubuntu 22.04, as currently there is only one amd64 libicu package available (libicu70 / 70.1-2).
On Arch Linux installing icu69
from AUR solved the problem for me for the extension on visual-studio-code-bin
.
this is not an available fix for ubuntu ^ just as a fyi for anyone else here
I've enabled debug diagnostics and out for liveshare on an Ubuntu 22.04 installation and got the following:
[Client I] Extension, IDE, OS : VSLS/1.0.5527 VSCode/1.66.2 Linux/5.15.0-27-generic
[Client I] Passed version check for Linux: found 5.15.0-27-generic
[Client.Rpc V] RPCClient.init retryCount:0 currentRetryInterval:0
[Debug.Rpc.Host V] TrackDebugManager created
[Client.Rpc V] Agent connection not completed: Error: connect ECONNREFUSED /tmp/CoreFxPipe_vscode.c27740359df36ed4371e6c2d997613d7; Retrying...
[Client.Rpc V] RPCClient.init retryCount:1 currentRetryInterval:100
[Client.Agent V] Agent lock on:</<redacte/<redacte.lock>
[Client.Agent I] starting agent with pipe:vscode.c27740359df36ed4371e6c2d997613d7
[Client.Agent I] signalR service -> uri:https://signlr-prod.core.vsengsaas.visualstudio.com/api/signalr/signalrhub
[Client.Agent V] Finished agent startup...
[Client.Agent V] Agent unlocked
[Client.Rpc I] Agent connection success - net.pipe://localhost/vscode.c27740359df36ed4371e6c2d997613d7
[Client.Rpc V] finish initialize agent session with rpcConnectId:null hostSessionId:1
[Client.Rpc.Auth V] < version.exchangeVersions()
[Client.Rpc.Auth V] > version.exchangeVersions() succeeded t:14.0
[Client I] Client version: 1.0.5527 (VSLS/2.2), agent version: 1.0.5527.20886 (VSLS/2.2)
[Client.Rpc.Auth V] < version.exchangeSettings()
[Client.Rpc.Auth V] > version.exchangeSettings() succeeded t:12.0
[Client.Rpc V] < telemetry.initialize()
[Client.Agent I] No usable version of libssl was found
[Client.Agent I] Aborted (core dumped)
[Client.Agent I] Agent terminated with exit code: 0 and signal null:
[Client.Rpc I] RPC connection closed. disposed: "false"
[Client.Rpc V] disposing reason: 'Error: RPC connection closed.', disposing 0 objects
[Client.Rpc E] > telemetry.initialize() error: undefined
In particular, note this line:
[Client.Agent I] No usable version of libssl was found
in my system, libssl v3 is installed:
❯ apt list "libssl*" --installed
Listing... Done
libssl-dev/jammy,now 3.0.2-0ubuntu1 amd64 [installed]
libssl3/jammy,now 3.0.2-0ubuntu1 amd64 [installed,automatic]
libssl3/jammy,now 3.0.2-0ubuntu1 i386 [installed,automatic]
which means that liveshare is probably not compatible with this version of libssl, and should probably be updated to reflect that. docs/reference/linux.md says that libssl1.0 is required for this extension, but it is not available in ubuntu jammy repositories.
Thing is, there's not even an error message for this since openssl is correctly installed in my sytem(v3.0.2, same as libssl) so the linux-prereqs.sh
script does not even report a problem here.
hopefully this helps someone figure out how to fix this problem
I might have found a temporary workaround. It started working for me after I installed libssl1.1
from the impish-security
repo.
Here are the commands:
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list
sudo apt update
sudo apt install libssl1.1
Hey everyone, sorry about this issue and thanks for your patience. I was able to repro this today. When the Live Share buttons don't work, this indicates that the agent is not activated. It should auto-activate, but if it doesn't, we can try to start it manually. You can navigate to the vsls-agent executable by finding it in the .vscode-server/extensions/ms-vsliveshare.{VERSION}/dotnet_modules
folder. When I recently installed it this morning, it was in my root folder.
When I tried running the executable, it was missing dependencies, which led me to discover that dotnet is not supported for Ubuntu 22.04. This appears to be the reason Live Share is not working. Here is the issue tracking that release: https://github.com/dotnet/core/issues/7038.
Hopefully this provides some helpful context about the issue. Feel free to use other supported versions of Ubuntu in the meantime. For future reference, here is our information about Live Share for Linux and the dependencies that are needed. And thanks to everyone helping provide workarounds.
In the meantime, I will continue to evaluate the workarounds, and if we find one that works, we can add it to the installation script.
I might have found a temporary workaround. It started working for me after I installed
libssl1.1
from theimpish-security
repo.Here are the commands:
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list sudo apt update sudo apt install libssl1.1
This one works. Thank you @gorfeelt
I might have found a temporary workaround. It started working for me after I installed
libssl1.1
from theimpish-security
repo.Here are the commands:
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list sudo apt update sudo apt install libssl1.1
live saver, this works :+1: thanks
Hey everyone, sorry about this issue and thanks for your patience. I was able to repro this today. When the Live Share buttons don't work, this indicates that the agent is not activated. It should auto-activate, but if it doesn't, we can try to start it manually. You can navigate to the vsls-agent executable by finding it in the
.vscode-server/extensions/ms-vsliveshare.{VERSION}/dotnet_modules
folder. When I recently installed it this morning, it was in my root folder.When I tried running the executable, it was missing dependencies, which led me to discover that dotnet is not supported for Ubuntu 22.04. This appears to be the reason Live Share is not working. Here is the issue tracking that release: dotnet/core#7038.
Hopefully this provides some helpful context about the issue. Feel free to use other supported versions of Ubuntu in the meantime. For future reference, here is our information about Live Share for Linux and the dependencies that are needed. And thanks to everyone helping provide workarounds.
In the meantime, I will continue to evaluate the workarounds, and if we find one that works, we can add it to the installation script.
based on the dotnet issue linked i think "dotnet is not supported on ubunut 22.04" is inaccurate. they state dotnet(core) 3.1 and net 5 arent supported net6+ will be supported.
So it looks like the solution has to be update liveshare deps to work with dotnet 6+ for any OS that ships with openssl3 by default
looks like this will come to a head (all the above workarounds will fall out of date) next september based on release info from openssl directly https://www.openssl.org/source/
I might have found a temporary workaround. It started working for me after I installed
libssl1.1
from theimpish-security
repo.Here are the commands:
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list sudo apt update sudo apt install libssl1.1
This one did it for me, thanks for sharing the solution.
Hi all, I updated the installation script to add libssl1.1 for Ubuntu. This fixed the problem for me when I installed a fresh Ubuntu 22.04, installed Live Share, then ran the script. Thanks for all the contributions!
Here is a link to the command and script: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux#install-linux-prerequisites.
i tried running the script but it failed with E: Package 'libssl1.1' has no installation candidate
on Ubuntu 22.04.
here's the full logs
(*) Updating package lists...
Hit:1 https://download.docker.com/linux/ubuntu focal InRelease
Hit:2 http://ppa.launchpad.net/openrazer/stable/ubuntu jammy InRelease
Hit:3 http://packages.microsoft.com/repos/code stable InRelease
Hit:4 https://deb.nodesource.com/node_16.x focal InRelease
Hit:5 http://ppa.launchpad.net/polychromatic/stable/ubuntu jammy InRelease
Hit:6 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:7 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:8 https://packages.cloud.google.com/apt cloud-sdk InRelease
Hit:9 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:11 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
(*) Verifying .NET Core dependencies...
Reading package lists...
Building dependency tree...
Reading state information...
libicu70 is already the newest version (70.1-2).
libicu70 set to manually installed.
libkrb5-3 is already the newest version (1.19.2-2).
libkrb5-3 set to manually installed.
zlib1g is already the newest version (1:1.2.11.dfsg-2ubuntu9).
zlib1g set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
(*) openssl already installed.
Reading package lists...
Building dependency tree...
Reading state information...
Package libssl1.1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libssl1.1' has no installation candidate
(*) Verifying keyring dependencies...
Reading package lists...
Building dependency tree...
Reading state information...
gnome-keyring is already the newest version (40.0-3ubuntu2).
gnome-keyring set to manually installed.
libsecret-1-0 is already the newest version (0.20.5-2).
libsecret-1-0 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
(*) Verifying browser integration dependencies...
Reading package lists...
Building dependency tree...
Reading state information...
desktop-file-utils is already the newest version (0.26-1ubuntu3).
desktop-file-utils set to manually installed.
x11-utils is already the newest version (7.7+5build2).
x11-utils set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
(*) Success!```
I am also unable to install libssl1.1 on Ubuntu 22.04 Desktop, as it is not available as an install candidate. Standard (and rather fresh) install, universe and multiverse are enabled, system is completely up-to-date. The install script linked by @alyssajotice produces the same output as shown by @dermasmid.
Not sure why libssl1.1 seems to be available for some installs but not for others?
@frank-straetz hello, did you well add impish-security
in your apt source ?
https://github.com/MicrosoftDocs/live-share/issues/4646#issuecomment-1115120608
So I investigated this problem for a bit, and it seems like there simply is no libssl1.1 for Ubuntu 22.04, no matter which install we are talking about:
https://packages.ubuntu.com/search?keywords=libssl1.1&searchon=names&suite=all§ion=all
@frank-straetz hello, did you well add
impish-security
in your apt source ?
No. In my opinion, this is not a problem resolution, but a workaround / hack. One can not expect all users of VS Code working with Ubuntu 22.04 to add apt repositories of older Ubuntu versions to their sources.list. (And they may not even be able to do so.) Also, this is not even documented as a required workaround at https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux#install-linux-prerequisites.
I might have found a temporary workaround. It started working for me after I installed
libssl1.1
from theimpish-security
repo.Here are the commands:
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list sudo apt update sudo apt install libssl1.1
Thanks a lot, finally works on ubuntu 22.04 LTS
Any tips for the Snap code-insiders
app in Arch? Not working either.
Just in case, I've just checked and I have all the libs required by the community editions:
gcr liburcu openssl-1.0 krb5 zlib icu gnome-keyring libsecret desktop-file-utils xorg-xprop icu69
But still the Live Share on Snap doesn't seem to work.
My remote is running the latest Raspberry Pi OS x64. I tried Repair Installation
and the prerequisites installation script, but the developer tools still shows
Activating extension 'ms-vsliveshare.vsliveshare' failed: Agent terminated with exit code: 0 and signal null: /bin/sh: 1: /home/pi/.vscode-server-insiders/extensions/ms-vsliveshare.vsliveshare-1.0.5597/dotnet_modules/vsls-agent: Exec format error.
In my case uninstalling extension codetogether did the trick. This was how my extension host log looked like
[2022-06-14 10:10:12.698] [exthost] [error] Error: No matching bindings found for serviceIdentifier: Symbol(Logger)
at /home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:18180
at g (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:18477)
at e (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:18968)
at Object.t.plan (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:19631)
at /home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:16289
at e._get (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:16198)
at e.get (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:594:14910)
at Object.t.deactivate (/home/marcello/.vscode/extensions/genuitecllc.codetogether-2022.1.6/out/extension.js:3:108516)
at m._deactivate (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:13083)
at /opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:10642
at Array.map (<anonymous>)
at m._deactivateAll (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:10630)
at m.terminate (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:11010)
at m.terminate (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:92:620)
at l (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:36401)
at Socket.<anonymous> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:102:34097)
at Socket.emit (node:events:402:35)
at Socket.emit (node:domain:475:12)
at Pipe.<anonymous> (node:net:687:12)
[2022-06-14 10:10:12.944] [exthost] [error] ProxyResolver#resolveProxy undefined Canceled: Canceled
at Object.L [as canceled] (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:5:1172)
at s._remoteCall (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:13902)
at Proxy.p.<computed>.M.charCodeAt.p.<computed> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:10298)
at S.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:87:21082)
at Object.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:59769)
at useProxySettings (/opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:159:16)
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:107:13
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:336:13
[2022-06-14 10:10:12.945] [exthost] [error] ProxyResolver#resolveProxy undefined Canceled: Canceled
at Object.L [as canceled] (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:5:1172)
at s._remoteCall (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:13902)
at Proxy.p.<computed>.M.charCodeAt.p.<computed> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:10298)
at S.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:87:21082)
at Object.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:59769)
at useProxySettings (/opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:159:16)
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:107:13
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:336:13
[2022-06-14 10:10:12.945] [exthost] [error] ProxyResolver#resolveProxy undefined Canceled: Canceled
at Object.L [as canceled] (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:5:1172)
at s._remoteCall (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:13902)
at Proxy.p.<computed>.M.charCodeAt.p.<computed> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:86:10298)
at S.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:87:21082)
at Object.resolveProxy (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:59769)
at useProxySettings (/opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:159:16)
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:107:13
at /opt/visual-studio-code/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:336:13
On Arch here with ICU 71.1-1 and Live Share fails for me as well on fresh install of both VS Code and . Just thought I'd chime in with what fixed it for me:
Set the env var DOTNET_SYSTEM_GLOBALIZATION_INVARIANT to 1 (export DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1
) prior to starting VS Code is a workaround for me.
This issue has popped up again, now even the workaround does not work, since Ubuntu Impish has reached it's EOL and it's repositories are no longer accessible
The patch is no longer working on Ubuntu 22.04 LTS. Any workarounds?
It was also not working for me. I tried installing libssl1.1
from the above steps but didn't work for me. Then I tried installing it manually.
wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb
sudo dpkg -i libssl1.1_1.1.0g-2ubuntu4_amd64.deb
I hope this would do the job...
I think it might be worth re-opening this issue? I'm also on Ubuntu22.04 and tried the fix of installing libssl1.1
but it failed to install. After checking out Ubuntu's package manager website for libssl1.1 here it seems as though the package doesn't exist.
Maybe there is another place that I can get this package installed, but right now I can't get it installed using the workaround listed above, nor can I get it working with apt
or apt-get
.
It was also not working for me. I tried installing libssl1.1 from the above steps but didn't work for me. Then I tried installing it manually. wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb sudo dpkg -i libssl1.1_1.1.0g-2ubuntu4_amd64.deb I hope this would do the job...
This works for me! Thanks! @The15thSin
echo "deb http://security.ubuntu.com/ubuntu impish-security main" | sudo tee /etc/apt/sources.list.d/impish-security.list sudo apt update sudo apt install libssl1.1
This workaround was no longer effective.
OS: Ubuntu 22.04 LTS 5.15.0-41-generic
It was also not working for me. I tried installing
libssl1.1
from the above steps but didn't work for me. Then I tried installing it manually.wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.0g-2ubuntu4_amd64.deb
sudo dpkg -i libssl1.1_1.1.0g-2ubuntu4_amd64.deb
I hope this would do the job...
This works, Tks!