Comment 3 for bug 1768233

Note that this behaviour seems to have arisen in the last couple of months around the time of the 2.40 release to xenial. However, I haven't managed to establish exactly what changed to cause it.