Jonne,
I just sought clarification upstream, and apparently this was fixed after 1.4.3 also. It will be available in the first 1.5 release.
Also, "Fix Committed" does not imply any release in Ubuntu. (That status is confusing to me since we're tracking the bug upstream already, but there it is.)
In the meantime, it can be requested for a backport once it's released (9.10?) or specifically patched to fix this bug, though I'm not sure how the latter process works.
Jonne,
I just sought clarification upstream, and apparently this was fixed after 1.4.3 also. It will be available in the first 1.5 release.
Also, "Fix Committed" does not imply any release in Ubuntu. (That status is confusing to me since we're tracking the bug upstream already, but there it is.)
In the meantime, it can be requested for a backport once it's released (9.10?) or specifically patched to fix this bug, though I'm not sure how the latter process works.