Version: 1.9.1 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3.4) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-11-generic Hi! I have been writing a longer tex document (60 page thesis) with Kile, and I have noticed that sometimes, duplicate and missing characters appear. I.e. when I write "Hello World!", this may turn out as "Hlloo Worldd!". I am using a wired keyboard (so it should not be a problem with the Keyboard connection). This happens only infrequently, so it is hard to reproduce. I assume it might correlate with autosaves, but I am not sure. Usually when this happens, I notice some activity in the lower right corner of the kyle window (in the status bar), but I have never been fast enough to see what is actually happening. I usually have multiple tabs open. This is a fuzzy bug, and I originally didn't think it was worth reporting, since it didn't happen that often was quickly fixed. However, I am currently reviewing my document and have seen such typos in many occasions, so it happened more often than I originally realized. I hope you guys can figure this out. Feel free to ask if you need further infos. Regards, Jonas Diemer.
I have observed something similar with both 1.9.2 and 1.9.3. In my case I have only witnessed characters getting lost, and I attributed this to auto-saving. There was an old bug 82083 related to this issue, but the developers seem to have taken some relevant action. Unfortunately, it seems this is not enough, as the problem still happens.
related bugs #98871, #144418, #82083, #164959 ?
I can confirm this problem using version 2.0.3 (kde 3.5.10 release 50, openSUSE 11.0). In particular, I have noticed that it is more evident if you have the Structure sidebar opened. When the current file is autosaved, then the Structure is refreshed and if you are typing, then you loose some character.
Please check if this problem still occurs with the latest version of Kile (2.1 beta 3).
2.1 beta 3 works for me. Typed characters seem to be buffered and appear in the correct order after refreshing of the structure has completed.
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.