search

microsoft / live-share

Real-time collaborative development from the comfort of your favorite tools
http://aka.ms/vsls
Creative Commons Attribution 4.0 International
2.28k stars 253 forks source link

Problem with terminal during live share #3505

Open xfoscarz opened 4 years ago

xfoscarz commented 4 years ago

Describe what happened: When in live share, the collaborator's terminal would be blank, and when they type, it would type on other collaborators terminals but their terminal would still be blank. Basically, they can type but they can't see the terminal for some reason. Also, when I open node js and leave node js, the terminal on the collaborator still says that the language is: 1: node [Shared]

Screen Shot 2020-05-08 at 4 02 36 PM

Version: 1.44.2 Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd Date: 2020-04-16T17:07:18.473Z (3 wks ago) Electron: 7.1.11 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Darwin x64 18.7.0

What was your system configuration? Product and Version [VS/VSCode]: 1.44.2 OS Version[macOS/Windows]: macOS, Darwin x64 18.7.0, macOS Mojave 10.14.6 Live Share Extension Version: 1.0.3 Target Platform or Language [e.g. Node.js]: Terminal was running regular bash/shell

Steps to Reproduce / Scenario:

  1. Open the terminal (im pretty sure you have to leave terminal open)
  2. Start collab session
  3. When the people who join come in, the terminal will be blank, and when they type, the terminal is still blank, but what they typed appeared on the host's terminal.

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 Logs.zip

Screenshots If applicable, add screenshots to help explain your problem.

nandiniYeltiwar commented 4 years ago

@ChezCoder Thanks for reporting the issue. If you shared another terminal while in the session, do you still see blank terminal?

infalmo commented 4 years ago

Face the same issue too. +1

xfoscarz commented 4 years ago

No @nandiniYeltiwar , if I open a new terminal and share it, the other person will be able to see it

sfogarty commented 4 years ago

This seems to happen mostly when I have read-write access. If I do not have r/w access to the terminal, then I do see their updates, but the lines often don't appear in correct location/order when a long string of text is sent.

davipbl commented 3 years ago

I am experiencing this same issue. I can't share my terminal as it appears only as this black bar as input, but isn't printing anything.

davipbl commented 3 years ago

I am experiencing this same issue. I can't share my terminal as it appears only as this black bar as input, but isn't printing anything.

So, apparently I was able to 'unlock' my terminal by clicking on the 'Maximizing Panel Size' button, located on the top right of the terminal. Me and my friend were able to type into the shared terminal. Maximize button panel

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically in 2 days.

nyabinary commented 1 year ago

Same here

MaxValue commented 9 months ago

Still existing. I guess this is the same bug as: Host opens new read/write terminal, guest sees it. Only the message Host shared a Live Share terminal. Enter to type. is displayed. When pressing Enter, nothing happens. Only the input of the host is visible to the guest. Outcome: guest cannot interact with the read/write terminal.

I am on Mac OS with VS Code Version: 1.86.0 Live Share Version: v1.0.5905

Trying to connect to a LiveShare Session on Windows 11

EDIT: Restart of the host machine (Windows) fixed the issue. This should not be needed in 2024, Microsoft.

dadlobster commented 5 months ago

Same issue, running VS Code on windows 11 w WSL2 and trying to access the terminal through VS Code on a mac