Bug 141873 - Bad numbering; attempt to fix it crashes LO.
Summary: Bad numbering; attempt to fix it crashes LO.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-24 15:54 UTC by TorrAB
Modified: 2021-06-16 13:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
doc with header6 all numbered 0 (14.75 KB, application/vnd.oasis.opendocument.text)
2021-04-24 16:01 UTC, TorrAB
Details
screenshot after crash (27.69 KB, image/png)
2021-04-24 21:03 UTC, TorrAB
Details
doc recovered after crash (14.48 KB, application/vnd.oasis.opendocument.text)
2021-04-24 21:27 UTC, TorrAB
Details
original; all heading6 are 0 (23.25 KB, image/png)
2021-05-24 21:32 UTC, TorrAB
Details
2 paras FirstLineIndent have been deleted (21.38 KB, image/png)
2021-05-24 21:34 UTC, TorrAB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description TorrAB 2021-04-24 15:54:37 UTC
Description:
In Head6.odt, all header6 are numbered 0; they should be (Tools>ChapterNumbering, level 6) numbered 0, 1, 2…
One can fix that (?) in 2 steps: unnumber (~^u) and renumber (^m), beginning with the 1st one, even though its # 0 appears correct; then, proceed to the 2nd one: ~^u works, but ^m crashes LO! (Report sent.) In the doc recovered from the crash, 2nd header6 has been (correctly) renumbered ‘1’.

Steps to Reproduce:
1.unnumber (~^u) the 1st header6;
2.renumber (^m) it;
3.unnumber (~^u) the 2nd header6;
4.try to renumber (^m) it

Actual Results:
Crash!

Expected Results:
all header6 should be (Tools>ChapterNumbering, level 6) numbered 0, 1, 2…, without ‘fix’ or crash.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.2.2 (x64) / LibreOffice Community
Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-CA (en_US); UI: en-US
Calc: threaded
Comment 1 TorrAB 2021-04-24 16:01:20 UTC
Created attachment 171385 [details]
doc with  header6 all numbered 0
Comment 2 Julien Nabet 2021-04-24 17:14:44 UTC
Just for the record, I don't reproduce this with master sources updated today.
I unnumbered and re-numbered each one, one by one.
Comment 3 TorrAB 2021-04-24 21:03:04 UTC
Created attachment 171391 [details]
screenshot after crash
Comment 4 TorrAB 2021-04-24 21:23:58 UTC
(In reply to Julien Nabet from comment #2)
> Just for the record, I don't reproduce this with master sources updated
> today.
> I unnumbered and re-numbered each one, one by one.

I confirm your observation (no crash) with LODev 7.2
Then, I tried again with LO7.1.2.2 —which crashed after the 3rd renumbering!

Attachment #171391 [details] to prove I was not dreaming…
The next attachment shows the recovered doc, with numbers 0, 1, 2, 0, 0
The crash report was successfully uploaded.
You can soon find the report at:
https://crashreport.libreoffice.org/stats/crash_details/2718c88a-5697-4a47-816e-1a0b98bab476
Comment 5 TorrAB 2021-04-24 21:27:03 UTC
Created attachment 171392 [details]
doc recovered after crash
Comment 6 Xisco Faulí 2021-05-20 08:42:21 UTC
Hello TorrAB@Yahoo.com,
could you please attach a screencast showing how to reproduce the issue ? I don't understand the steps 'unnumber (~^u)' and 'renumber (^m)'
Comment 7 TorrAB 2021-05-23 01:33:07 UTC
(In reply to Xisco Faulí from comment #6)
> Hello TorrAB@Yahoo.com,
> could you please attach a screencast showing how to reproduce the issue ? I
> don't understand the steps 'unnumber (~^u)' and 'renumber (^m)'

Hello!
Good news: no more crash under version 7.1.3.2.
But the numbering (0 everywhere) remains faulty.
~ = Alt; ^ = Ctrl (Ancient but compact notation.)
For unnumber, you can format>paragraph>numbering style: none
Comment 8 TorrAB 2021-05-23 01:39:30 UTC
New observation: The numbering becomes normal if you remove the FirstLineIndents paragraphs, as if a FirstLineIndent reset the numbering. (It should not.)
 But, if that were the case, why would the sequence 'unnumber' and 'renumber' work, ie, number the heading6's normally in the presence of FirstLineIndents?
Comment 9 Xisco Faulí 2021-05-24 09:31:27 UTC
(In reply to TorrAB from comment #8)
> New observation: The numbering becomes normal if you remove the
> FirstLineIndents paragraphs, as if a FirstLineIndent reset the numbering.
> (It should not.)
>  But, if that were the case, why would the sequence 'unnumber' and
> 'renumber' work, ie, number the heading6's normally in the presence of
> FirstLineIndents?

Please, attach a screencast
Comment 10 TorrAB 2021-05-24 21:28:22 UTC
(In reply to Xisco Faulí from comment #9)
> (In reply to TorrAB from comment #8)
> > New observation: The numbering becomes normal if you remove the
> > FirstLineIndents paragraphs, as if a FirstLineIndent reset the numbering.
> > (It should not.)
> >  But, if that were the case, why would the sequence 'unnumber' and
> > 'renumber' work, ie, number the heading6's normally in the presence of
> > FirstLineIndents?
> 
> Please, attach a screencast

Head6.png: original
Head6a.png: after deletion of two FirstLineIndent paras
Comment 11 TorrAB 2021-05-24 21:32:18 UTC
Created attachment 172306 [details]
original; all heading6 are 0
Comment 12 TorrAB 2021-05-24 21:34:10 UTC
Created attachment 172307 [details]
2 paras FirstLineIndent have been deleted
Comment 13 Timur 2021-06-16 13:31:11 UTC
After 99 bugs, one should know the basics: one issue per bug. 
Here no crash, WFM 
For "header6 are numbered 0; they should be numbered 0, 1, 2…" it's InsufficientData because it's not explained how it was created. 
Obviously messed around with numbering, please do not report.