https://bugs.kde.org/show_bug.cgi?id=457889
Thomas Friedrichsmeier <thomas.friedrichsme...@kdemail.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thomas.friedrichsmeier@kdem
| |ail.net
--- Comment #2 from Thomas Friedrichsmeier <thomas.friedrichsme...@kdemail.net>
---
Use
QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox" rkward
to disable sandboxing.
*However*
a) R (and RKWard) allows mixing package from several local "library locations".
It's perfectly ok (and common) to have a system-wide, non-user writable library
location, and a user-controlled library location on top of that.
b) Under Linux, from the RKWard package management dialog, you can simply
select the system location (/usr/lib64/R/library). If you do not have write
access, you will be prompted to either install to a custom location (i.e. case
a), or to install using sudo. You do not need to run the whole frontend as root
for that.
As for the --debug-output option: It does not work that way. Use
"--debug-output terminal" to write output to the console. Otherwise, debug
output is written to /tmp/rkward.frontend and /tmp/rkward.rbackend.
--
You are receiving this mail because:
You are watching all bug changes.
