Whoopsie lacks fallbacks to other network management systems

[Peter J. Mello]

On a whim I thought I'd take a glance at my previous error report submissions via the System Settings panel and upon finding it empty (and unable to recall the last time I'd seen anything present on that settings panel) I elected to be nosy in journalctl about it. The problem was readily apparent upon seeing the following lines:

`Could not get the Network Manager state: GDBus.Error: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files`

I long ago switched over to systemd-networkd and systemd-resolved for network interface management (there's a small Systemd fanboy stuck inside me that I have to throw a bone to every once in a while, this time it was when both Network Manager and netplan.io didn't adequately document the configuration model for my use case), so I infer that since that time I have failed to contribute any data to the Error Tracker. In light of the fact that my inner (K)Ubuntu fanboy is the dominant fanboy within me, that's disappointing.

Surely we can give whoopsie a more robust logic chain by which to ascertain whether a network connection is present, can't we? I'm going to poke around in the codebase now to see if it's within my skill set to tackle, but this bug report is being filed in the event it's not or that someone with more time/skills cares to tackle it instead.