Comment 36 for bug 1975549

> Sebastien Bacher wrote:
>
> yes, the current details are about a working system but we want to work on the bug

Thanks again Sebastien.

I rebooted the machine with the phone tethered and it used USB0 as the network adapter. I then ran 'apport-collect 1975549'.

Here is the current nmcli when running the command in its current state (boot with phone tethered):

$ nmcli
usb0: connected to Ethernet
        "Google Nexus 4/5/7/10"
        ethernet (rndis_host), 82:1F:DF:52:0B:39, hw, mtu 1500
        ip4 default
        inet4 192.168.11.182/24
        route4 0.0.0.0/0
        route4 192.168.11.0/24
        route4 169.254.0.0/16
        inet6 fe80::801f:dfff:fe52:b39/64
        route6 fe80::/64

enp4s0: disconnected
        "Qualcomm Atheros Killer E2400"
        1 connection available
        ethernet (alx), D8:9E:F3:92:24:60, hw, mtu 1500

wlp3s0: disconnected
        "Qualcomm Atheros QCA9377"
        wifi (ath10k_pci), 90:32:4B:76:E0:B9, hw, mtu 1500

p2p-dev-wlp3s0: disconnected
        "p2p-dev-wlp3s0"
        wifi-p2p, hw

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 192.168.11.111
        interface: usb0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.