nmcli error report on reboot after latest 20.04 updates

[Bill (franksmcb)]

Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416.

Upon reboot system should error and error for nmcli.

Crash file located in /var/crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Apr 16 21:58:56 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-04-25 (357 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp2s0 scope link metric 1000
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago)
nmcli-dev:
 DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp2s0 wifi connected full full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1
 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- --
 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected started full enabled enabled enabled enabled enabled

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Bill (franksmcb) (franksmcb)]

Link to crash report from step #2:

https://errors.ubuntu.com/oops/88d785d4-80ba-11ea-a860-fa163ee63de6