Right, since this was with a daily image using 4.8.0-11, it's quite possible this has already been fixed in a later image build and is worth a re-check.
Right, since this was with a daily image using 4.8.0-11, it's quite possible this has already been fixed in a later image build and is worth a re-check.