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

anonymous user: Long time RStudio fan, but on my new macbook pro 2017 computer there is a typing lag when rstudio is on the native display. If I move rstudio to a lower resolution display the lag goes away. I am using the RStudio Mac daily build and the lag is present in console, rmarkdown scripts, and r scripts. I appreciate any advice on how to fix this. Thank you

also: https://support.rstudio.com/hc/en-us/community/posts/115009090288-Keyboard-typing-lag-on-macOS-High-Sierra

There seems to be a good amount of typing lag after I upgraded to High Sierra. (Almost as bad as Spyder right now, which is pretty noticeable.) I tried with the latest daily RStudio and same problem remains.

System details

RStudio Edition : Desktop
RStudio Version : 1.2.1049
OS Version      : Windows 10 Pro
R Version       : 3.5.1

Steps to reproduce the problem

• Save a Rmd notebook

Describe the problem in detail

I'm getting this error randomly when I save a .Rmd file with notebook format output.

 Attempting to reconstruct a stack trace...

   Frame	Code address
 * 0x521daf0	0x3b31926 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3731926
 * 0x521daf8	0x7ffb8e4600f0 C:\WINDOWS\System32\IMM32.DLL+0xf0
 * 0x521db00	0x521de60
 * 0x521db70	0x7ffb8ec54571 C:\WINDOWS\SYSTEM32\ntdll.dll+0x34571
 * 0x521db78	0x75c6011
 * 0x521db80	0x1
 * 0x521db88	0x43
 * 0x521db90	0x7539430
 * 0x521db98	0x55
 * 0x521dba0	0x7567308
 * 0x521dba8	0x75f12e1
 * 0x521dbb0	0x75940d0
 * 0x521dbb8	0x75940ea
 * 0x521dbc0	0x7756038
 * 0x521dbc8	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dbd0	0x3e87e98 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3a87e98
 * 0x521dbd8	0x7518f38
 * 0x521dbe0	0x3d6a75c C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x396a75c
 * 0x521dbe8	0x7754a7d
 * 0x521dbf0	0x44d47ca C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x40d47ca
 * 0x521dbf8	0x454f519 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x414f519
 * 0x521dc00	0x3d541e0 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x39541e0
 * 0x521dc08	0x7519128
 * 0x521dc10	0x4643851 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243851
 * 0x521dc18	0x3d541d1 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x39541d1
 * 0x521dc20	0x454f519 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x414f519
 * 0x521dc28	0x3d541c1 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x39541c1
 * 0x521dc30	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dc38	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dc40	0x3e7a34a C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3a7a34a
 * 0x521dc48	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dc50	0x454f519 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x414f519
 * 0x521dc58	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dc60	0x4643821 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4243821
 * 0x521dc68	0x3d6a73b C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x396a73b

   ... (maximum recursion depth reached.) 

Describe the behavior you expected

I spect to get a html preview when I save the file

Sorry for not having a reprex ready, but despite multiple other Stan users reporting similar behaviour in both the discourse forum and on the Stan slack, I'm having trouble making this happen in a reproducible way.

For me, I'm running RStudio 1.4.1106 with R 4.0.3 on Ubuntu 20.04.2, and I have RStan 2.21.2 installed though I don't use it and instead use CmdStanR 0.3.0.9000.

Any tips for working out what's going on?

System details

RStudio Edition : Desktop [Open Source]
RStudio Version : 1.2.1335
OS Version      : Windows 10 x64 (build 17763)
R Version       : R version 3.5.3 Patched (2019-03-11 r76275)

Steps to reproduce the problem

Create an R project that doesn't use C++ / Rcpp, create a new C++ file, and then save that outside of the project directory. Ensure it has the contents:

#include <Rcpp.h>
using namespace Rcpp;

// [[Rcpp::export]]
NumericVector test(NumericVector x) {
  x.
}

Try e.g. requesting autocompletion results after x..

Describe the problem in detail

