Comment 48 for bug 756317

Unfortunately, I cannot reproduce the bug by deliberately running apt update while the captive portal is in effect.

I think I must have hit some obscure edge case that isn't covered by the existing fix. Maybe something to do with switching networks during an automatic update? Who knows. Clearly I haven't got enough information to resolve this.

Unfortunately I did not retain a copy of the files I removed, so they cannot be analysed, though I have saved a copy of the current captive portal page if anyone wants me to upload it. (It might differ from the one that triggered the bug for me though.)

Apologies for double comment.