Yes, i've tried it.
Could id be because of polish signs in location addres ("ą")? or a fact that this is my company's computer and R is istnalled locally on my profile (rstudio is at default location in program files) ?
This sounds like the problem (having "ą" in your path).
We've seen this causing problems before and seems there are still
some bugs to work out. Would you mind opening a standard R session
and telling me the output of the following commands:
I have been using R Studio for more than a year and had not much
of a problem in the past. It is indeed a very functional and well
Recently it has been very slow to boot up and all of a sudden
the error message '"R session failed to start" kept on
I am having exactly the same problems and same type of messages
mentioned in the previous discussions when I tried out the
suggestions. It keeps on giving the ERROR system error 9938
(Unknown error); OCCURRED AT: core all the time as per
I have no problem running an R session by itself and also with
I have uninstalled and re-installed R Studio a dozen times and
even with the older versions but have the same message all the
It appears that R Studio has an inconsistent and quirky approach
to start R.
I would appreciate very much if your team could resolve the core
of the problem that manifest consistently in recent months.
If you'd prefer to email me any information directly (rather
than posting to this forum), you can send it to "josh at rstudio
dot org". I'm mainly interested if you could tell me the result of
the following commands in R:
Also since using Ctrl to start RStudio does not
work, can you try the following:
1) Open the Windows Command Prompt
2) Type the following commands, making sure to point to your actual
paths. For example if you installed R to another location rather
than Program Files. Also note that you do not type the
>, this is just the command prompt:
> set R_HOME=C:\Program Files\R\R-2.12.0\
> set PATH=%PATH%;C:\Program Files\R\R-2.12.0\bin\i386
> cd "C:\Program Files\RStudio\bin"
> rsession.exe --program-mode=desktop
3) Tell me the output from there
If this fails or it tells you "rsession.exe is not recognized as
an internal or external
command, operable program or batch file", then double check all
your paths and try again.
Thanks and I got the email. Unfortunately based on the input it
looks like it is the result of the "ą" in your username and
home directory. I've updated our bug further and I'll message
another engineer to see if he has any input here.
I had Joe take a deeper look and I unfortunately I don't think
there is going to be anything we can do at the moment. I've made a
note though to ping back to this thread once we have a fix we think
will do it. Not sure on the time-frame for this though.