Diagnostics + autocompletion features fail to work.

Describe the behavior you expected

These features should work without issue.

Notes

The issue appears to arise because we use the DESCRIPTION's LinkingTo entry to figure out what packages should be used when searching for headers, but when that entry is blank / missing we don't look for e.g. Rcpp.

System details

RStudio Edition : Desktop
RStudio Version : 1.3.944
OS Version      : macOS Catalina 10.15.4 
R Version       : R-devel (2020-04-18 r78249)

Steps to reproduce the problem

cl <- parallel::makeCluster(1)

Same if the number of nodes is > 1.

Describe the problem in detail

I have got a (so far) unpublished R package using MC simulations that suddenly did not work anymore. Every time when I tried to start the simulation RStudio went to 100 % CPU load and did nothing anymore. Sometimes, in particular, during the first seconds, I could press the 'stop' button to shutdown the R process. If I waited too long, I had to kill the RStudio process. I narrowed down the problem to the single code line shown above. However, plain R (in the terminal or the R GUI) does work without any problem. I did run the following combinations:

R version | R Studio (1.3.938) | R Studio (1.3.944) | R Studio (1.2.5042) ----------|-----------------|--------------------| -------------------| R-devel | FREEZE | FREEZE | FREEZE | FREEZE | R 4.0 RC | NA | FREEZE | FREEZE | R 3.6.3 | NA | OK | NA

NA: not tested.

My best guess is that this issue is related to recent changes in 'parallel' Important (and again), it works in the R terminal and the normal R GUI, so, therefore, I believe that something needs to be modified in RStudio (I might be wrong though). Side note: If I used the RStudio check and build functionality where I also test examples, RStudio works fine.

Update 2020-04-24

I realised that FREEZE is probably not correct, the default timeout for the connection between master and worker in parallel::makeCluster() is two minutes. If you wait the full time, R will throw the following error message :

> cl <- parallel::makeCluster(2)
Error in makePSOCKcluster(names = spec, ...) : 
  Cluster setup failed. 2 of 2 workers failed to connect.

Describe the behaviour you expected

Calling

cl <- parallel::makeCluster(1)

does not freeze RStudio or fails with the mentioned error message.

Update 2020-04-26, potential intermediate work-around

Since I had to continue testing with R 4.X and I wanted to use RStudio*, I played a little bit with the parameters, and (at least on my machine), I figured out the following:

If I use the parameter setup_timeout and set it to < 1 s, it still works. Example:

cl <- parallel::makeCluster(10, setup_timeout = 0.5)

I tested up to 100 nodes, without any problem. Obviously this is not a fix, and it may be different on other machines (not to mention that one may want to have these longer timeouts). However, it may provide an intermediate solution until a fix can be provided. Values > 1 s consistently did not work for me, according to the manual entry for parallel::makeCluster the default is 2 min.

• [X] I have read the guide to submitting good bug reports at https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports .
• [X] I have installed the latest version of RStudio and confirmed that the issue still persists.
• [ ] If I am reporting a RStudio crash, I have included a diagnostics report. https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report Not applicable, it does not really crash.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

System details

RStudio Edition : Desktop
RStudio Version : 1.2.1013 
OS Version      : Windows 10
R Version       : 3.5.1

Steps to reproduce the problem

On a windows machine with R 3.5.1,

• install Rtools in C:/Rbuildtools. This is the path by default where the installer install Rtools. The installer is the one that you get when your are inside Rstudio and pkgbuild::has_build_tools() does not find Rtools. If you get the one on CRAN, it opens a box where you can choose where to install Rtools (by default C:/Rtools) - I do not know why the two installers are different.

• Add to the PATH on the system C:\RBuildTools\3.5\bin & C:\RBuildTools\3.5\mingw_64\bin.

After that in RStudio, when trying to install from source with devtools, RStudio IDE do not find Rtools and open a box to offer to download Rtools, even if I already have it.

Describe the problem in detail

