Comment 10 for bug 1777364

Revision history for this message
Martin Barlow (martin-barlow) wrote :

I forced version 2.1 and i did NOT reproduce issue. I also forced 3.0 again, and issue occurred again.

So, it seems forcing 2.1 may also be workaround.