Comment # 4 on bug 1178041 from Nick Dordea

Hello Christophe.  
Your question---So you would prefer trusting a renderer engine that's
unmaintained upstream for years ?--- deflects software's failure .
This is that old typical/refuge .... user error . It is may fault that I dare
to use the new rkward and it crashed !

Answer :  rkward worked fine before the renderer was changed.
           so the change/enhancement affected rkward in a negative way.
           The failure is due to the new renderer, NOT the unmaintained 
           old renderer!   

I would prefer that the rkward maintenance/QA to assure software's backward
compatibility, that the new "enhanced" software does not fail .... 
in our case the failing message points to an unsolved chromium issue many years
old ....

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[27199:27199:1022/175843.788358:ERROR:zygote_host_impl_linux.cc(89)] Running as
root without --no-sandbox is not supported. See https://crbug.com/638180

What about.... that the "maintenance" considers that if root user uses the new
enhanced rkward, the new rkward starts/calls the magic new renderer with
--no-sandbox  option ? 
If that is done, the new enhanced rkward will be better that the failing actual
one.

Anyhow, your approach to rkward failure was enough to switch to rstudio .....
thanks for your "user oriented support" !

Please close this ticket mentioning that .... "as long as the new enhanced
rkward  is not used by root users, it works beautifully !"

ND