| Summary: | Calc: Can't create 2nd group at the previous position of 1st group (until reloaded) | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | PhBe <sitanou> |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | aron.budea, lo_bugs, miguelangelrv, oliver.brinzing, xiscofauli |
| Priority: | medium | Keywords: | notBibisectable, regression |
| Version: | 3.6.0.4 release | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 116661 | ||
| Attachments: | bibisect-linux-64-releases, tail of terminal output | ||
|
Description
PhBe
2019-11-07 10:03:33 UTC
Repro Version: 6.4.0.0.alpha1+ (x64) Build ID: 25c390e17a7f1c018b5eed1ef7dfd568b76f4a84 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: CL After reload the file works for me. Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) but not in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Created attachment 155992 [details]
bibisect-linux-64-releases, tail of terminal output
Working on debian buster in bibisect-linux-releases repository, I see
that the problem started between openoffice-3.3.0 and
libreoffice-3.5.0rc3.
I had to skip many probes for the lack of libpng12.so.0. The
resulting range is so large that I am leaving keyword bibisectRequest.
For me 3.5.0.3 is still fine, and the bug started with 3.6.0.4. Bibisected to the following range using repo bibisect-43all (single commit in the bibisect repo). Unfortunately the range is 2011-12-13 to 2012-02-06, which is unhelpful. Setting keyword notBibisectable. https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=43c7830b03d141ae11d8617c0fdabefa32dd243c..ce97851773a06103504972eb2771eecd7dd81e36 Dear PhBe, 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 Repro 24.8. |