live-share
live-share copied to clipboard
microsoft
Activating extension fails on Ubuntu 18.04.4
Issue Type: Bug
Cannot activate the extension, it returns this error:
Activating extension 'ms-vsliveshare.vsliveshare' failed: A system error occurred: uv_os_get_passwd returned ENOENT (no such file or directory). _logMessageInConsole @ /snap/code/31/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3826
System Info: Ubuntu 18.04.4
Extension version: 1.0.2048 VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T17:50:03.709Z) OS version: Linux x64 5.3.0-46-generic snap
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz (8 x 3991) |
| GPU Status | 2d_canvas: unavailable_software flash_3d: disabled_software flash_stage3d: disabled_software flash_stage3d_baseline: disabled_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: disabled_off rasterization: disabled_software skia_renderer: disabled_off_ok video_decode: disabled_software viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: unavailable_software webgl2: unavailable_software |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 15.36GB (8.67GB free) |
| Process Argv | --force-user-env --no-sandbox --unity-launch --no-sandbox |
| Screen Reader | no |
| VM | 0% |
@rodsscg: Thanks for filing this issue! I'm opening a bug to fix the issue. It looks like it might be due to the account you're running under not having an entry for os.userInfo(). In the interim if you're able to run under a different account that supports this it might resolve your issue. If you're able to try that out and confirm I'll update the notes in the bug.
Found this issue using an LDAP account. How to get around this? reference: https://github.com/MicrosoftDocs/live-share/issues/3914
Since it's seems to be only a minor passwd issue due to ldap login, it's kind of sad that this is still not fixed or even has been triaged. Since a lot of companies rely on ldap I'm suppres this has no bigger impact.
Anyway I found a dirty workaround that works for me: Simply create a new local user. Let's say "yournewuser". Login as this user via GUI-Login and install and use the extension with this user.
If you don't like to switch Users in GUI, it's a bit more complicated, but possible as well:
- create a new local user "yournewuser"
- As your normal user run: xhost + sudo su - yournewuser
- as yournewuser run: export DISPLAY=:0.0 code
- install the extension again
- use the login process as requested from the extension
- In the final login step within your browser use: "THE SYSTEM RUNNER" and not "VSCODE" app directly
Please note that there might exist a couple of other issues with this process.
We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it is for you.
