Comment 0 for bug 1875172

Steps to reproduce:

1. Install GNOME Weather (sudo apt install gnome-weather)
2. In GNOME Control Center > Privacy, enable Location Services
3. Open GNOME Weather at least once, so it embeds a forecast in the notifications menu
4. Do something latency-sensitive on WiFi, like SSH or ping

Hypothesis:

When GNOME Weather is running in the background and location services are enabled, it seems to tell geoclue to use NetworkManager's D-Bus API for letting wpasupplicant scan for surrounding networks very often. This causes lots of latency spikes and visible lag.

Typing characters in an SSH session is rather laggy, and running something as simple as mtr 192.168.1.1 will show that every ~20 seconds the latency is over 100ms and packet loss occurs, while it's normally around 1.5ms with no packet loss. There are probably lots of other issues caused by this as well.

When a WiFi adapter scans for SSID's, it has to switch channels, delaying or dropping traffic in the meanwhile. This is what causes the lag and packet loss.

Disabling location services in gnome-control-center and disabling automatic location in gnome-weather solves this issue.

Expected behaviour:

Don't break WiFi for a weather report.

$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04

$ apt-cache policy gnome-weather
gnome-weather:
  Installed: 3.36.1-1
  Candidate: 3.36.1-1
  Version table:
 *** 3.36.1-1 500
        500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        500 http://nl.archive.ubuntu.com/ubuntu focal/universe i386 Packages
        100 /var/lib/dpkg/status