Description: Word count starting again when pasting unformatted text to a footnote (maybe bug 120515) Steps to Reproduce: 1. Open attachment 145863 [details] 2. Select some text part & copy it 3. Select the text in a footnote, CTRL+SHIFT+V.. Paste as unformatted text. Word count starts again Actual Results: Full word recount Expected Results: Only the change Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha0+ Build ID: b63d48a146c3615f56b6ec83361b3c02ebcbb215 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-13_23:33:20 Locale: nl-NL (nl_NL); Calc: CL
I confirm this with Version: 6.2.0.0.alpha0+ (x64) Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42 Locale: en-US (de_DE); Calc: CL but it only happens the first time. If you paste the copied text a second time, everything works O. K.
Reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; but not in Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
This seems to have begun at the below commit. Adding Cc: to Noel Grandin; Could you possibly take a look at this one? Thanks 46a5506b97ad5599ec0c27abe6d39f46de3d7360 is the first bad commit commit 46a5506b97ad5599ec0c27abe6d39f46de3d7360 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Thu Sep 10 18:25:16 2015 -0700 source e126468e5dbc4ef85fc4b6146e0ba73e85281f70 author Noel Grandin <noel@peralex.com> 2015-09-07 14:01:23 +0200 committer Noel Grandin <noel@peralex.com> 2015-09-08 08:16:46 +0200 commit e126468e5dbc4ef85fc4b6146e0ba73e85281f70 (patch) tree 929c0344bcb272fe6fb4d158ec70abc775568b7d parent b4deeef405fc4200c1b33d2cecf7b301417b2398 (diff) convert Link<> to typed
raal, are you sure about that? that commit modified the character map dialog, it didn't touch anything at all word count related
Dear Telesto, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro Version: 6.4.0.0.alpha0+ (x86) Build ID: c45d477b0a0038d9c25176cf7cff299e5ddf3a7a CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-09-30_05:06:55 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL As comment 1 states, only at the first paste
repro 7.2+, but not in bibisect-50max The type of paste doesn't matter. A normal paste does the same thing. Nor does it matter whether the paste is into a footnote or not. I saw the same thing happening in the oldest of bibisect-linux-64-5.2 (aka 5.1). When testing bibisect-50max, it didn't seem to re-count the words. BIBISECT_REQUEST: I think Windows has a nice 5.1 bibisect. There is no nice bibisect 51 for Linux. I have a daily, debug version, but the debug is much slower. On the oldest commit (which matches the day after 50 master), I notice the word count restarting from 1. So I'm doubtful whether a bibisect will turn up anything...
This started with the following xommit, bibisected using repo bibisect-win32-5.1. https://cgit.freedesktop.org/libreoffice/core/commit/?id=b0fde7a912ff3aa370496802f20895b1158b072c author Ashod Nakashian <ashodnakashian@yahoo.com> 2015-07-05 12:05:26 -0400 committer Caolán McNamara <caolanm@redhat.com> 2015-07-15 07:46:01 +0000 tdf#38837 Reduce power consumption by minimizing idle timers
Dear Telesto, 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
Still present in Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded