Comment # 1 on bug 1176553 from Jonathan Kang

> gnome-shell[1363]: Device state invalid, is 0
> NetworkManager[3528]: <info>  [1600161229.2581] NetworkManager (version 1.26.2) is starting... (after a restart)

It seems NetworkManager is still in the state of restarting when GNOME Shell is
populating the wifi dialog.

When the connect button is clicked, GNOME Shell tries to connect to an invalid
connection, logging the following line:
> gnome-shell[1363]: error: Execution of ���gnome-control-center��� failed:: Array element (type filename) may not be null

This might be caused by low performance of the test machine:
> gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-19ms), your system is too slow
> gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-1ms), your system is too slow
> gnome-shell[1363]: libinput error: event3  - QEMU QEMU USB Tablet: client bug: event processing lagging behind by 38ms, your system is too slow
> gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-17ms), your system is too slow