Version: 1.7.1 (using KDE KDE 3.4.0) Installed from: Unlisted Binary Package OS: Linux Working with kile, sometimes the user interface stops to react on mouse or keyboard input. Unfortunately I dont't know how to reproduce this behaviour, it appears erratically. The program seems not to be crashed completely, for instance the cursor still blinks and the mouse-pointer changes its look depending on wether it is over the sidebar or the editor. But I haven't found a possibility to save my work and exit kile gracefully or to reactivate the program. Then I kill the process and restart kile.
I noticed this state, too. I managed to still control kile via dcop, e.g. start kdcop, open up kile -> kile -> call void closeDocument() until all docs are closed. kile even asks you if you want to save your changes, but the main window stays frozen. I am using kile 1.7b1, kde 3.4.0 (debian)
It seems to me this happens when I have been doing other stuff for a couple of minutes and I then go back to kile. I am editing my thesis, so it is quite large and includes a lot of stuff. Happens to me around 0.4 times a day using kile for about 8-9 hours a day. If you want some more info, mail me...
It would be nice if you could give me a step by step instruction of how to reproduce it. Something that always works (well, fails). best, Jeroen
Hello Jeroen, unfortunately, I'm not able to reproduce the GUI-freeze. But it happens every couple of hours while I'm working on my thesis. The hint from Ole Langbehn works well, it is possible to communicate with kile through KDCOP. Also there is no data loss - simply waiting longer than the autosafe time before killing kile saves my files. So kile is still active in a sense. I conjecture that this bug is identical with bug nr. 98871. My impression is that there is an invisible dialog box and kile is waiting for some input. If you could give me a hint how to get more information on this behavior, I would be glad to help. I'm using Debian Sarge with the KDE 3.4.1 packages from pkg-kde.alioth.debian.org best wishes, Tobias
Indeed it is a duplicate of 98871. The problem seems to be more general, either Kate or perhaps some more low level libraries. This problem occurred with Kate as well. It _could_ be that compiler optimizations screw up to Kile binary, recompiling without any optimizations could bring that to light. best, Jeroen *** This bug has been marked as a duplicate of 98871 ***
If you have this problem, try turning off autosave... I noticed that when I turn off the autosave option, kile is not showing this behavior anymore. I have been using kile without this prob for three days now. If the problem resurfaces, I will post here. But I have the feeling that autosave leads to the source of it.
This shouldn't be marked resolved, it is not. There's just a workaround, but turning autosave off cannot be considered a permanent solution
It is marked as RESOLVED:DUPLICATE. This just means that there are multiple bug report about the same problem. To keep things simple, we only keep one bug report open and refer to the others. best, Jeroen