Comment # 2 on bug 1018371 from
Updating to 16.05.8.1 will fix this issue.


You are receiving this mail because: