Description: Intermittent problem. Running Version: 6.0.4.2 (x64) on Windows 7 Professional. 11 page .odt document while writing I'll ctrl "b" or click the bold text icon after selecting target text. All pages of all text are then bold. ctrl "z" then... I save and try again. Same result. Doesn't matter how long I wait. Close and re-open document does not solve. font "Verdana" set to regular in "format"-"Character"-"font" Should not have to restart machine so have not. Steps to Reproduce: 1. heading 3> enter > Numbered list > bold text 2. Create new sentence not numbered > normal text 3. Create new numbered sentence > highlite text > ctrl "b". Actual Results: All Text All Pages bold. Expected Results: I expected to have the highlighted text now bold. Not the entire document. The software should respond to the command "un-bold" and the command "bold highlighted text" instead of "bold all text on all pages". Reproducible: Sometimes User Profile Reset: Yes Additional Info: I did go to safe mode in writer and reverted to last good configuration and it appeared to be fixed. Still very annoying. I have donated by the way. more than once. Not that I expect favor because I don't. Just saying, not a mooch. Thanks team for a great product
(In reply to Michael Shurtleff from comment #0) > Steps to Reproduce: > 1. heading 3> enter > Numbered list > bold text > 2. Create new sentence not numbered > normal text > 3. Create new numbered sentence > highlite text > ctrl "b". I tried this with a blank document starting from scratch, but did not see the problematic effect. Can you create a minimal document containing all the steps before the last "highlite text > ctrl "b"" that reliably shows the problem? Please attach it to the report. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document. 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 Michael Shurtleff, 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 Michael Shurtleff, 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