Comment 2 for bug 1965500

Revision history for this message
Jiri Srba (srba) wrote :

I can confirm that it is the revision 1613 that broke this, in revision 1612 all was working fine.