Bug 128645 - Calc: Can't create 2nd group at the previous position of 1st group (until reloaded)
Summary: Calc: Can't create 2nd group at the previous position of 1st group (until rel...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: notBibisectable, regression
Depends on:
Blocks: Group&Outline
  Show dependency tree / graph
 
Reported: 2019-11-07 10:03 UTC by PhBe
Modified: 2026-01-11 03:11 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Attachments
bibisect-linux-64-releases, tail of terminal output (4.74 KB, text/plain)
2019-11-21 00:06 UTC, Terrence Enger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description PhBe 2019-11-07 10:03:33 UTC 
Description:
sorry for my English
When I create a line group (Ex Lines 7 to 10) and insert lines just above,
I can not create a new group starting with the first group line (line 7)

Reproducible on columns

Tested by other users of the french forum LibreOffice (topic https://forum.openoffice.org/fr/forum/viewtopic.php?f=8&p=332724)

Testé sur Windows, Ubuntu, et diverses versions de LibreOffice (5.x 6.x)

Steps to Reproduce:
1- Open a new Calc
2- Create a line group (for example 7 to 10) (with F12 key)
3- Insert new lines above (the group lines are logically moved down) - ex 5 new lines
5- Can not create a new group starting with the line 7




Actual Results:
Aucun message d'erreur le groupe ne se crée pas

Expected Results:
A line group should be created


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.0.7.2 (x64)
Build ID: 78c12ce5f2b8960f18b204a7ea82f971769f1679
Threads CPU : 2; OS : Windows 10.0; UI Render : par défaut; 
Locale : fr-FR (fr_FR); Calc: group

Version: 6.2.6.2 (x86)
Build ID: 684e730861356e74889dfe6dbddd3562aae2e6ad
Threads CPU : 2; OS : Windows 10.0; UI Render : par défaut; VCL: win; 
Locale : fr-FR (fr_FR); Langue IHM : fr-FR
Calc: threaded
Comment 1 m_a_riosv 2019-11-07 14:53:24 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.
Comment 2 Xisco Faulí 2019-11-11 14:58:23 UTC 
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
Comment 3 Terrence Enger 2019-11-21 00:06:10 UTC 
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.
Comment 4 Aron Budea 2020-04-05 05:28:46 UTC 
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
Comment 5 QA Administrators 2022-04-06 03:45:26 UTC Comment hidden (obsolete)
Comment 6 Timur 2024-01-11 11:38:00 UTC 
Repro 24.8.
Comment 7 QA Administrators 2026-01-11 03:11:31 UTC 
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