While typing, some of the characters will appear out of the order I typed them. For example, when I tried typing the summary above in a Writer document, this is what appeared: Whil teyping, some characesat rppear out of order oh tow the rayet yped. This does not seem to happen in Calc, only Writer. However, just to make sure, I tested a different keyboard that was working normally on another machine, and also tried other USB ports to plug the keyboards in to. In each case I have gotten the same result, only while typing in Writer.
Did the problem appear in version 5.1.2? What distro and desktop environment do you use? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
(In reply to Buovjaga from comment #1) > Did the problem appear in version 5.1.2? > What distro and desktop environment do you use? > > Set to NEEDINFO. > Change back to UNCONFIRMED after you have provided the information. I think it appeared in 5.1.2. I am running Unity in Ubuntu 15.10.
Maybe you could try this: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile It certainly seems like a unique problem as there have been no other reports.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20161207
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170131
*** Bug 117054 has been marked as a duplicate of this bug. ***
NEW per dupe. This is a pretty funky issue. If you have the chance to log in with a Wayland session, would be nice to hear if it makes the problem go away.
Also, please test with version 6.0.x. A person on IRC was able to reproduce, but not with 6.
In writer it could easily be management of the m_aInBuffer in edtwin.cxx - but on the surface it looks ok I guess. Joseph - how fast are you typing ? if you type slowly - do you get a better behavior ? (and/or is your machine slow/loaded) ? Chris suggest it is indeed performance related. If anyone can reproduce this that can build something; if they could apply this patch and test again: --- a/sw/source/uibase/docvw/edtwin.cxx +++ b/sw/source/uibase/docvw/edtwin.cxx @@ -2420,7 +2420,7 @@ KEYINPUT_CHECKTABLE_INSDEL: comphelper::string::padToLength(aBuf, m_aInBuffer.getLength() + aKeyEvent.GetRepeat() + 1, aCh); m_aInBuffer = aBuf.makeStringAndClear(); - g_bFlushCharBuffer = Application::AnyInput( VclInputFlags::KEYBOARD ); + g_bFlushCharBuffer = false; // Application::AnyInput( VclInputFlags::KEYBOARD ); bFlushBuffer = !g_bFlushCharBuffer; if( g_bFlushCharBuffer ) m_aKeyInputFlushTimer.Start(); It would be rather interesting to know if that stops the problem.
Dear Joseph, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Joseph, are you still reproducing this problem with the newest versions?
No more reports about this since 2018. Buovjaga, if no info from the reporter and the duplicate reporter, could this bug be closed?
We also have bug 139807 for automated typing causing the same effect