This bug was filed from the crash reporting server and is br-18767ca4-1ab8-4199-a6e0-0673e1a735c1. ========================================= I highlighted some text which had a comment attached, and dragged it to the start of the paragraph. When I released the mouse, Writer crashed. Upon recovery, no data had been lost, but the moved text now appeared in two places, with the comment still attached to the text in its original place, the moved text ending with two special symbols embedded in the text. When I tried to reproduce the crash with a smaller file, I couldn't.
Sorry, I need to correct the version - I assumed the crash reporter would set that correctly. Version: 6.4.2.2 Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11; Locale: en-GB (en_AU.UTF-8); UI-Language: en-US Calc: threaded
Please attach a file and explain where exactly to highlight and drag.
Created attachment 159440 [details] Tiny excerpt from the book in which thje crash occurred When I tried it on just the sample document, I couldn't reproduce it. I had first tried cutting and pasting the comment to move it to the indicated location, but the comment was not copied. So I used Undo, reselected the text, and tried to move it. That's when it crashed.
I can't reproduce it in Versión: 6.4.2.2 (x86) Id. de compilación: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3 Subprocs. CPU: 2; SO: Windows 6.1 Service Pack 1 Build 7601; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
STR 1. Open attachment 159440 [details] 2. Select 'four a.m.' with the mouse 3. To begin of the sentence; before 'fingering'
(In reply to Telesto from comment #5) > STR > 1. Open attachment 159440 [details] > 2. Select 'four a.m.' with the mouse > 3. To begin of the sentence; before 'fingering' Steps 3: drag & drop it to the beginning of the sentence Reproduced in Version: 7.0.0.0.alpha0+ Build ID: acedbb8692bc84c93114dc4d441b3eb20b3ac467 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded @Telesto, thanks you for investigating this issue and found the steps to reproduce it
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=b402d0112a0bb53221b847fa372bfa3f6390a0e2 author Ashod Nakashian <ashod.nakashian@collabora.co.uk> 2018-09-28 06:27:09 -0400 committer Ashod Nakashian <ashnakash@gmail.com> 2018-12-03 08:10:45 +0100 commit b402d0112a0bb53221b847fa372bfa3f6390a0e2 (patch) tree 770cf33fa2b14159ca62a469b6bf75110d435182 parent 349748e63c698076bb44f75da9eaa104489e959c (diff) sw: paragraph-sign: erase metafields from copied text correctly Bisected with: bibisect-linux64-6.3 Adding Cc: to Ashod Nakashian
Here is confirmed for Linux and I confirm for Windows, so All is correct.
Crash report: https://crashreport.libreoffice.org/stats/crash_details/dd7c73c6-c9ef-4d13-8692-dc44d8123dc2
*** Bug 133712 has been marked as a duplicate of this bug. ***
Bug is a regression and has duplicate and same commit in bug 132892 (that also has a duplicate). We have multiple reports and bibisects and more can come. I set highest. I don't remember seeing Ashod responding in Bugzilla to his regressions. Aron, can you please check with him somehow, if possible?
I agree that a crash is bad, at the same time I'd like to point out that over the past ~1.5 years there were less than 20 reported crashes with this signature, therefore I'm not sure if the priority is warranted. https://crashreport.libreoffice.org/stats/signature/sw::mark::AnnotationMark::InitDoc
Keep in mind, that at least in my cases, LibreOffice don't provide option to crash to LibreOffice https://crashreport.libreoffice.org site. Thus crashes are much more often than you see there.
(In reply to Aron Budea from comment #12) > I agree that a crash is bad, at the same time I'd like to point out that > over the past ~1.5 years there were less than 20 reported crashes with this > signature, therefore I'm not sure if the priority is warranted. > https://crashreport.libreoffice.org/stats/signature/sw::mark::AnnotationMark: > :InitDoc In that list there are 19 reports. You can count few more by including crash reports found by KDE crash handler from https://bugs.documentfoundation.org/show_bug.cgi?id=133712 too. Then you have 20 reports with critical severity.
There is also bug 132892; there is a revert in progress https://gerrit.libreoffice.org/c/core/+/100753
*** This bug has been marked as a duplicate of bug 132892 ***