When trying to use any devtools function (i.e load_all) that need Rtools, I get the message to download unless I use first

pkgbuild::find_rtools(debug = TRUE)
#> Scanning R CMD config CC...
#> cc_path: c:/Rtools/mingw_64/bin/gcc 
#> 'c:/Rtools/mingw_64/bin/gcc.exe' does not exist
#> Scanning path...
#> ls: C:\RBuildTools\3.5\bin\ls.exe 
#> gcc_path: C:\RBuildTools\3.5\mingw_64\bin\gcc.exe 
#> VERSION.txt
#> Rtools version 3.5.0.4 
#> Version: 3.5 
#> Found compatible gcc on path
#> [1] TRUE

After that, everything works find with devtools.

I think I get the message because .Call("rs_canBuildCpp") returns FALSE. I think this function is not checking the PATH environment variable.

If I uninstall Rtools, get the installer directly from CRAN, double click on it and install Rtools in C:/Rtools, configure PATH with new paths, oddly everything is working now.

• .Call("rs_canBuildCpp") returns TRUE
• pkgbuild::has_build_tools() too
• pkgbuild::find_rtools seems to correctly get the information from R CMD config CC this time

pkgbuild::find_rtools(debug = TRUE)
#> Scanning R CMD config CC...
#> cc_path: c:/Rtools/mingw_64/bin/gcc 
#> install_path: c:/Rtools 
#> VERSION.txt
#> Rtools version 3.5.0.4 
#> Found compatible gcc from R CMD config CC
#> [1] TRUE

So there seem to be something with the location where RTools is installed... 🤔

Describe the behavior you expected

As I have everything set up in my PATH, I expected to get it to work directly in RStudio without having to call pkgbuild::find_rtools

devtools::session_info()
#> - Session info ----------------------------------------------------------
#>  setting  value                       
#>  version  R version 3.5.1 (2018-07-02)
#>  os       Windows 10 x64              
#>  system   x86_64, mingw32             
#>  ui       RTerm                       
#>  language (EN)                        
#>  collate  French_France.1252          
#>  ctype    French_France.1252          
#>  tz       Europe/Paris                
#>  date     2018-09-30                  
#> 
#> - Packages --------------------------------------------------------------
#>  package     * version     date       lib source                         
#>  assertthat    0.2.0       2017-04-11 [1] CRAN (R 3.5.1)                 
#>  backports     1.1.2       2017-12-13 [1] CRAN (R 3.5.0)                 
#>  base64enc     0.1-3       2015-07-28 [1] CRAN (R 3.5.0)                 
#>  callr         3.0.0       2018-08-24 [1] CRAN (R 3.5.1)                 
#>  cli           1.0.1       2018-09-25 [1] CRAN (R 3.5.1)                 
#>  crayon        1.3.4       2017-09-16 [1] CRAN (R 3.5.1)                 
#>  desc          1.2.0       2018-09-30 [1] Github (r-lib/desc@0ae0017)    
#>  devtools      1.13.6.9000 2018-09-30 [1] Github (r-lib/devtools@9b4b6e8)
#>  digest        0.6.17      2018-09-12 [1] CRAN (R 3.5.1)                 
#>  evaluate      0.11        2018-07-17 [1] CRAN (R 3.5.1)                 
#>  fs            1.2.6       2018-08-23 [1] CRAN (R 3.5.1)                 
#>  glue          1.3.0       2018-09-16 [1] Github (tidyverse/glue@4e74901)
#>  htmltools     0.3.6       2017-04-28 [1] CRAN (R 3.5.1)                 
#>  knitr         1.20        2018-02-20 [1] CRAN (R 3.5.1)                 
#>  magrittr      1.5         2014-11-22 [1] CRAN (R 3.5.1)                 
#>  memoise       1.1.0       2017-04-21 [1] CRAN (R 3.5.1)                 
#>  pkgbuild      1.0.1.9000  2018-09-30 [1] Github (r-lib/pkgbuild@446d70c)
#>  pkgload       1.0.0       2018-07-07 [1] CRAN (R 3.5.1)                 
#>  prettyunits   1.0.2       2015-07-13 [1] CRAN (R 3.5.1)                 
#>  processx      3.2.0       2018-08-16 [1] CRAN (R 3.5.1)                 
#>  ps            1.1.0       2018-08-10 [1] CRAN (R 3.5.1)                 
#>  R6            2.2.2       2017-06-17 [1] CRAN (R 3.5.1)                 
#>  Rcpp          0.12.18     2018-07-23 [1] CRAN (R 3.5.1)                 
#>  remotes       1.1.1.9000  2018-09-30 [1] Github (r-lib/remotes@42045fc) 
#>  rlang         0.2.2       2018-08-16 [1] CRAN (R 3.5.1)                 
#>  rmarkdown     1.10        2018-06-11 [1] CRAN (R 3.5.1)                 
#>  rprojroot     1.3-2       2018-01-03 [1] CRAN (R 3.5.1)                 
#>  sessioninfo   1.1.0       2018-09-25 [1] CRAN (R 3.5.1)                 
#>  stringi       1.2.4       2018-07-20 [1] CRAN (R 3.5.1)                 
#>  stringr       1.3.1       2018-05-10 [1] CRAN (R 3.5.1)                 
#>  testthat      2.0.0       2017-12-13 [1] CRAN (R 3.5.1)                 
#>  usethis       1.4.0       2018-08-14 [1] CRAN (R 3.5.1)                 
#>  withr         2.1.2       2018-03-15 [1] CRAN (R 3.5.1)                 
#>  yaml          2.2.0       2018-07-25 [1] CRAN (R 3.5.1)                 
#> 
#> [1] C:/Users/chris/Documents/R/win-library/3.5
#> [2] C:/Program Files/R/R-3.5.1/library

Intent

Adresses #1941

Approach

Automated Tests

QA Notes

This code:

# pak::pak("r-lib/cli")
library(cli)
library(glue)

tf <- tempfile()
writeLines(c("bla bla", "yada yada yada"), tf)

port <- .rs.httpdPort()

links <- c(
  style_hyperlink('open in browser: dplyr::summarise()'   , 'https://dplyr.tidyverse.org/reference/summarise.html' ),
  style_hyperlink('open in viewer: dplyr::summarise()'    , 'https://dplyr.tidyverse.org/reference/summarise.html', c(target = "viewer" )),
  style_hyperlink('open file'                             , glue('file://{tf}')),
  style_hyperlink('open file at line 2'                   , glue('file://{tf}:2')),
  style_hyperlink('open file at line 2, column 6'         , glue('file://{tf}:2:6')),
  
  
  style_hyperlink('open help page ?stats::rnorm'          , glue("http://localhost:{port}/library/stats/html/rnorm.html")),
  style_hyperlink('open help page ?mean'                  , glue("http://localhost:{port}/library/base/html/mean.html"))
)

writeLines(links)

will produce these links in the console:

Checklist

• [ ] If this PR adds a new feature, or fixes a bug in a previously released version, it includes an entry in NEWS.md
• [ ] If this PR adds or changes UI, the updated UI meets accessibility standards
• [ ] A reviewer is assigned to this PR (if unsure who to assign, check Area Owners list)
• [ ] This PR passes all local unit tests

System details

RStudio Edition : Desktop
RStudio Version :  1.2.5042 / 1.4.285
OS Version      :  Ubuntu 20.04
R Version       :  4.0.0 (2020-04-24)

Steps to reproduce the problem

1. Upgrade from Ubuntu 19.10 to 20.04

2. Install RStudio

apt update
apt install gdebi-core
apt install r-base r-base-dev
wget https://download1.rstudio.org/desktop/bionic/amd64/rstudio-1.2.5042-amd64.deb
gdebi https://download1.rstudio.org/desktop/bionic/amd64/rstudio-1.2.5042-amd64.deb
rstudio

