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.

Sign up for GitHub

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

Jump to bottom

install fails to create directory in /run/user/7413 #126313

Closed
pabtor opened this issue Jun 14, 2021 · 9 comments
Closed

install fails to create directory in /run/user/7413 #126313

pabtor opened this issue Jun 14, 2021 · 9 comments
Assignees
@bpasero @deepak1556
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@pabtor
Copy link

pabtor commented Jun 14, 2021

Issue Type: Bug

I have been using Visual Studio Code and Code-Insiders for several months and noticed a few months ago that I could no longer invoke it after installing a new version. I tried version 1.54.0 of code-insiders and 1.53.2 of code and neither would invoke on my Red Hat 7 based machine. I tried a different Red Hat 7 based machine as well and couldn't run there either.

Today I decided to try code-insiders 1.58 and ran into the same issue.

I finally tracked down the issue to this sequence:

  1. I am running on Exceed on Demand on a Red Hat 6 server. From this, I log into a Red Hat 7 or Red Hat 8 server using ssh and install code-insiders running as root from that shell.

  2. I exit the root shell and then try to invoke code-insiders with DISPLAY set to my Red Hat 6 Exceed on Demand display.

  3. nothing happens - no message or anything.

Today, after this happened again, I logged into my Red Hat 8.3 based server in a VNC session. That machine had already been installed with code-insiders 1.58 using the same ssh followed by rpm install that I described above. I attempted to invoke code-insiders there, and I get a dialog that says that I need to make sure that a couple of directories are writable:

~/.config/Code - Insiders - it was OK - there and writable
~/.vscode-insiders/extensions - it was OK - there and writable
/run/user/7413 - it was not there

7413 is my Unix user id.

I ran again as root and created the directory and chown'ed it to my user name.

I was then finally able to invoke code-insiders.

So, in all, I think there are two problems:

  1. there seems to be a chicken and egg problem in making sure that the directory /run/user/ gets created in time for it to be needed by code-insiders.

  2. there seems to be a problem showing the error dialog when using Exceed on Demand over a DISPLAY variable.

VS Code version: Code - Insiders 1.58.0-insider (e1161be, 2021-06-14T05:13:48.044Z)
OS version: Linux x64 4.18.0-240.el8.x86_64
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (4 x 2497)
GPU Status 2d_canvas: unavailable_software
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: disabled_off
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
Load (avg) 1, 0, 0
Memory (System) 15.46GB (2.94GB free)
Process Argv --crash-reporter-id a127b379-56aa-4b65-aeb3-cd1564895ef8
Screen Reader no
VM 100%
DESKTOP_SESSION gnome
XDG_CURRENT_DESKTOP GNOME
XDG_SESSION_DESKTOP gnome
XDG_SESSION_TYPE x11
Extensions (2)
Extension Author (truncated) Version
cpptools ms- 1.4.1
vim vsc 1.21.2
A/B Experiments 
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
pythonvspyt551:30291412
vspre833:30267464
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158cf:30286554
pythonvsuse255:30319630
vscgsv2:30305091
vscorehov:30301224
vscod805:30301674
vscextlangct:30310089
vsccppwt:30312692
@joaomoreno joaomoreno assigned bpasero and deepak1556 and unassigned joaomoreno Jun 15, 2021
@bpasero
Copy link
Member

bpasero commented Jun 15, 2021

Can you try running with --no-sandbox?

@bpasero bpasero added the info-needed Issue requires more information from poster label Jun 15, 2021
@pabtor
Copy link
Author

pabtor commented Jun 15, 2021 via email

@bpasero
Copy link
Member

bpasero commented Jun 15, 2021

Hm, can you then try code --no-sandbox --disable-gpu to see if that unblocks the UI interaction?

@pabtor
Copy link
Author

pabtor commented Jun 16, 2021 via email

@bpasero
Copy link
Member

bpasero commented Jun 16, 2021

Ok thanks.

@pabtor
Copy link
Author

pabtor commented Jun 18, 2021 via email

@deepak1556
Copy link
Collaborator

@pabtor can you paste the output of code --verbose from the RHEL 7 machine.

@pabtor
Copy link
Author

pabtor commented Jun 23, 2021 via email

@deepak1556
Copy link
Collaborator

Thanks for the logs, it helped identify the issues. There are two parts,

  1. the issue with sandbox is tracked in Linux: Unable to launch Code after upgrade to 1.57 #126019 and will be fixed in next stable release.

  2. The second issue is due to CXXABI incompatibility, this is tracked Update rpm dependencies file for newer CXXABI requirement #115784. Please follow that issue for updates. Thanks!

@deepak1556 deepak1556 added *duplicate Issue identified as a duplicate of another issue(s) and removed info-needed Issue requires more information from poster labels Jun 23, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Aug 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bpasero bpasero

@deepak1556 deepak1556

Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@joaomoreno @bpasero @deepak1556 @pabtor