Arch Linux User Repository

Thanks @LuisDamiano I updated the package and made your changes. They were working on my local machine.

I also removed the sandbox hack from the .desktop file. This was something that needed to be fixed for the QT version, and no longer applies for the Electron version.

Everything seems to be running like normal on my end!

Hey @chendaniely, thanks for the update. It's very much welcome, I appreciate your working on this.

Note that /bin/rstudio-daily-bin calls exec /usr/lib/rstudio/bin/rstudio "$@". However, the binary is installed in /usr/lib/rstudio/rstudio (note that the folder and the binary files have the same name). The desktop /usr/share/applications/rstudio.desktop looks good to me.

Hi folks! Sorry it took me a while to figure out how to update this package.

But it should now update using the new electron builds now, too! Main issue was using the deb build that required openssl3 which isn't a thing on Arch yet. That caused a whole bunch of problems trying to get it installed properly and not breaking the rest of my computer. Realized that there were still builds using openssl1 (duh!)

(I can officially claim I did something for hacktoberfest now)

Edit: Just give me some time to get all the automation and stuff working again. But the hardest part is done!

I used to edit the BUILDPKG by hand and update the URL of the daily build from time to time. However, they seem to have introduced a new modification. Once the deb package is extracted using ar, the content is now in unzstd format. That involves some extra tweaking I haven't gotten to so far.

Thanks folks for bearing with me. I'm mostly all moved into the new place, just haven't set up the mini server to do the auto-updates.

BUT, I updated and modified the PKGBUILD file to add the --disable-seccomp-filter-sandbox flag into the .desktop file. I think this should fix things for the time being.

@chendaniely any chance you could include the workaround in the .desktop launcher? It seems like there won't be an official fix anytime soon.

Thanks @Alarg, confirmed that --disable-seccomp-filter-sandbox works. I'm no security expert, so I'll start using that version moving forward, and edit my comment below.

If you want I would suggest posting that message to the linked github rstudio issue. Otherwise, I'll do it on your behalf in a few days.

Hey! I've got, in my opinion, a better suggestion

Using --no-sandbox can pose some security risks. I've checked by using --disable-seccomp-filter-sandbox and this option works too, and as far as I've heard, should be much safer option. I suggest you to use this rather than --no-sandbox :)

quick fix for the --no-sandbox / --disable-seccomp-filter-sandbox issue in rstudio is to either:

1. export RSTUDIO_CHROMIUM_ARGUMENTS="--disable-seccomp-filter-sandbox" >> ~/.bashrc

2. You can also aim to modify /usr/share/applications/rstudio.desktop to include --disable-seccomp-filter-sandbox at the end of the exec section

See this GitHub comment and the one below it: https://github.com/rstudio/rstudio/issues/9854#issuecomment-1047074303

edit: used to say --no-sandbox, changed becaues of @alarg's comment above

Edit: used to say --no-sandbox but edited from @alarg's comment above

This should be fixed now! I'll be in the process of moving the next 2 weeks so the daily updates may be a bit sporadic.

Also, if you're on KDE seems like qt update will break a bunch of things. For RStudio it'll cause a blank white screen. I can also confirm this happens with the daily version of rstudio here.

From the comment by Goetz commented on 2022-02-15 19:57 (EST) in the "rstudio-desktop-bin" AUR package, the solution (for now) is to launch rstudio with the --disable-seccomp-filter-sandbox flag.

For the daily version it'll be rstudio-daily-bin --disable-seccomp-filter-sandbox