Description: After doing a find and replace the ability to scroll, either with the bars or mouse fails to function. The up/down and sideways functions lock up. It is possible to move up and down with the arrow keys. Functionality can be resumed by doing another find/replace or it is necessary to save and exit the program. Steps to Reproduce: 1.Open find/replace 2.type word/phrase to find 3.go to the desired place in document 4.close find/replace 5.scrolling locked Actual Results: 1.Open find/replace 2.type word/phrase to find 3.go to the desired place in document 4.close find/replace 5.scrolling locked 6.re-open find/replace and type another word (same place I want to work) 7.go to that word 8.close find/replace. this will sometimes unlock the scroll functions. 9.there have been incidents when the scroll function ceases without doing a find/replace. 10.in some instances it has been necessary to save and close, then reopen document Expected Results: scroll function - either with bars or mouse fails to work. Up/down/sideways Reproducible: Sometimes User Profile Reset: No Additional Info: This behavior began with the last update to Version: 6.1.0.3 Build ID: 6.1.0-2 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: en-US (en_US.UTF-8); Calc: group threaded
Could not reproduce. Maybe try in Safe mode, Help - Restart in safe mode and then Continue in safe mode. Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit Version: 6.1.1.2 Build ID: 6.1.1-1 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 8b1501d80dc9d3f42c351c6e026fa737e116cae5 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on 23 September 2018
Dear Bill H Moore, 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
Dear Bill H Moore, 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-FollowUp