Bug 84391 - White lines between paragraphs when paragraph background color set
Summary: White lines between paragraphs when paragraph background color set
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.0.0.alpha0+ Master
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2014-09-27 09:24 UTC by Yousuf Philips (jay) (retired)
Modified: 2015-12-15 11:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
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 Yousuf Philips (jay) (retired) 2014-09-27 09:24:04 UTC 
Steps:
1) Open writer
2) Change paragraph background color
3) Press enter a few times

Behaviour: Each new line has a whitish line between them.

Tested on master on Windows and Linux.

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 1 Matthew Francis 2014-09-27 12:23:06 UTC 
Also reproducible on OSX/4.4 master

git bisect start
# bad: [43872fb10d2b129017dcddb83a7e0b14a0790e61] 2014-09-20
git bisect bad 43872fb10d2b129017dcddb83a7e0b14a0790e61
# good: [b3130c846de5cf1b4be48b48dfc780bb369549fa] 2014-05-21
git bisect good b3130c846de5cf1b4be48b48dfc780bb369549fa
# bad: [2b0304ea2fa4675aecc3d9c617dc1daa774cdff8] 2014-07-20
git bisect bad 2b0304ea2fa4675aecc3d9c617dc1daa774cdff8
# good: [3940c8876107f8bd07b8938a3a114d0e056af5b6] 2014-06-20
git bisect good 3940c8876107f8bd07b8938a3a114d0e056af5b6
# bad: [479f8e7126777715c2ce39bb89483b88696f747e] 2014-07-05
git bisect bad 479f8e7126777715c2ce39bb89483b88696f747e
# good: [0f33e70e503bddcb7eb9c462407c9cda6d3e3a14] 2014-06-27
git bisect good 0f33e70e503bddcb7eb9c462407c9cda6d3e3a14
# good: [51d0b5cdc80ce7b0a3e0694e91547d3e7942f19f] 2014-07-01
git bisect good 51d0b5cdc80ce7b0a3e0694e91547d3e7942f19f
# bad: [3c19bff344aa6109cdd40e5ab4986a95ecdd7542] 2014-07-03
git bisect bad 3c19bff344aa6109cdd40e5ab4986a95ecdd7542
# bad: [b7ea5ebd0e0fee42d8971dd75b8efbc6e0e47739] 2014-07-02
git bisect bad b7ea5ebd0e0fee42d8971dd75b8efbc6e0e47739
# first bad commit: [b7ea5ebd0e0fee42d8971dd75b8efbc6e0e47739] 2014-07-02

It may be that big merge from Apache on July 1st again. Will follow up when I have a build ready at that point
Comment 2 Matthew Francis 2014-09-27 13:45:51 UTC 
As I thought, it's this one again

http://cgit.freedesktop.org/libreoffice/core/commit/?id=7d9bb549d498d6beed2c4050c402d09643febdfa
Comment 3 Björn Michaelsen 2014-10-16 14:59:01 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 5 Robinson Tryon (qubit) 2015-12-15 11:03:03 UTC 
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]