Since few days ago (I'm using the daily builds),
once I start Rkward the windows do not update their contents.
That is, I can clik on one tab (i.e., for a script), the tab becomes active, but the contents of
the window is still the contents of the previously selected tab. Also, I cannot write.
The console window is also in some cases not fully responsive.
The problem is normally solved by quiting ans starting again. The second time it usually works fine.
> sessionInfo()
R version 2.13.0 (2011-04-13)
Platform: i486-pc-linux-gnu (32-bit)
I have not managed to reproduce the problem, so far. Thus a number of questions:
once I start Rkward the windows do not update their contents.
The problem is normally solved by quiting ans starting again. The second time it usually works fine.
So, if I understand you correctly, you either get an RKWard session where window handling is broken right from the start, or an RKWard session where window handling is working. It is not a problem that appears after working in a session for a while. Correct?
Can you give a rough estimate of what percentage of RKWard sessions is affected for you?
I guess that you have set up RKWard to load an .RData file directly on startup. Perhaps the problem is related to this, somehow. If you configure RKWard not to load the .RData file on startup, but rather open it manually after startup, do you still see the problem?
That is, I can clik on one tab (i.e., for a script), the tab becomes active, but the contents of the window is still the contents of the previously selected tab. Also, I cannot write.
Is the thin red border (which indicates the active window) shown around the window?
What if you use the new Ctrl+Tab feature to switch windows (in a "broken" session) does that seem to activate the windows correctly?
Could you post the contents of the most recent /tmp/kde-USERNAME/rkwardXXXXX.tmp after a broken session?
Regards
Thomas
P.S.:
> sessionInfo()
Since a few days there is rk.sessionInfo(), which adds a few RKWard specific lines to sessionInfo().
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you give a rough estimate of what percentage of RKWard sessions is affected for you?
50%: the 1st time does not work, the 2nd one works
I guess that you have set up RKWard to load an .RData file directly on startup.
I get the options menu at startup, then select the .RData
If you configure RKWard not to load the .RData file on startup, but rather open it manually after startup, do you still see the problem?
I'll do it (several trials) today and will report back
Is the thin red border (which indicates the active window) shown around the window?
Yes, and the tabs in the menu work. But the contents of the window does not change
Could you post the contents of the most recent /tmp/kde-USERNAME/rkwardXXXXX.tmp after a broken session
I'll do it in a while
Note: the problem occurs on 2 different computers running ubuntu 10.04
and I suspect it's related to opening a large .RData file (related to memory resources?).
Do you know of a tool I could use to make a video of my starting up under linux so that you could actually sse the problem?
Many thanks for your support
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My /tmp/kde-USERNAME/rkwardXXXXX.tmp after a session with the problem
(but note that I exit normally, as the menu works fine). I select "Discard" after Exit.
alobo@delia:/tmp/kde-alobo$ cat rkwardPE6029.tmp
rkward(6029)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know ""
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
rkward(6029)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/alobo/.local/share/mime/magic"
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
QThread: Destroyed while thread is still running
QProcess: Destroyed while process is still running.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not really understand what might be the cause of this issue, yet. However, based on the symptoms, I have tried something in SVN. Please let me know, whether you see any change with tomorrow's daily build.
Perhaps, before you update, could you do two more tests with your current version for me?
1) What happens when you close one of the tabs?
2) What happens when you detach one of the windows? Does this fix the problem? Does at least the detached window behave correctly?
Regards
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it's too late for the machine at home, I had just upgraded few minutes before your message.
Now the tabs names shake like crazy until I click on any of them, but then everything works fine.
I'll try at the office tomorrow morning and will report back.
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
just to let you know: The change I made, yesterday, has not hit the daily build archive, yet. The next daily build will probably happen in around three or four hours.
BTW, one more thing: How many files do you have opened? Do all tabs fit in the tab bar, or do you get scroll-arrows on the tab bar? All script files, or others as well? (Or you could post the .rkworkplace file). One possibility is that the number of opened windows is what's causing the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Changes in the .RData file might have "solved" the problem, because (not having updated) the problem does not happen anymore on any of the 2 machines.
Of all your questions, I can only answer 3:
1) What happens when you close one of the tabs?
Nothing, no response
Do all tabs fit in the tab bar, or do you get scroll-arrows on the tab bar?
Yes, all tabs were fitting in the tab-bar
One possibility is that the number of opened windows is what's causing the problem.
I doubt it, I think I have some more help tabs opened.
I take note of the rest of your questions in case the problem appears again. I regret not having posted the .rkworkplace fiel, I should have thought on that.
Thanks for your excellent support!
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem is back.
I include an snapshot. Note that the text window on the left is selected, but part of a help page
is actually displayed: https://sites.google.com/site/filestemp2/home/rkward1.jpeg
If I detach a window, it works, but those docked do not refresh the contents.
This is still a mystery to me. Could you try the following, to try to narrow down the problem:
- Create a new R workspace, with nothing, or only few objects in it. Save it to "temp.RData", exit RKWard.
- Copy the workplace file you posted to "temp.RData.rkworkplace".
- Start RKWard and open temp.RData .
Does this trigger the same problem?
In a session that is affected: What happens when you run
rk.restore.workplace()
in the R console (in theory, this should close all windows, and re-open them)?
Which version of KDE are you using?
Regards
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I follow your directions, I get the message that I do not have access to the script file (which is not true)
script::::file:///media/Iomega_HDD/FLUXPYR/EDDY_CURS/RFLUX/flux1_log.txt
and the
help pages are not displayed (the titles are displayed, but not the contents), just the following text:
Only help files, NEWS, DESCRIPTION and files under doc/ in a package can be viewed
but I think this is an entirely different issue.
When I encounter the error (which just happened again) and run rk.restore.workplace(), the windows are closed and opened, but the problem remains.
Which KDE pakage(s) do you refer to? Note I use gnome, I have those kde packages that get installed for RKward. Most
of them 4:4.4.5-0
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Correction: If I use rk.restore.workplace() during a session in which the error is happening, the windows do not close and reopen, there is just no response (the console works).
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm afraid, I'm going to have to give up on this, soon. A few more things, before I do:
1) Could you perhaps store a backup of the affected workspace/workplace and all related files, somewhere? In case the problem goes away one day, it would be good to be able to verify whether it was actually fixed, or whether you simply no longer trigger it, then.
2) Is flux1_log.txt very large? Could there be anything else unusual about this file?
3) Suppose you copy flux1_log.txt to an internal disk, instead of a USB drive (or whatever it is), open it from there, instead, save the workplace, and restart RKWard with that? Same issue?
Regarding the errors you cite in comment #11: Yes, these are almost certainly unrelated. In case you copied the lines for the .rkworkplace-file, manually, with a text-editor, please check for any trailing or leading spaces, and make sure that there is a hard line break after each line. ATM, I can't think of any other possible source of error. This should work (I tried, here, replacing flux1_log.txt for a different file, but did not manage to reproduce the bug).
Some more loud thinking:
- You said that the workspace is very big, and suggested a memory issue. I think this is very unlikely. You would get much less confined symptoms in this case.
- Of course, a race condition comes to mind. But I can't make any sense of this, either. Only after the R workspace has been fully loaded, and all associated events have been processed, RKWard goes on with restoring the .rkworkplace. So that's guaranteed to be sequential.
- ATM, I'm suspecting a problem in KDE / Qt, rather than RKWard code, but I can't find any pointers on that, either.
Regards
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree this is difficult because it is very erratic: the same .rkworkplace-file and workspace work fine after closing (and not saving) the session in which I had the problem. It also happens with different projects, some very small (it seems to me that the fact that the problem first occurred using a very large workspace is a coincidence) and on 2 different computers.
Something I have not mentioned is that, when the problem occurs, the line numbers on the left do change if I select a different window, but not the contents of the window itself.
Hopefully the problem will be solved in a future release of KDE/Qt…
Thanks,
Agus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could this problem be caused by rattle()?
I tried rattle some time ago and I've recently observed that the package gets automatically loaded. At quiting R I get:
Warning message:
In save(list = ls(envir = .GlobalEnv, all.names = TRUE), file = outfile, :
'package:rattle' may not be available when loading
BTW, I just had a crash, this is the debuging info:
Thread 3 (Thread 0x7f7f91d09700 (LWP 3291)):
#0 0x00007f7fa54ed16e in ?? () from /lib64/libc.so.6
#1 0x00007f7fa54763dc in ?? () from /lib64/libc.so.6
#2 0x00007f7fa5474e78 in free () from /lib64/libc.so.6
#3 0x00007f7fa20831ba in ?? () from /lib64/libglib-2.0.so.0
#4 0x00007f7fa6f74013 in QEventDispatcherGlib::~QEventDispatcherGlib() () from /usr/lib64/libQtCore.so.4
#5 0x00007f7fa6e55364 in ?? () from /usr/lib64/libQtCore.so.4
#6 0x00007f7fa6e5577d in ?? () from /usr/lib64/libQtCore.so.4
#7 0x00007f7fa6bc59ca in start_thread () from /lib64/libpthread.so.0
#8 0x00007f7fa54dd70d in clone () from /lib64/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f7f912f2700 (LWP 3304)):
#5 0x00007f7fa542aa75 in raise () from /lib64/libc.so.6
#6 0x00007f7fa542e5c0 in abort () from /lib64/libc.so.6
#7 0x00007f7fa54644fb in ?? () from /lib64/libc.so.6
#8 0x00007f7fa546e5b6 in ?? () from /lib64/libc.so.6
#9 0x00007f7fa5474e83 in free () from /lib64/libc.so.6
#10 0x00007f7fa6f5fb26 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#11 0x00007f7fa6f64085 in QSocketNotifier::~QSocketNotifier() () from /usr/lib64/libQtCore.so.4
#12 0x00007f7fa6ee4bda in ?? () from /usr/lib64/libQtCore.so.4
#13 0x00007f7fa6ee9933 in ?? () from /usr/lib64/libQtCore.so.4
#14 0x00007f7fa6f25037 in ?? () from /usr/lib64/libQtCore.so.4
#15 0x00007f7fa6ee486a in QProcess::waitForFinished(int) () from /usr/lib64/libQtCore.so.4
#16 0x000000000052be2e in _start ()
Thread 1 (Thread 0x7f7faad7f760 (LWP 3284)):
#0 0x00007f7fa54ed16e in ?? () from /lib64/libc.so.6
#1 0x00007f7fa54763dc in ?? () from /lib64/libc.so.6
#2 0x00007f7fa5474e78 in free () from /lib64/libc.so.6
#3 0x00007f7fa6f5f18b in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#4 0x00007f7fa6ee4bda in ?? () from /usr/lib64/libQtCore.so.4
#5 0x00007f7fa6ee4d62 in QProcess::~QProcess() () from /usr/lib64/libQtCore.so.4
#6 0x00007f7fa6f58a5c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4
#7 0x00007f7fa6f5fae4 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#8 0x00007f7fa6e52fd9 in QThread::~QThread() () from /usr/lib64/libQtCore.so.4
#9 0x000000000052b858 in _start ()
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-rw----- 1 alobo alobo 5623 2011-06-14 15:37 rkwardPE3284.tmp
-rw----- 1 alobo alobo 164 2011-06-14 15:37 rkward.rbackendMT3305.tmp
alobo@delia:/tmp/kde-alobo$ more rkwardPE3284.tmp
rkward(3284)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know ""
rkward(3284)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
rkward(3284)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/alobo/.local/share/mime/mag
ic"
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged
line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged
line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/windows/rkcommandeditorwindow.cpp - function tryCompletion line 545
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/windows/rkcommandeditorwindow.cpp - function tryCompletion line 545
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
8 requests for recording output still active on interface shutdown
QThread: Destroyed while thread is still running
QProcess: Destroyed while process is still running.
alobo@delia:/tmp/kde-alobo$
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not in theory. But of course, in theory, you would not see this problem. All you can do is try (i.e. detach package::rattle, before you save the workspace, next time). I have installed rattle, here, but still could not reproduce the problem, so far.
--
The crash looks like it occurred while exiting RKWard. Is that correct? Unfortunately, there is not much to be seen from the backtrace, beyond that. Let me know, if you see this more often, though.
--
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/windows/rkcommandeditorwindow.cpp - function tryCompletion line 545
Ok, I've just fixed these. They were harmless, though.
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged line 85
This still needs fixing, but I am fairly sure that it is also harmless.
Regards
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since few days ago (I'm using the daily builds),
once I start Rkward the windows do not update their contents.
That is, I can clik on one tab (i.e., for a script), the tab becomes active, but the contents of
the window is still the contents of the previously selected tab. Also, I cannot write.
The console window is also in some cases not fully responsive.
The problem is normally solved by quiting ans starting again. The second time it usually works fine.
> sessionInfo()
R version 2.13.0 (2011-04-13)
Platform: i486-pc-linux-gnu (32-bit)
locale:
LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8
attached base packages:
grid stats graphics grDevices utils datasets methods base
other attached packages:
raster_1.8-15 sp_0.9-72 reshape_0.8.3 plyr_1.2.1 proto_0.3-8 rkward_0.5.6
loaded via a namespace (and not attached):
ggplot2_0.8.8 lattice_0.19-26 tools_2.13.0
>
Agus
Hi!
I have not managed to reproduce the problem, so far. Thus a number of questions:
So, if I understand you correctly, you either get an RKWard session where window handling is broken right from the start, or an RKWard session where window handling is working. It is not a problem that appears after working in a session for a while. Correct?
Can you give a rough estimate of what percentage of RKWard sessions is affected for you?
I guess that you have set up RKWard to load an .RData file directly on startup. Perhaps the problem is related to this, somehow. If you configure RKWard not to load the .RData file on startup, but rather open it manually after startup, do you still see the problem?
Is the thin red border (which indicates the active window) shown around the window?
What if you use the new Ctrl+Tab feature to switch windows (in a "broken" session) does that seem to activate the windows correctly?
Could you post the contents of the most recent /tmp/kde-USERNAME/rkwardXXXXX.tmp after a broken session?
Regards
Thomas
P.S.:
Since a few days there is rk.sessionInfo(), which adds a few RKWard specific lines to sessionInfo().
50%: the 1st time does not work, the 2nd one works
I get the options menu at startup, then select the .RData
I'll do it (several trials) today and will report back
Yes, and the tabs in the menu work. But the contents of the window does not change
I'll do it in a while
Note: the problem occurs on 2 different computers running ubuntu 10.04
and I suspect it's related to opening a large .RData file (related to memory resources?).
Do you know of a tool I could use to make a video of my starting up under linux so that you could actually sse the problem?
Many thanks for your support
Agus
My /tmp/kde-USERNAME/rkwardXXXXX.tmp after a session with the problem
(but note that I exit normally, as the menu works fine). I select "Discard" after Exit.
alobo@delia:/tmp/kde-alobo$ cat rkwardPE6029.tmp
rkward(6029)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know ""
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
rkward(6029)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/alobo/.local/share/mime/magic"
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
rkward(6029)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "khtml_part_widget" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rktoolwindowbar.cpp - function addWidget line 134
Assert failed at /build/buildd/rkward-0.5.5.z+0.5.6/rkward/windows/rkworkplace.cpp - function restoreWorkplace line 653
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
rkward(6029)/Kate (Code Completion) KateCompletionWidget::startCompletion: No active window to install event filter on!!
QThread: Destroyed while thread is still running
QProcess: Destroyed while process is still running.
Hi!
I do not really understand what might be the cause of this issue, yet. However, based on the symptoms, I have tried something in SVN. Please let me know, whether you see any change with tomorrow's daily build.
Perhaps, before you update, could you do two more tests with your current version for me?
1) What happens when you close one of the tabs?
2) What happens when you detach one of the windows? Does this fix the problem? Does at least the detached window behave correctly?
Regards
Thomas
I think it's too late for the machine at home, I had just upgraded few minutes before your message.
Now the tabs names shake like crazy until I click on any of them, but then everything works fine.
I'll try at the office tomorrow morning and will report back.
Agus
just to let you know: The change I made, yesterday, has not hit the daily build archive, yet. The next daily build will probably happen in around three or four hours.
BTW, one more thing: How many files do you have opened? Do all tabs fit in the tab bar, or do you get scroll-arrows on the tab bar? All script files, or others as well? (Or you could post the .rkworkplace file). One possibility is that the number of opened windows is what's causing the problem.
Changes in the .RData file might have "solved" the problem, because (not having updated) the problem does not happen anymore on any of the 2 machines.
Of all your questions, I can only answer 3:
Nothing, no response
Yes, all tabs were fitting in the tab-bar
I doubt it, I think I have some more help tabs opened.
I take note of the rest of your questions in case the problem appears again. I regret not having posted the .rkworkplace fiel, I should have thought on that.
Thanks for your excellent support!
Agus
The problem is back.
I include an snapshot. Note that the text window on the left is selected, but part of a help page
is actually displayed:
https://sites.google.com/site/filestemp2/home/rkward1.jpeg
If I detach a window, it works, but those docked do not refresh the contents.
My .rkworkplace file:
base::::file:///media/Iomega_HDD/FLUXPYR/EDDY_CURS/RFLUX
script::::file:///media/Iomega_HDD/FLUXPYR/EDDY_CURS/RFLUX/flux1_log.txt
help::::rkward://rhelpbase/library/stats/html/ts.html
help::::rkward://rhelpbase/library/zoo/doc/index.html
help::::rkward://rhelpbase/library/zoo/html/aggregate.zoo.html
help::::rkward://rhelpbase/library/base/help/as.POSIXct
help::::rkward://rhelpbase/library/raster/html/cluster.html
help::::rkward://rhelpbase/library/zoo/html/yearmon.html
workspace::sidebar,0::
commandlog::sidebar,3::
filebrowser::sidebar,0::
pendingjobs::sidebar,4::
console::sidebar,3::
helpsearch::sidebar,3::
> sessionInfo()
R version 2.13.0 (2011-04-13)
Platform: i486-pc-linux-gnu (32-bit)
locale:
LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8
attached base packages:
stats graphics grDevices utils datasets methods base
other attached packages:
rkward_0.5.6
loaded via a namespace (and not attached):
tools_2.13.0
Agus
Hi!
This is still a mystery to me. Could you try the following, to try to narrow down the problem:
- Create a new R workspace, with nothing, or only few objects in it. Save it to "temp.RData", exit RKWard.
- Copy the workplace file you posted to "temp.RData.rkworkplace".
- Start RKWard and open temp.RData .
Does this trigger the same problem?
In a session that is affected: What happens when you run
in the R console (in theory, this should close all windows, and re-open them)?
Which version of KDE are you using?
Regards
Thomas
When I follow your directions, I get the message that I do not have access to the script file (which is not true)
script::::file:///media/Iomega_HDD/FLUXPYR/EDDY_CURS/RFLUX/flux1_log.txt
and the
help pages are not displayed (the titles are displayed, but not the contents), just the following text:
Only help files, NEWS, DESCRIPTION and files under doc/ in a package can be viewed
but I think this is an entirely different issue.
When I encounter the error (which just happened again) and run rk.restore.workplace(), the windows are closed and opened, but the problem remains.
Which KDE pakage(s) do you refer to? Note I use gnome, I have those kde packages that get installed for RKward. Most
of them 4:4.4.5-0
Agus
Correction: If I use rk.restore.workplace() during a session in which the error is happening, the windows do not close and reopen, there is just no response (the console works).
Agus
Hi!
I'm afraid, I'm going to have to give up on this, soon. A few more things, before I do:
1) Could you perhaps store a backup of the affected workspace/workplace and all related files, somewhere? In case the problem goes away one day, it would be good to be able to verify whether it was actually fixed, or whether you simply no longer trigger it, then.
2) Is flux1_log.txt very large? Could there be anything else unusual about this file?
3) Suppose you copy flux1_log.txt to an internal disk, instead of a USB drive (or whatever it is), open it from there, instead, save the workplace, and restart RKWard with that? Same issue?
Regarding the errors you cite in comment #11: Yes, these are almost certainly unrelated. In case you copied the lines for the .rkworkplace-file, manually, with a text-editor, please check for any trailing or leading spaces, and make sure that there is a hard line break after each line. ATM, I can't think of any other possible source of error. This should work (I tried, here, replacing flux1_log.txt for a different file, but did not manage to reproduce the bug).
Some more loud thinking:
- You said that the workspace is very big, and suggested a memory issue. I think this is very unlikely. You would get much less confined symptoms in this case.
- Of course, a race condition comes to mind. But I can't make any sense of this, either. Only after the R workspace has been fully loaded, and all associated events have been processed, RKWard goes on with restoring the .rkworkplace. So that's guaranteed to be sequential.
- ATM, I'm suspecting a problem in KDE / Qt, rather than RKWard code, but I can't find any pointers on that, either.
Regards
Thomas
I agree this is difficult because it is very erratic: the same .rkworkplace-file and workspace work fine after closing (and not saving) the session in which I had the problem. It also happens with different projects, some very small (it seems to me that the fact that the problem first occurred using a very large workspace is a coincidence) and on 2 different computers.
Something I have not mentioned is that, when the problem occurs, the line numbers on the left do change if I select a different window, but not the contents of the window itself.
Hopefully the problem will be solved in a future release of KDE/Qt…
Thanks,
Agus
Could this problem be caused by rattle()?
I tried rattle some time ago and I've recently observed that the package gets automatically loaded. At quiting R I get:
Warning message:
In save(list = ls(envir = .GlobalEnv, all.names = TRUE), file = outfile, :
'package:rattle' may not be available when loading
BTW, I just had a crash, this is the debuging info:
Application: RKWard (rkward.frontend), signal: Aborted
Thread 3 (Thread 0x7f7f91d09700 (LWP 3291)):
#0 0x00007f7fa54ed16e in ?? () from /lib64/libc.so.6
#1 0x00007f7fa54763dc in ?? () from /lib64/libc.so.6
#2 0x00007f7fa5474e78 in free () from /lib64/libc.so.6
#3 0x00007f7fa20831ba in ?? () from /lib64/libglib-2.0.so.0
#4 0x00007f7fa6f74013 in QEventDispatcherGlib::~QEventDispatcherGlib() () from /usr/lib64/libQtCore.so.4
#5 0x00007f7fa6e55364 in ?? () from /usr/lib64/libQtCore.so.4
#6 0x00007f7fa6e5577d in ?? () from /usr/lib64/libQtCore.so.4
#7 0x00007f7fa6bc59ca in start_thread () from /lib64/libpthread.so.0
#8 0x00007f7fa54dd70d in clone () from /lib64/libc.so.6
#9 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f7f912f2700 (LWP 3304)):
#5 0x00007f7fa542aa75 in raise () from /lib64/libc.so.6
#6 0x00007f7fa542e5c0 in abort () from /lib64/libc.so.6
#7 0x00007f7fa54644fb in ?? () from /lib64/libc.so.6
#8 0x00007f7fa546e5b6 in ?? () from /lib64/libc.so.6
#9 0x00007f7fa5474e83 in free () from /lib64/libc.so.6
#10 0x00007f7fa6f5fb26 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#11 0x00007f7fa6f64085 in QSocketNotifier::~QSocketNotifier() () from /usr/lib64/libQtCore.so.4
#12 0x00007f7fa6ee4bda in ?? () from /usr/lib64/libQtCore.so.4
#13 0x00007f7fa6ee9933 in ?? () from /usr/lib64/libQtCore.so.4
#14 0x00007f7fa6f25037 in ?? () from /usr/lib64/libQtCore.so.4
#15 0x00007f7fa6ee486a in QProcess::waitForFinished(int) () from /usr/lib64/libQtCore.so.4
#16 0x000000000052be2e in _start ()
Thread 1 (Thread 0x7f7faad7f760 (LWP 3284)):
#0 0x00007f7fa54ed16e in ?? () from /lib64/libc.so.6
#1 0x00007f7fa54763dc in ?? () from /lib64/libc.so.6
#2 0x00007f7fa5474e78 in free () from /lib64/libc.so.6
#3 0x00007f7fa6f5f18b in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#4 0x00007f7fa6ee4bda in ?? () from /usr/lib64/libQtCore.so.4
#5 0x00007f7fa6ee4d62 in QProcess::~QProcess() () from /usr/lib64/libQtCore.so.4
#6 0x00007f7fa6f58a5c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4
#7 0x00007f7fa6f5fae4 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#8 0x00007f7fa6e52fd9 in QThread::~QThread() () from /usr/lib64/libQtCore.so.4
#9 0x000000000052b858 in _start ()
Just in case this might be useful as well:
-rw----- 1 alobo alobo 5623 2011-06-14 15:37 rkwardPE3284.tmp
-rw----- 1 alobo alobo 164 2011-06-14 15:37 rkward.rbackendMT3305.tmp
alobo@delia:/tmp/kde-alobo$ more rkwardPE3284.tmp
rkward(3284)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know ""
rkward(3284)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
rkward(3284)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/alobo/.local/share/mime/mag
ic"
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName
line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged
line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged
line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/misc/rkxmlguisyncer.cpp - function uiRcFileChanged line 85
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/windows/rkcommandeditorwindow.cpp - function tryCompletion line 545
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/windows/rkcommandeditorwindow.cpp - function tryCompletion line 545
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
Assert failed at /build/buildd/rkward-0.5.6z+0.5.7/rkward/core/renvironmentobject.cpp - function packageName line 52
8 requests for recording output still active on interface shutdown
QThread: Destroyed while thread is still running
QProcess: Destroyed while process is still running.
alobo@delia:/tmp/kde-alobo$
Not in theory. But of course, in theory, you would not see this problem. All you can do is try (i.e. detach package::rattle, before you save the workspace, next time). I have installed rattle, here, but still could not reproduce the problem, so far.
--
The crash looks like it occurred while exiting RKWard. Is that correct? Unfortunately, there is not much to be seen from the backtrace, beyond that. Let me know, if you see this more often, though.
--
Ok, I've just fixed these. They were harmless, though.
This still needs fixing, but I am fairly sure that it is also harmless.
Regards
Thomas