Comment 8 for bug 1813946

Revision history for this message
Jonas Dahlbaek (dahlbaek) wrote :

I can verify that updating to 4.15.0.45.47 fixed this problem for me.