Bug 386981 - RKWard
Summary: RKWard
Status: RESOLVED WORKSFORME
Alias: None
Product: rkward
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: RKWard Team
URL:
Keywords: triaged
: 386899 386913 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-16 10:11 UTC by Rodrigo
Modified: 2018-10-28 03:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo 2017-11-16 10:11:26 UTC
---Descrição do problema---
Por favor, preencha as informações ausentes *em inglês*.

Encontrei a mensagem de erro citada abaixo. Além disso, vi os seguintes sintomas:
###Por favor, preencha (se aplicável)###

O que fez - em detalhes - diretamente antes de encontrar este problema?
###Por favor, preencha###

Quando tentou repetir os passos acima, o problema voltou a ocorrer (não, às vezes, sempre)?
###Por favor, preencha###

Se aplicável: Ao fazer a mesma coisa em uma sessão de R fora do RKWard, ocorreu o mesmo problema?
###Por favor, preencha###

Você tem alguma informação adicional que possa nos ajudar a localizar este problema? Em particular, se aplicável, pode fornecer dados e código em R como exemplo para reproduzir este problema?
###Por favor, preencha###

O RKWard está disponível em muitas distribuições e, às vezes, os problemas são específicos para um determinado método de instalação. Como você instalou o  RKWard (quais arquivos você baixou)?
###Por favor, preencha###


---Error Message---
Código da mensagem: r_engine_has_died
Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed
A infraestrutura do R será encerrada imediatamente. Isso significa que você não poderá usar mais funções que dependam dele, ou seja, provavelmente não poderá fazer mais nada, nem mesmo salvar o espaço de trabalho (mas, se tiver sorte, o R já o fez antes). O que poderá fazer, todavia, é salvar os arquivos de comandos que estiverem abertos, o resultado ou copiar os dados das janelas de editores de dados abertas. Saia do RKWard depois disso. Pedimos desculpas!

---Session Info---
RKWard version: 0.6.4
KDE version (runtime): 4.14.16
KDE version (compile time): 4.14.13
Qt build key: x86_64 linux g++-4 full-config
Local KDE directory: /home/rodrigo/.kde/
RKWard storage directory: /home/rodrigo/.rkward/
Backend version (as known to the frontend): 3.4.1

Debug message file (this may contain relevant diagnostic output in case of trouble):
/tmp/rkward.frontend.n13094
- backend not available or rk.sessionInfo() canceled -
Comment 1 Thomas Friedrichsmeier 2017-11-16 11:09:20 UTC
Thanks for taking the time to submit this report. However, it would be _much_ more helpful, if you would try to fill in answers to the questions in the report template, rather than submitting the same report again, without context.

Anyway, I assume this is a problem while starting RKWard, and it will probably go away, if you try the most recent version of RKWard (0.6.5), when using R 3.4.x. Please try that, and report back, if problems persist.
Comment 2 Thomas Friedrichsmeier 2017-11-16 11:09:49 UTC
*** Bug 386899 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Friedrichsmeier 2017-11-16 11:10:19 UTC
*** Bug 386913 has been marked as a duplicate of this bug. ***
Comment 4 Andrew Crouthamel 2018-09-28 02:35:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-28 03:41:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!