Bug 84041 - FORMATTING: Bug in numbering
Summary: FORMATTING: Bug in numbering
Status: RESOLVED DUPLICATE of bug 87548
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.1.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2014-09-18 13:23 UTC by Michael Kůr
Modified: 2015-12-17 08:35 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Here is wrong numbering (41.19 KB, image/jpeg)
2014-09-18 13:23 UTC, Michael Kůr
Details
Sample file (20.49 KB, application/vnd.oasis.opendocument.text)
2014-09-29 10:57 UTC, Michael Kůr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kůr 2014-09-18 13:23:05 UTC
Created attachment 106502 [details]
Here is wrong numbering

Steps to reproduce:
1. Select text, so that the lines which you want to apply numbering are not groped together.
2. Apply numbering
3. You see that after gap numbering will restarts

Current behavior: The numbering will go 1, 2, 3, 4....

Expected behavior: The numbering restarts (1, 2, 1, 1, 2...)

Here is video, which gave you more exact way how to reproduce the bug:
https://www.youtube.com/watch?v=Ckn0v3PqgOY
              
Operating System: Windows 8
Version: 4.3.1.2 release
Comment 1 Jorendc 2014-09-22 09:08:01 UTC
(In reply to comment #0)
> 3. You see that after gap numbering will restarts

So 1, 2, 1, 1, 2 as shown in your screenshot?

> Current behavior: The numbering will go 1, 2, 3, 4....
> 
> Expected behavior: The numbering restarts (1, 2, 1, 1, 2...)

I guess you flipped the current and expected behavior?
Comment 2 Michael Kůr 2014-09-22 13:55:58 UTC
Yes, that is a bug in the bug report. I'm sorry.
Comment 3 Yousuf Philips (jay) (retired) 2014-09-29 06:18:40 UTC
Hello Michael,

Thank you for filing the bug. Please send us a sample document, so we can tests your steps to reproduce and verify the bug.
Comment 4 Michael Kůr 2014-09-29 10:57:17 UTC
Created attachment 107059 [details]
Sample file
Comment 5 Michael Kůr 2014-09-29 10:58:02 UTC
I added the sample document.
Comment 6 Yousuf Philips (jay) (retired) 2014-09-29 23:15:52 UTC
Hi Michael,

Thank you for sending in a sample file. I can see that the bug is available in 4.3.3 and 4.4 master. Regression as it works correctly in 4.2.6.

Steps:
1) open attachment 107059 [details]
2) select numbering lines 1), 2), 3), 4), 5) using the mouse and holding ctrl
3) press the numbering button twice in the toolbar

Behaviour: all numberings are '1.'

Version: 4.3.3.0.0+
Build ID: 14907346d792f2f93a00083bbab5086cf56ddb24
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-3, Time: 2014-09-26_03:39:23

Version: 4.4.0.0.alpha0+
Build ID: df73f4115cfe4d07e4159adf087571687eb173ec
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-09-25_23:36:54
Comment 7 Xisco Faulí 2014-10-02 11:27:40 UTC
bibisected:

766413e76a63c047bfd6227ab12fcd866 is the first bad commit
commit ce81582766413e76a63c047bfd6227ab12fcd866
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Mon May 12 01:37:21 2014 +0000

    source-hash-3d1b1eea83703919c43620f9adef05e5b24c4bed
    
    commit 3d1b1eea83703919c43620f9adef05e5b24c4bed
    Author:     Caolán McNamara <caolanm@redhat.com>
    AuthorDate: Wed Mar 19 12:27:07 2014 +0000
    Commit:     Caolán McNamara <caolanm@redhat.com>
    CommitDate: Wed Mar 19 15:37:56 2014 +0000
    
        coverity#735757 Unchecked dynamic_cast
    
        Change-Id: I268b9c4df81598f68b8da2c258d70c2118b69d82

