Comment 8 for bug 1713457

I cannot reproduce this on debian.

It seems that one of the difference is that resolvconf support is disabled in the ubuntu package. I feel that the problem comes from here. resovconf support should probably (not tested) be enabled in case it's pulled on the system by a dependency