Description: Hello, test the attached document. Fill the grey fields. When I open the print dialog (or, after closing it without printing, I double-click on the first ROAD field), the first ROAD grey field is corrupted and have the TIMETABLE value copied inside its text... Steps to Reproduce: 1. write on fields 2. open print dialog (if the bug doesn't appear, close the print dialog and double click on first field) Actual Results: The first field is corrupted Expected Results: The first field should not be modified Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 153550 [details] odt file for the bug
Thank you for reporting the bug. I cannot reproduce the bug in Version: 6.3.0.0.alpha0+ Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04 Locale: en-US (en_US); UI-Language: en-US Calc: threaded and in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Created attachment 154216 [details] new DOC with the bug
Created attachment 154217 [details] Video demonstrating the bug
now I've uploaded a new version of the doc and a video about it. I'm using LibreOffice 6.2.7 (the STILL version). Steps to reproduce it: go to the field in which the value is "ewqewqew 2", double click on it and write a new number (in the video I added a 2 to the end -> "ewqewqew 22") you see that the fields is modified...
I confirm it with Version: 6.4.0.0.alpha0+ (x64) Build-ID: f0c832acb53326ccc9a8c1a47401fbc9e1081feb CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-11_05:46:53 Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Still present in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to reproduce 1. Open attachment 154216 [details] 2. Double click in field of cell B1 in first table (ewqewqew 2) 3. Change entry to ewqewqew 23 => OK Actual result entry changes to ewqewqew 210.00 - 12.000.00 - 12.00 Expected result no change (still ewqewqew 23)
Dear luca.manganelli, 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
(In reply to QA Administrators from comment #9) > Test to see if the bug is still present with the latest version of > LibreOffice from https://www.libreoffice.org/download/ It is still present in the actually latest LibreOffice 7.5.5. > 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/ I downloaded all old version of LibreOffice from 3.3 to earlier, and I discovered that this bug appeared between: - LibreOffice 4.2.8 is the LAST working version, WITHOUT this bug - LibreOffice 4.3.0.4 is the first next release I tried that HAS this bug (I have tried many releases, all higher than 4.3, and they have all this bug).
No repro with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 71c28942fbc7f36e5bcd46c5a6cdfbb3fcbcd6a0 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Seems to be fixed with dev version. Please could you test it with dev version? You can download it here: http://dev-builds.libreoffice.org/daily/master/ Thank you
Yes, no repro with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 40617d867346956588ac023511f31210107217f4 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 => RESOLVED WORKSFORME