I tried latest stable + latest daily build

Describe the problem in detail

RStudio starts but freezes with white background

Error message:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
Received signal 11 SEGV_MAPERR 0000000000e6

Describe the behavior you expected

RStudio starts normally without freezing

Issue seems related to #6723, #6379, #6727

• [ x] I have read the guide to submitting good bug reports at https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports .
• [ x] I have installed the latest version of RStudio and confirmed that the issue still persists.
• [ ] If I am reporting a RStudio crash, I have included a diagnostics report. https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report
• [ x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

System details

RStudio Edition : Desktop
RStudio Version : 1.2.1206
OS Version      : Windows 10 Pro
R Version       : 3.5.1

Steps to reproduce the problem

• Save a Rmd notebook

Describe the problem in detail

Since you update to pandoc 2.5 64bit I'm getting this error again, is exactly the same error of this closed issue #3661

Access violation in generated code when executing data at 0x49f9259

 Attempting to reconstruct a stack trace...

   Frame	Code address
 * 0x561daf0	0x49f9259 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f9259
 * 0x561daf8	0x7ffc358300f0 C:\WINDOWS\System32\IMM32.DLL+0xf0
 * 0x561db00	0x561de60
 * 0x561db70	0x7ffc35afbaa1 C:\WINDOWS\SYSTEM32\ntdll.dll+0x3baa1
 * 0x561db78	0x7974b61
 * 0x561db80	0x1
 * 0x561db88	0x43
 * 0x561db90	0x79513d0
 * 0x561db98	0x33
 * 0x561dba0	0x7977318
 * 0x561dba8	0x79eda49
 * 0x561dbb0	0x79d70d0
 * 0x561dbb8	0x79d70ea
 * 0x561dbc0	0x7bc5220
 * 0x561dbc8	0x49f8661 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f8661
 * 0x561dbd0	0x40e5b88 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3ce5b88
 * 0x561dbd8	0x7929670
 * 0x561dbe0	0x7929639
 * 0x561dbe8	0x488920a C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x448920a
 * 0x561dbf0	0x488920a C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x448920a
 * 0x561dbf8	0x40e5b68 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3ce5b68
 * 0x561dc00	0x488920a C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x448920a
 * 0x561dc08	0x79297b8
 * 0x561dc10	0x7925fbb
 * 0x561dc18	0x79122a0
 * 0x561dc20	0x79122b8
 * 0x561dc28	0x79122d0
 * 0x561dc30	0x49f8661 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f8661
 * 0x561dc38	0x40d800a C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3cd800a
 * 0x561dc40	0x49f8661 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f8661
 * 0x561dc48	0x4904359 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x4504359
 * 0x561dc50	0x49f8661 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f8661
 * 0x561dc58	0x49f8661 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x45f8661
 * 0x561dc60	0x40536d3 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3c536d3
 * 0x561dc68	0x4126b69 C:\PROGRA~1\RStudio\bin\pandoc\pandoc.exe+0x3d26b69

   ... (maximum recursion depth reached.) 

Describe the behavior you expected

I spect to get a html preview when I save the file

Another feature request (hence lack of system info), this one is for global search and replace functionality, perhaps implemented in the Window that pops-up when you press Ctrl-Shift-F. I opened this a while back on the old feature request site: https://support.rstudio.com/hc/en-us/community/posts/205333518-Global-search-and-replace

System details

RStudio Edition : Desktop
RStudio Version : 2022.12.0+353
OS Version      : macOS Ventura 13.1

R version: 4.2.2 (2022-10-31) Platform: aarch64-apple-darwin20 (64-bit)

Steps to reproduce the problem

Knitting any PDF causes this error, because the pandoc built in with latest Rstudio is incompatible with MAC OS: 13.1 Macbook Air M2

Describe the problem in detail

Looks like the pandoc built in with latest Rstudio is incompatible with MAC OS: 13.1 Macbook Air M2

I get this error:

sh: /Applications/RStudio.app/Contents/Resources/app/quarto/bin/tools/pandoc: Bad CPU type in executable

Error in strsplit(info, "\n")[[1]] : subscript out of bounds In addition: Warning message: In system(paste(shQuote(path), "--version"), intern = TRUE) : running command ''/Applications/RStudio.app/Contents/Resources/app/quarto/bin/tools/pandoc' --version' had status 126

Describe the behavior you expected

the PDF should be generated

Note: I then installed pandoc using brew. And when I used that pandoc, by setting the env variable RSTUDIO_PANDOC, things worked fine

• [x] I have read the guide for submitting good bug reports.
• [x] 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.
• [ x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

I've been having an issue for a little while on the daily builds where Control + . to "go to function" isn't finding my function definitions. This has been particularly annoying with C functions, like in vctrs.

Note that s3_find_method() exists both at the R and C level. It used to always find both. I'm not sure if the fact that they share the same name has anything to do with it.

RStudio 2022.12.0+353 "Elsbeth Geranium" Release (7d165dcfc1b6d300eb247738db2c7076234f6ef0, 2022-12-03) for macOS Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) RStudio/2022.12.0+353 Chrome/102.0.5005.167 Electron/19.1.3 Safari/537.36

System details

RStudio Edition : Desktop
RStudio Version : 2022.12.0,353
OS Version      : macOS 13.1
R Version       : 4.2.2

Steps to reproduce the problem

Just open RStudio and ~/.local/share/rstudiowill be created.

Describe the problem in detail

According to the documentation RStudio supposedly respects XDG_DATA_HOME which is set to ~/.config/local/share, so it seems that there is a bug.

Describe the behavior you expected

Instead of writing session data to ~/.local/share/rstudio, it should be written to ~/.config/local/share/rstudio.

• [x] I have read the guide for submitting good bug reports.
• [x] 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.
• [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

When I do Alt+LeftMouseButton+DragVertically a text block is selected but can not be copied/cut/pasted.
Backspace and Delete keys also do not work.

RStudio 2022.12.0+353 "Elsbeth Geranium" Release (, 2022-12-03) for Windows Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) RStudio/2022.12.0+353 Chrome/102.0.5005.167 Electron/19.1.3 Safari/537.36

R Session Startup Failure Report

RStudio Version

RStudio 2022.12.0+353 "Elsbeth Geranium " (7d165dcf, 2022-12-03) for Ubuntu Bionic

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) rstudio/2022.12.0+353 Chrome/102.0.5005.167 Electron/19.1.3 Safari/537.36

Error message

[No error available]

Process Output

The R session exited with code 127.

Error output:

/usr/lib/rstudio/resources/app/bin/rsession: error while loading shared libraries: libR.so: cannot open shared object file: No such file or directory

Standard output:

[No output emitted]

Logs

/home/gdevenyi/.local/share/rstudio/log/rsession-gdevenyi.log

rstudio-0.js#-1::eval
Client-ID: 33e600bb-c1b1-46bf-b562-ab5cba070b0e
User-Agent: Mozilla/5.0 (X11  Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.12.8 Chrome/69.0.3497.128 Safari/537.36

System details

RStudio Edition : Desktop
RStudio Version : 2022.12.0 Build 353
OS Version      : Manjaro ( Kernel: 6.1.1)
R Version       :  4.2.2.

Steps to reproduce the problem

Start Rstudio and eyes start to leak.

Describe the problem in detail

1. Font smoothing. Something terrible has happened with font rendering in the 2022.12.0! Fonts now blurred and absolutely unclear! Editor fonts suffered the most, font in the help pages and menus happily are still readable. Setting Options >> Appearance >> Text rendering does not change anything. What happened? how to fix?

2. Socket file. Now (after update to 2022.12 a 0 kb socket file named "rstudio" creates on the desktop or in the project folder at Rstudio startup. What is it? Why it creates?