Incorrect rendering of thick lines and polygons (doko 2.0.1-0breezy1 packages)

Bug #29001 reported by José M. López-Cepero
6
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Medium
Matthias Klose
openoffice.org2 (Ubuntu)
Fix Released
High
Matthias Klose

Bug Description

Lines with a thickness over 0.00 are not rendered correctly in the experimental OpenOffice2 packages. Instead of being like a rectangle, they look "twisted", so that they have thickness 0 at the middle point of the line. Arrowheads are also not rendered if the thickness is over 0.00.

Likewise, if the thickness of the lines in an open polygon is changed to over 0.00, the polygon is incorrectly drawn closed.

This happens both in newly created lines and in ones in previously existing (and correct) documents created with earlier versions. The rendering bug also appears in exported PDF documents.

My guess is that there is a bug somewhere that makes Ooo2 consider that every line or polygon with thickness != 0.00 is a closed polygon. That would explain the weird behaviors of the lines and the fact that arrowheads dissapear.

Product: OpenOffice 2.0.1, experimental "doko" (Matthias Klose) packages (2.0.1-0breezy1)
OS: Ubuntu Breezy, i386, tested on two different computers
Steps to reproduce:
1) Launch ooimpress2
2) Choose the "line" tool (at the bottom)
3) Draw any line - the line is correctly shown with thickness 0.00
4) Give it an arrowhead with the corresponding button at the top - the arrowhead is shown
5) Increase the line thickness - the arrowhead is lost and the line is incorrectly rendered (the effect is clearer with higher thicknesses)
6) Click Edit Points (bottom). The Edit Points toolbar should appear (if not click View > Toolbars > Edit Points). Select Add Point, click in the middle of the line and drag to add a new point to it. The result is a closed triangle (the expected result is two joined straight lines forming an open polygon).
7) Click the Close Bezier button. The interior of the polygon will be filled with the fill colour (probably soft blue). This means that the polygon from step 6 was not really closed, but a rendering artifact.
8) Undo the Close Bezier operation. Select the point that was added in step 6. Click Divide curve (the icon with the scissors in the Edit Points toolbar). The result is two unjoined lines which also exhibit the "twisting" problem. This also confirms that the extra closing line in step 6 is an artifact and does not really exist.

NB. bug #6668 also refers to this, but it is not as clear and mixes various problems.

Revision history for this message
ischoegl (inch) wrote : same bug on dapper (standard repository)

I just found the same behavior on dapper. However, I would assign a higher severity, since the faulty graphics rendering makes documents containing figures useless.
The problem appears to be specific to ubuntu. I manually installed a different openoffice package, which didn't show this behavior ... http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/2.0.1-RC5/

Revision history for this message
José M. López-Cepero (cepe) wrote :

I have installed the upstream packages (downloaded from http://www.openoffice.org and converted via alien) and they do not exhibit the bug.

Changed in openoffice.org2:
assignee: nobody → doko
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Confirmed in 2.0.1-0ubuntu4 (dapper).

Changed in openoffice.org2:
status: Unconfirmed → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

This bug makes OO2 Draw almost useless. 6.04 can not ship this IMHO.

Revision history for this message
José M. López-Cepero (cepe) wrote :

Updated my system to Dapper. I can also confirm that the error does happen with the official Dapper packages.

I second Tormod's oppinion - this is a rather major bug for the final Dapper to have. Also note that it's not only OOo2 Draw which is affected - Impress is also, as well as Write and probably the whole suite. It's just that Draw and Impress happen to be the places where the bug is more noticeable.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

New versions of openoffice are being built, hopefully fixing this issue. Looking forward to testing them once they're successfully built.
https://launchpad.net/distros/ubuntu/+source/openoffice.org

Revision history for this message
José M. López-Cepero (cepe) wrote :

The OOo packages in Dapper have been updated to 2.0.1oob680m5-ubuntu2. I can confirm they no longer exhibit the bug. Well done!

As a side note, will these packages also be made available through the doko repos? I hope they are (I still run Breezy in a few computers at work ;))

Revision history for this message
José M. López-Cepero (cepe) wrote :

Please, Tormod (or any other third party), can you test the packages also? I think the bug may be safely marked as solved if they work for you.

Revision history for this message
Matthias Klose (doko) wrote :

fixed in 2.0.2 dapper

Changed in openoffice.org2:
status: Confirmed → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

fixed in 2.0.2 dapper

Revision history for this message
Matthias Klose (doko) wrote :

nothing to do with openicdl

Changed in openicdl:
status: Unconfirmed → Rejected
Revision history for this message
F.H. (fheinsen) wrote :

Matthias,

The latest version for Breezy at http://people.ubuntu.com/~doko/OOo2 still has this bug. Do you expect that it will be fixed for Breezy?

If it won't, a quick "no" would be appreciated so that I and others can figure out a way to deal with the bug until Dapper is released.

(I recognize that you're quite busy, and truly appreciate your taking the time to read and answer these posts.)

Warm regards,

Franz

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 29001] Incorrect rendering of thick lines and polygons (doko 2.0.1-0breezy1 packages)

Franz A. Heinsen schrieb:
> The latest version for Breezy at http://people.ubuntu.com/~doko/OOo2 still has this bug. Do you expect that it will be fixed for Breezy?
>
> If it won't, a quick "no" would be appreciated so that I and others can figure out a way to deal with the bug until Dapper is released.

on the list, but low priority

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.