Comment 24 for bug 1874464

I just saw this again on 5.8.0-18-generic, and this time I did not manually modify my networking state; I installed the new kernel and rebooted into it, and the problem exhibited immediately. (Fortunately, for whatever reason, a reboot into Windows and back to -18 _has_ come up with networking, so it isn't happening on every boot.)

I'll try a 4.15 kernel as requested in the last comment, and see what happens.