It appears this bug was fixed in the very next revision of ooo-build-3-0-1 so it will be fixed after Jaunty alpha 3.
It appears this bug was fixed in the very next revision of ooo-build-3-0-1 so it will be fixed after Jaunty alpha 3.