I can also confirm the presence of the problem in both 2017.02.07-1 and 2017.03.26-1 as well as the absence in upstream 2017.05.09.

Sören

Reply via email to