Does anybody else can reproduce this bug if you manually change IPv6 settings to Automatic? If so, I do think this bug should be kept opening.
Does anybody else can reproduce this bug if you manually change IPv6 settings to Automatic? If so, I do think this bug should be kept opening.