Arch Linux User Repository

I started getting this error when I launch RStudio (preview 1.2.1511 running R 3.6.0):

The R session had a fatal error.

ERROR r error 4 (R code execution error) [errormsg=Error: option error has NULL value
]; OCCURRED AT: rstudio::core::Error rstudio::r::exec::executeSafely(rstudio_boost::function<void()>) /var/lib/jenkins/workspace/IDE/open-source-pipeline/v1.2-patch/src/cpp/r/RExec.cpp:224

Edit: I fixed this issue I had to comment out these lines from my .RProfile:

#if (requireNamespace("rlang", quietly = TRUE)) {
#  options(error = rlang::entrace)
#}

please see this thread for more information: https://community.rstudio.com/t/rstudio-crash-fatal-error-link-to-rstudio-executesafely-and-jenkins/29945/5

On which flavor are you exactly? (Arch, Manjaro, etc.?) I cannot reproduce the issue and hence I cannot do anything against it. Might be worth reporting upstream at the rstudio-github repo with more OS details.

I am also victim of the black screen since last update. I tried reinstalling, it did not help... Any idea?

@aldomann

I just updated my system, I'm able to run rstudio just fine... If you tried to do a clean install? Maybe also try installing the non-preview version to see if it still happens?

I think the package needs openssl-1.0 requirement. There are potentially more requirements, but since the standard ArchLinux openssl is 1.1, this one gets exposed.

@pat-s yeah that was totally my fault. I didn't even think to check while I was away since the update cycle for the preview version used to be every Friday and significantly slowed down. The original out-of-date flag got utterly buried in my inbox. But that shouldn't happen anymore, I've switched to a different email and made it public in my AUR profile so I should be easier to ping next time.

@chendanlely I just added you as a co-maintainer. Sorry for taking ownership if you've just been on vacation. However, you did not respond for a long time and I was worried about the maintenance of this package.

As you see I just updated it with the most recent PKGBUILD from the desktop-bin package.

I was out on vacation this month.. is it possible to be a listed as a co-maintainer for this repository? I just saw the batch of emails for ownership changes today which just got me concerned and confused @_@ I also didn't see the out-of-date flag, that was my mistake.

pandoc 2.x might cause some issues with rmarkdown. See:
https://github.com/rstudio/rmarkdown/issues/1211

gstreamer0.10-base has been un-orphaned