Comment 82 for bug 1824874

How do I figure out which application tripped the policy and then resulted in the dialog?

In my case the unclickable dialog happens on my Desktop PC booting into my Ubuntu 20.04.
No VM, no remote connection, no xRPD involved, no new software installed, no torrents, and downloaded nothing.

I have several virtual networks created by docker, but this setup worked for years until a few days ago.

The only change was that I added a new SSD to the system on top of existing ones, formatted to ext4, but it's not even in fstab yet.

```
apt list gnome-shell -a
Listing... Done
gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.1 amd64 [installed]
gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64
gnome-shell/focal 3.36.1-5ubuntu1 amd64
```