Live-share: "Live share" button doesn't appear; void linux #vsliveshare

Created on 9 Apr 2019  路  9Comments  路  Source: MicrosoftDocs/live-share

Issue Type: Bug

voidlinux #vsliveshare

I can't see the button "Live share" in the blue bar below. I tried the version from the repo of my distro (Void Linux) and the appimage https://code.visualstudio.com/docs/?dv=linux64. I've tried appimage on a laptop with Fedora and it worked. The installation of the extension didn't report any error and gone well. Vscode works really well but the only thing isn't working is vsliveshare. Another important thing is this message written on a pannel in the right under contacts: "There is no data provider registered that can provide view data." I tried to press all the options in - session details - but in the blue bar appears only "Activating Extensions... " then nothing happens.

Extension version: 1.0.18
VS Code version: Code - OSS 1.33.0 (Commit unknown, 2019-04-05T07:44:24.679Z)
OS version: Linux x64 4.19.32_1


System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz (4 x 2052)|
|GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
surface_synchronization: enabled_on
video_decode: unavailable_off
webgl: enabled
webgl2: enabled|
|Load (avg)|0, 1, 1|
|Memory (System)|7.67GB (3.40GB free)|
|Process Argv|--unity-launch|
|Screen Reader|no|
|VM|0%|


Most helpful comment

dupe of #2030

I'm working on making liveshare work with Linux distros that don't have openssl 1.0. Closing this issue, and tracking the work there.

All 9 comments

The "There is no data provider..." message is probably a red herring. If you don't see the "Live Share" button in the status bar, that usually indicates our agent process (a process we run external to VS Code and the VS Code extension host) failed to start. You can view logs from the agent process using the Live Share: Export Logs command from the command palette (ctrl + shift + p). You can either go through them yourself looking for an indication of the issue or attach them here.

Our general Linux support doc is here, but note that we don't explicitly support Void.

@daytonellwanger here there's the log of vsliveshare from the command Live Share: Export Logs :smile:

vsliveshare-log.zip
I've installed libressl-2.8.3_1 and libssl46-2.8.3_1 but it doesn't seem to find libssl. I suggest libssl46 is what is needed by vsliveshare but I'm not sure.
In the terminal I've tried to see where is libssl.

`[riccardo@tuxvoid` ~]$ whereis libssl
libssl: /usr/lib/libssl3.so

Yup, as per the logs, it looks like the issue is with libssl - No usable version of the libssl was found. +@Chuxel @Priya91 , our libssl issue experts 馃槃

Yup, as per the logs, it looks like the issue is with libssl - No usable version of the libssl was found. +@Chuxel @Priya91 , our libssl issue experts

If I tag them with @Chuxel @Priya91, will they receive advice or notification to this post to comment? Or shall I ask them to help using GitHub chat (if it exists) or an email..? :wink:

Yes, they'll get a notification.

Same for me

$ whereis libssl
libssl: /usr/lib/libssl3.so /usr/lib64/libssl3.so

As of March 2019, this shouldn't be required. We have updated .NET Core 2.1 and later to pick up and work with either OpenSSL 1.1 or 1.0 (whatever is available). So this problem should no longer happen with recent releases of .NET Core.

My case could be related to: https://github.com/dotnet/core/issues/1930

[2019-04-16 20:08:44.802 Client.Rpc V] RPCClient.init retryCount:1 currentRetryInterval:100
[2019-04-16 20:08:44.809 Client.Agent V] Agent lock on:/home/FDisk/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.45/dotnet_modules/vsls-agent.lock
[2019-04-16 20:08:44.810 Client.Agent I] starting agent with pipe:vscode.5c9b431e14a83ee5bf305f9971eedee0
[2019-04-16 20:08:45.577 Client.Agent V] Finished agent startup...
[2019-04-16 20:08:45.578 Client.Agent V] Agent unlocked
[2019-04-16 20:08:45.579 Client.Rpc I] Agent connection success - net.pipe://localhost/vscode.5c9b431e14a83ee5bf305f9971eedee0
[2019-04-16 20:08:46.185 Client.Agent I] Cannot get required symbol EC_KEY_set_public_key_affine_coordinates from libssl
[2019-04-16 20:08:46.495 Client.Rpc I] RPC connection closed.
[2019-04-16 20:08:47.048 Client E] Unhandled promise rejection: 
RPC connection closed.

p.s. I followed https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux

I'm having the same issue after upgrading to Ubuntu 19.04. When trying to install the dependencies manually again I get this:

(*) Verifying .NET Core dependencies...
Reading package lists...
Building dependency tree...
Reading state information...
libicu63 is already the newest version (63.1-6).
libicu63 set to manually installed.
libkrb5-3 is already the newest version (1.17-1).
zlib1g is already the newest version (1:1.2.11.dfsg-1ubuntu2).
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
Reading package lists...
Building dependency tree...
Reading state information...
Package libssl1.0.0 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.0.0' has no installation candidate
(!) libssl1.0.0 installation failed!

20190426_123511_15562821116300_VSCode.log

dupe of #2030

I'm working on making liveshare work with Linux distros that don't have openssl 1.0. Closing this issue, and tracking the work there.

I could fix the issue with this workaround:

export CLR_OPENSSL_VERSION_OVERRIDE=46
Was this page helpful?
0 / 5 - 0 ratings