| Git Clone URL: | https://aur.archlinux.org/rstudio-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | rstudio-desktop |
| Description: | A powerful and productive integrated development environment (IDE) for R programming language |
| Upstream URL: | https://github.com/rstudio/rstudio |
| Licenses: | AGPL-3.0-only |
| Conflicts: | rstudio-desktop |
| Provides: | rstudio-desktop |
| Submitter: | None |
| Maintainer: | xiota |
| Last Packager: | xiota |
| Votes: | 73 |
| Popularity: | 0.052003 |
| First Submitted: | 2011-03-04 15:02 (UTC) |
| Last Updated: | 2024-11-11 05:37 (UTC) |
@ith140 Is this the same issue as you mentioned before? And you've rebuilt with the latest available PKGBUILD?
I wonder if related to GPU availability. Another possibility is difference between native processor and VM instruction sets. (Are you building inside VM? Or outside VM, possibly on a different machine?)
I'll look in extra/code for anything useful.
@xiota,
This used to work for me on this system, but no longer with a recent update. (VS) Code works for me with electron32. The ubuntu 24 tarball will start fine for me with some errors, but no segfaults. The AUR packaged version segfaults after exiting GPU process line.
[14421:1107/121546.666322:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)]. [14421:1107/121546.669913:ERROR:viz_main_impl.cc(198)] Exiting GPU process due to errors during initialization [14477:1107/121547.972637:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)]. [14477:1107/121547.974757:ERROR:viz_main_impl.cc(198)] Exiting GPU process due to errors during initialization [14499:1107/121548.327250:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)]. [14499:1107/121548.343768:ERROR:viz_main_impl.cc(198)] Exiting GPU process due to errors during initialization [14462:1107/121548.602198:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [14490:1107/121548.612550:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
I'm running Arch in a VM, and my host is: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz 2.30 GHz 64 GB wayland (KDE)
Recent changes:
~/.config/rstudio-flags.conf.aur/nvm to avoid incompatible nodejs versions.The build failed for me with nodejs 23.1, can anyone confirm? I reverted to 22.X via the Arch Linux Archive, and this fixed it.
@ith140 Please check whether the Ubuntu 24 tarball at rstudio downloads has the same problem.
Please provide some system details (CPU, GPU, X11 vs wayland, etc).
Have you had similar problems with other Electron apps?
@xiota,
I tried the launcher and the snippet from @dr_evo, but it still isn't fully compatible (at least with my system as I receive a GLES version 3 being greater than the max supported by my system (2.0)).
I couldn't find anything on how to lower the GLES...
@dr_evo I'll add support to read options from ~/.config/rstudio-flags.conf. I will probably reference your repo as a list of potentially useful flags. Will take a little while because I have a backlog of other packages to update.
@xiota I've done some research and added some comments to my script, you can check it out ( https://github.com/ozankiratli/dotfiles/blob/master/.config/sway/scripts/rstudio-wayland ). A secondary launcher might be a good idea to help people using Wayland (I think chromium and electron have no intention of addressing this soon). I think it would be better if the switches could be read from a user-defined file in the .config folder. This is only a workaround, so the switches needed might differ for different system configurations.
@ith140 Try: # RSTUDIO_QUERY_FONTS=0 rstudio
@dr_evo Don't worry. I'll avoid breaking X11. Would add your script as a secondary launcher rstudio-wayland, or make a new script that reads user-defined options from another file.
Pinned Comments
trap000d commented on 2024-05-16 21:42 (UTC) (edited on 2024-05-28 20:09 (UTC) by trap000d)
A note for users.
This package is quite complex. It MAY not be built because of OTHER issues. I always build, install and test it on at least two different machines. Only after that I would push a new version to AUR.
Please try some generic solutions before reporting of build problems:
1) Update all other packages (sudo pacman -Syu),
2) Clean up yay and/or makepkg caches ('yay -Sc', 'rm -rf /var/tmp/makepkg'),
3) Be sure you've got enough RAM (8 GB or more is highly recommended) and space on disk (at least 3 GB).
4) Is your Internet connection is stable, fast and not blocked somewhere?
trap000d commented on 2022-07-05 20:32 (UTC) (edited on 2022-10-03 06:28 (UTC) by trap000d)
PLEASE READ THIS MESSAGE BEFORE COMPLAINING FOR LIBBOOST
When boost is updated to a new version and you see an error message about missing libboost*.so, you will need to rebuild and reinstall the rstudio-desktop package.
trap000d commented on 2022-02-19 06:20 (UTC) (edited on 2022-02-19 06:21 (UTC) by trap000d)
Build logic is slightly changed due to changes in upstream. As they've introduced new project format (quarto), it contradicted with standard Arch package base. In brief, quarto contains pandoc as part of itself, so it's pretty hard to keep together system pandoc and embedded quarto.
So I've "resolved" it such way: if there is "quarto*" package installed, then rstudio-desktop will pick it up and use. Otherwise (not installed), quarto support in rstudio will be disabled.
'quarto' is added as optional dependency.