Comment 5 for bug 138337

I'm the original reporter of the bug, but with a new ID.

Unfortunately I don't see myself having the time to check this out any time soon, but if the application is still at the same version as it was then, as I suspect it probably is, then I think it is safe to assume the problem is still there.