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

Live Share commands not found on fresh installs #4626

Closed
Tylerwbrown opened this issue Apr 3, 2022 · 23 comments
Closed

Live Share commands not found on fresh installs #4626

Tylerwbrown opened this issue Apr 3, 2022 · 23 comments

Comments

@Tylerwbrown
Copy link

Tylerwbrown commented Apr 3, 2022

Describe what happened:
On a fresh install of both Ubuntu 22.04 and Fedora 36 (both running Gnome 42), the share/join buttons don't do anything. Manually invoking the "Live Share: Join Collaboration Session" results in an error command 'liveshare.join' not found).

Things I've tried

  • installing differently (snap (Ubuntu & Fedora), deb (Ubuntu) and rpm (Fedora)), wiping the .vscode folder between installs
  • older versions of vscode & liveshare
  • Manually installing linux dependencies - wget -O ~/vsls-reqs https://aka.ms/vsls-linux-prereq-script && chmod +x ~/vsls-reqs && ~/vsls-reqs
  • Repairing the installation

What was your system configuration?
Product and Version: VSCode - 1.66.0
OS Version:Ubuntu 22.04 & Fedora 36
Live Share Extension Version: 1.0.5449

Steps to Reproduce / Scenario:

  1. Install either Ubuntu 22.04 or Fedora 36
  2. Download VSCode either through the gnome software app or through the website
  3. Install Live Share through extensions
  4. None of the commands are found.

Please attach logs to this issue:
20220403_185304_16490119845280_VSCode.log
20220403_185304_Agent.log

@pkkid
Copy link

pkkid commented Apr 5, 2022

I believe I may be hitting this same issue on Ubuntu 22.04. I tried all the following with no success.

  • Running the menu option "Live Share: Repair Installation"
  • Uninstalling and reinstalling the extension.
  • Uninstalling the extension, deleting ~/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.5449, and reinstalling.
  • Uninstall VSCode totally, delete ~/.vscode and ~/.config/Code, and reinstall VSCode via apt.

Some interesting console logs:

Activating extension 'ms-vsliveshare.vsliveshare' failed: Connection got disposed..
[Extension Host] rejected promise not handled within 1 second: Error: RPC connection closed.
[Extension Host] stack trace: Error: RPC connection closed.

@alyssajotice
Copy link
Contributor

Thank you for the issue. This is likely caused by the agent failing to start up. We're working on some changes that should hopefully address agent startup issues.

@tenstad
Copy link

tenstad commented Apr 25, 2022

Any update on this @alyssajotice?

Also see #4646

@mickutz
Copy link

mickutz commented May 2, 2022

Definitely an issue on any Ubuntu 22.04 based distro fresh install.

@fev4
Copy link

fev4 commented May 19, 2022

Got the same problem via a Snap

@messiias
Copy link

Definitely an issue on any Ubuntu 22.04 based distro fresh install.

Same here, i'm using PopOS 22.04...

@shukrikhalid
Copy link

shukrikhalid commented May 23, 2022

Same with me using PopOS 22.04.
when installing using apt or using Pop!_OS(deb) cannot share & join
error (command 'liveshare.start' not found)
error (command 'liveshare.join' not found)

>Live Share: Repair Installation this also is not fixing this issue

The temporary solution is to install vscode using flathub (flatpak).

@Hydrog3n
Copy link

@shukrikhalid you can also install libssl1.x explain here #4646 (comment)

@shukrikhalid
Copy link

Thank you @Hydrog3n, is working.

@userhv
Copy link

userhv commented Jun 12, 2022

Same problem Fedora 36.

@Bon-1900
Copy link

Bon-1900 commented Jun 22, 2022

The same issue also exists on Ubuntu 20.04, 19.04, macOS Catalina 10.15.7 and possibly more. Quite a few people continue to experience similar errors after the closure of #2118.

@noisy
Copy link

noisy commented Jun 28, 2022

Solution/Workaround for Ubuntu 22.04: #4646 (comment)

TL;DR:

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

@Bon-1900
Copy link

While libssl1.1 seems like a fine hack, a few, myself included, experienced the error below.

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

Also mentioned in #4646 (comment), libssl1.1 is not supported for 22.04 saddly.

@jvesouza
Copy link

jvesouza commented Jul 4, 2022

The same problem in fedora workstation 36 using code-insiders

@jvesouza
Copy link

jvesouza commented Jul 4, 2022

After install libssl1.1 on my fedora box the problem was fixed.

sudo dnf install openssl1.1

Thanks.

@jonkoops
Copy link

jonkoops commented Jul 5, 2022

I can confirm this problem still exists on Fedora 36 with the official RPM.

@navneetprakash
Copy link

After install libssl1.1 on my fedora box the problem was fixed.

sudo dnf install openssl1.1

Thanks.

Works for me when installing the openssl1.1

@eureka-cpu
Copy link

Definitely an issue on any Ubuntu 22.04 based distro fresh install.

Same here, i'm using PopOS 22.04...

were you able to find a solution? Currently experiencing this Pop_OS 22.04

@jaweherbensalah
Copy link

I have the same error for Windows 10, and I am very confused, as it was working fine then suddenly crushed, .. any help please?

@RickCastle2018
Copy link

Manjaro Linux, it throws the same error OP had. Is there any solution?

@tajnymag
Copy link

For anyone running an Arch based distro, install icu69-bin from AUR. Live Share probably depends on an older version of ICU than we have in the core repository.

@RickCastle2018
Copy link

@tajnymag it worked, thanks!

@derekbekoe
Copy link
Collaborator

We’ve made improvements in this area since this issue was filed (i.e. the vsls-agent process and associated dependencies have been removed). We believe this may have improved your experience and are closing this issue. If this issue still persists for you, please comment on the issue and let us know. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests