Red Hat Bugzilla – Bug 530642
Bug in java.awt.geom.IllegalPathStateException
Last modified: 2011-01-19 16:09:52 EST
Referring to the review of jaxodraw, bug #504405: the unit test fails with
[junit] Testcase: testGroupMarkedObjects(net.sf.jaxodraw.graph.JaxoGraphTest): Caused an ERROR
[junit] missing initial moveto in path definition
[junit] java.awt.geom.IllegalPathStateException: missing initial moveto in path definition
[junit] at java.awt.geom.Path2D$Float.needRoom(Path2D.java:280)
[junit] at java.awt.geom.Path2D$Float.lineTo(Path2D.java:350)
[junit] at sun.java2d.pisces.PiscesRenderingEngine$1.lineTo(PiscesRenderingEngine.java:99)
[junit] at sun.java2d.pisces.Stroker.emitLineTo(Stroker.java:742)
[junit] at sun.java2d.pisces.Stroker.finish(Stroker.java:705)
[junit] at sun.java2d.pisces.Stroker.close(Stroker.java:592)
[junit] at sun.java2d.pisces.PiscesRenderingEngine.pathTo(PiscesRenderingEngine.java:249)
[junit] at sun.java2d.pisces.PiscesRenderingEngine.strokeTo(PiscesRenderingEngine.java:231)
[junit] at sun.java2d.pisces.PiscesRenderingEngine.createStrokedShape(PiscesRenderingEngine.java:85)
[junit] at java.awt.BasicStroke.createStrokedShape(BasicStroke.java:296)
[junit] at net.sf.jaxodraw.object.loop.JaxoLoopObject.getBounds(JaxoLoopObject.java:79)
[junit] at net.sf.jaxodraw.util.JaxoGeometry.getBounds(JaxoGeometry.java:148)
[junit] at net.sf.jaxodraw.graph.JaxoGraph.groupMarkedObjects(JaxoGraph.java:715)
[junit] at net.sf.jaxodraw.graph.JaxoGraphTest.testGroupMarkedObjects(JaxoGraphTest.java:466)
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
I was able to reproduce it. I didn't run the junit tests, but when the application is run, if one tries to draw the filled ovals or rectangles an exception is thrown on the first click on the canvas.
I have done some heavy refactoring of the rendering engine lately and it seems
that has fixed this bug. I am trying to push it into openjdk7.
I will close this when it gets backported to 6.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
java-1.6.0-openjdk-184.108.40.206-220.127.116.11.fc13 has been submitted as an update for Fedora 13.
java-1.6.0-openjdk-18.104.22.168-22.214.171.124.fc14 has been submitted as an update for Fedora 14.
java-1.6.0-openjdk-126.96.36.199-188.8.131.52.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
java-1.6.0-openjdk-184.108.40.206-220.127.116.11.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.