:100644 100644 55e483c4a724436ee0e792f72b90a3d301c77064 46da6ac1f330f20bd0a4ebebe27910e2c0e49e49 M	ccache.log
:100644 100644 109c99441737bb49205950d8d26f994ab7ade8ca 88c019e4e1f3e2591ad255a84ebb468863e18b3f M	commitmsg
:100644 100644 489b61544cecbe2b2fc066ce04098712be6374d8 80fe30beee6868b7ef681d3d1040c51b252661ea M	make.log
:040000 040000 8d40ab0ff1362b98fa7646afb94a246acb54cd98 fe475bf82129a0a85c90230737d704d41ab77938 M	opt

[423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
# good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932
git bisect start 'latest' 'oldest'
# good: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect good e02439a3d6297a1f5334fa558ddec5ef4212c574
# good: [4850941efe43ae800be5c76e1102ab80ac2c085d] source-hash-980a6e552502f02f12c15bfb1c9f8e6269499f4b
git bisect good 4850941efe43ae800be5c76e1102ab80ac2c085d
# good: [a900e72b6357882284c5955bdf939bf14269f5fb] source-hash-dd1050b182260a26a1d0ba6d0ef3a6fecc3f4e07
git bisect good a900e72b6357882284c5955bdf939bf14269f5fb
# good: [a900e72b6357882284c5955bdf939bf14269f5fb] source-hash-dd1050b182260a26a1d0ba6d0ef3a6fecc3f4e07
git bisect good a900e72b6357882284c5955bdf939bf14269f5fb
# skip: [e80660c5a1d812cd04586dae1f22767fc3778c4a] source-hash-07c60c8ee2d1465544a6a39e57bc06b3690b8dfb
git bisect skip e80660c5a1d812cd04586dae1f22767fc3778c4a
# bad: [df9bcaed2faa2a8d11b19f877cdff3a12a887278] source-hash-6ba9692d8bbe3e3c245aca9a7c928e81178d05f1
git bisect bad df9bcaed2faa2a8d11b19f877cdff3a12a887278
# bad: [9d57c189d74551d2b3770cc81139ea10a62e672f] source-hash-5b5e62650354788e50b44f32c22b687b2018aba9
git bisect bad 9d57c189d74551d2b3770cc81139ea10a62e672f
# bad: [ce81582766413e76a63c047bfd6227ab12fcd866] source-hash-3d1b1eea83703919c43620f9adef05e5b24c4bed
git bisect bad ce81582766413e76a63c047bfd6227ab12fcd866
# good: [4e0843c411a14e3065f96f196eeb4d603664f97f] source-hash-51605bf98220d7e54dee20af17c33cebe23a0813
git bisect good 4e0843c411a14e3065f96f196eeb4d603664f97f
# good: [bfba063779a12bca219e4a9fba9bba8b67821ec1] source-hash-86a32589e90ee983159fb5b2c6a594428ab7d422
git bisect good bfba063779a12bca219e4a9fba9bba8b67821ec1
# good: [db29eee512d03b1dc0139b3752bbe7931b165377] source-hash-77b6c1602aaa0bd059077765e7fabb53d9e6ddeb
git bisect good db29eee512d03b1dc0139b3752bbe7931b165377
# good: [e34eadbaf87d8e71ebd9cf34e6acc628ad0b4650] source-hash-7b56d303300fbf592473b28b654fd22fec110962
git bisect good e34eadbaf87d8e71ebd9cf34e6acc628ad0b4650
# first bad commit: [ce81582766413e76a63c047bfd6227ab12fcd866] source-hash-3d1b1eea83703919c43620f9adef05e5b24c4bed
Comment 8 Xisco Faulí 2014-10-02 11:33:08 UTC
This commit 04187aaf09969341a7ae9ae7ff5a13925381a96b looks quite suspiciouss...
Comment 9 Björn Michaelsen 2014-10-16 14:59:00 UTC
(This is an automated message.)

It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.)

Thus setting keyword "bisected".
Comment 10 Yousuf Philips (jay) (retired) 2015-03-08 10:54:18 UTC
CCing Caolán the bibisect reported his commit.
Comment 11 Caolán McNamara 2015-04-03 12:24:27 UTC

*** This bug has been marked as a duplicate of bug 87548 ***
Comment 12 Robinson Tryon (qubit) 2015-12-17 08:35:53 UTC
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]