Correct, the bug was not yet fixed. But the priority for fixing this bug was now a bit increased. Though still no ETA for a fix, sorry.