This looks like it could be the same bug reported about a month ago. Maybe it’s still on the to-do list …