You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What was your system configuration? Product and Version [VS/VSCode]: VSCode 1.71.0 & Insiders OS Version[macOS/Windows]: Ubuntu 22.04 & Fedora 36 & Linux Mint 20.3 Live Share Extension Version: v1.0.5711 Target Platform or Language [e.g. Node.js]: Rust
Install Live Share & rust-analyzer (or other extensions)
Share session
Joining session does not start rust-analyzer (or other extensions) on the joined vscode
Please attach logs to this issue: You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Hi @johannescpk, thank you for reaching out. This is a known issue on .NET Core dependencies. Please checkout this discussion and, see this workaround solution here. I am closing issue to consolidate. Please let us know if you still have the same problem.
It's not the libssl1.1 issue. I had to install libssl1.1 to make LiveShare work at all on Linux.
This issue concerns itself specifically with shared extension usage. So, joining sessions works – but extension sharing does not. So the joining session will not load extensions, even if host and guest have the same extensions installed.
Shared editing and other basic LiveShare functionality does work.
Describe what happened:
What was your system configuration?
Product and Version [VS/VSCode]: VSCode 1.71.0 & Insiders
OS Version[macOS/Windows]: Ubuntu 22.04 & Fedora 36 & Linux Mint 20.3
Live Share Extension Version: v1.0.5711
Target Platform or Language [e.g. Node.js]: Rust
Steps to Reproduce / Scenario:
Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
liveshare.log
Note
This used to work just fine. Couldn't test with participants other than linux hosts.
The text was updated successfully, but these errors were encountered: