This bug was actually fixed in 1.0.38-0ubuntu0.16.04.3 and it continues to be fixed in 1.0.38-0ubuntu0.16.04.4.
This bug was actually fixed in 1.0.38- 0ubuntu0. 16.04.3 and it continues to be fixed in 1.0.38- 0ubuntu0. 16.04.4.