Errors running RStudio under CentOS7 with and without --no-sandbox option

[katgit]

System details

RStudio Edition : Desktop
RStudio Version : 2022.12.0-353
OS Version      : CentOS7
R Version       : 4.2.1

Steps to reproduce the problem

rstudio --no-sandbox

Describe the problem in detail

With the newest installation we cannot start rstudio executable.
We get the following error:
[228737:1220/214141.389595:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /share/pkg.7/rstudio/2022.12.0-353/install/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

The only way we can start rstudio is using --no-sandbox option:
rstudio --no-sandbox.

In this case RStudio starts, however we get many errors on the background:
[15705:1220/213826.144383:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[15705:1220/213826.144467:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[15737:1220/213826.225750:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is desktop, ANGLE is
[15737:1220/213826.255945:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[15705:1220/213826.512168:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[15705:1220/213826.533181:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(node:15705) electron: Failed to load URL: http://127.0.0.1:41541/ with error: ERR_CONNECTION_REFUSED
(Use rstudio --trace-warnings ... to show where the warning was created)
[15705:1220/213830.681837:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[15705:1220/213833.414895:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

Describe the behavior you expected

We would like to see if there is a way to start rstudio without error messages

• I have read the guide for submitting good bug reports.
• I have installed the latest version of RStudio, and confirmed that the issue still persists.
• If I am reporting an RStudio crash, I have included a diagnostics report.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

[ronblum]

@katgit Thank you for raising the issue! I'm able to run on CentOS 7 without having to use the --no-sandbox option. I'll try out with the option. When you use it, does RStudio work, despite the errors?

Ref: There's an open issue for WSL and Electron regarding this error, so it might be similar.

[ronblum]

I can now reproduce the issue, which is surprising, because according to my records this is an identical environment to one that worked successfully for me a couple of weeks ago.

Here's what I get with CentOS 7.9 and R 3.3.3 and R 4.2.1:

As a regular user
Without options: Fails to run

[vmware@localhost ~]$ rstudio
[4870:1221/103616.741052:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /usr/lib/rstudio/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
[4872:0100/000000.770442:ERROR:zygote_linux.cc(650)] write: Broken pipe (32)

With --no-sandbox: Runs with minimal errors

[vmware@localhost ~]$ rstudio --no-sandbox
[5205:1221/103823.585222:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is desktop, ANGLE is
[5205:1221/103823.722340:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[5239:1221/103823.961517:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

As root
Without options: Fails to run (expected)

[root@localhost vmware]# rstudio
[1221/103850.244233:FATAL:electron_main_delegate.cc(292)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap (core dumped)

With --no-sandbox: Runs but with many errors, the ones described in the original post

[root@localhost vmware]# rstudio --no-sandbox
[5358:1221/103920.787518:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[5358:1221/103920.787924:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[5387:1221/103920.891344:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is desktop, ANGLE is
[5387:1221/103921.041522:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[5358:1221/103921.129264:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[5358:1221/103921.164387:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[5413:1221/103921.276603:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[5358:1221/103921.560543:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

[ronblum]

See issue #9854 which involves using --no-sandbox (not sure if it's related).

[katgit]

@ronblum I cannot run rstudio without "--no-sandbox" as a user. If I attempt to do it, the rstudio does not start and in addition to this the executable itself is updated and has a file size 0 after that, so I need to reinstall the software again.

With "-no-sandbox" option rstudio starts OK but I see many errors on the background and their number is increasing for various operations I perform within RStuido.

[ronblum]

What operations fail? No need to figure out all of them, just a few examples so that I can compare in my environment.

[katgit]

@ronblum
I work (and installed rstudio) on a remote server that is used by many users. Since it is a remote server, there are two ways to start a program with a GUI interface:

1. Using X-Forwarding (using ssh client and X-server)
2. Start a VNC server and open rstudio in the VNC server
   We usually recommend our users to use the second approach as it is faster.

If I open rstudio --no-sandbox within a VNC server (the second approach), I only get a couple of messages:

[20379:1222/161617.593791:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is desktop, ANGLE is 
[20379:1222/161617.634027:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Rstudio works fine No other errors appear when I use rstudio

If I start rstudio --no-sandbox in the ssh client with an X-server, then I get many copies of the same error message:

[51891:1222/162416.506045:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[51891:1222/162416.506204:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

And this message is repeated after I perform almost any operation within RStudio. It seems that it doesn't prevent rstudio to work normally. But on the background I get more and more copies of this message.

If I use an older version of rstudio (for example 2022.07.2-576), I do not get any error messages just a single info message:
TTY detected. Printing informational message about logging configuration. Logging configuration loaded from '/etc/rstudio/logging.conf'. Logging to '/usr1/scv/ktrn/.local/share/rstudio/log/rdesktop.log'.

--Katia

[cm421]

I also hit this while pulse checking for Cherry Blossom. Starting RStudio Desktop Pro 2023.03.0+385.pro2 on a fresh RHEL 7.9 install there was no feedback after trying to launch from the GUI. I had to check the system logs and saw the same error about chrome-sandbox that OP originally reported.

Following the instructions from /var/log/messages I ran sudo chmod 4755 chrome-sandbox. From there RStudio started from the GUI successfully