Comment 19 for bug 1536871

Thanks again for the rapid feedback. It's nice to know that I jumped to an unreasonable conclusion.

Now that I know to kill the fwupd process I've made more progress testing the failure modes but still find some lacking:

- Removing /etc/pki/fwupd or /etc/pki/fwupd-metadata results in nice error messages.

- Replacing /etc/pki/fwupd/GPG-KEY-Linux-Vendor-Firmware-Service and /etc/pki/fwupd-metadata/GPG-KEY-Linux-Vendor-Firmware-Service with my own GPG key immediately after installing the fwupd package but before running "fwupdmgr refresh" does not result in any kind of error message. /var/cache/app-info/xmls/fwupd.xml is downloaded and unpacked and I can't understand why this succeeds.

To reproduce:
start with a blank xenial vm
apt-get install fwupd
gpg --recv-keys 9D8D2E97 --keyserver keys.gnupg.net
gpg --export --armor 9D8D2E97 > /etc/pki/fwupd/GPG-KEY-Linux-Vendor-Firmware-Service
gpg --export --armor 9D8D2E97 > /etc/pki/fwupd-metadata/GPG-KEY-Linux-Vendor-Firmware-Service
ls -l /var/cache/app-info/xmls/fwupd.xml # confirm ENOENT
fwupdmgr refresh
ls -l /var/cache/app-info/xmls/fwupd.xml # confirm created -- why?

Thanks