Comment 22 for bug 72262

From the original Debian bug report it seems to be a factor of the Java version with which OOo was built. (The original bug report is now over a year old. It looks like there is some progress on it, but it seems very slow.) It seems that probably the only way this will get fixed is if OOo built with the now GPL'ed (or soon-to-be GPL'ed?) Sun java gets into the distribution. If it comes by way of upstream, then that's perfect, otherwise does anybody know whether it would be possible for Ubuntu to add it? Does anybody know who would be responsible for making a decision on this? Even a definitive "no" on this would be helpful, because then we'd know that it's just a matter of waiting for upstream to fix it, and that any efforts would be better spent on the Debian side of things. (BTW, as has been reported by others, removing all OOo packages and installing OOo from Sun's site fixed the problem for me. I had previously experienced these problems using the package-installed OOo with both Sun's runtime Java and the FSF's Java.)