Comment 2 for bug 1653063

Revision history for this message
Peter Maydell (pmaydell) wrote :

I think we fixed this bug in commit 013aabdc665e4256b38d which would have been in the 3.1.0 release (this is why we closed #1774677, which is the same issue).