Created attachment 189128 [details] testcase File x.odt (attached) contains two lines in liberation mono font: abcd efgh 1. open it with writer 2. position cursor between b and c and press shift-down to mark characters cd<LF>ef 3. copy to the clipboard (^C) 4. move cursor down to the clear space 5. paste (^V) Expected: two lines cd ef pasted in liberation mono font. Actual: the same two lines but the first one is in liberation serif font. This issue occurs only when pasting more than one line and the first line is copied not from its start. Clean profile, Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded Windows has the same problem although I didn't test with a clean profile there.
Thanks for reporting. I can reproduce in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded I've noticed from testing that the issue occurs only when the formatting style is anything except 'default paragraph style'. The first copied line will change to 'default paragraph style' and the second copied line retains the original formatting. This results in the change in font as described. The defect also only seems to happen with liberation font styles and not other fonts like 'Times New Roman' for example.
Reproducible in v.3.3.0, updating version to Inherited From OOo. Also reproducible in daily master build. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9a37652b79001bf5208841b9221dee851b9b6d0f CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Dear lvm, 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