Apparently this is fixed now, somehow this report got ignored... *** This bug has been marked as a duplicate of bug 951977 ***