Capt. Jack

> I think you'll need to share the daemon log in verbose mode so we can see what the modem manager plugin is doing. Please with 1.4.4. Sure...what are the...

``` (fwupdmgr:875): FuMain-DEBUG: 16:38:54.314: DW5821e Snapdragon X20 LTE DeviceId: fa707b9af86ff44bc17316b6c3e5ea82aab3ce86 Guid: 64da2d58-8d1b-5e5b-b793-f88ba5a25a8f

> Oh, I notice in there: > > `│ Update Error: No vendor ID set` > > That might be the root of the problem. Yes, that's what I'm suspecting...

> This commit: > [d8ea8da](https://github.com/fwupd/fwupd/commit/d8ea8da902493638bbe776ca854c1c17ca0fbcee) Is it (vendor-id) expected to be in this dictionary? https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.Firmware.html#gdbus-property-org-freedesktop-ModemManager1-Modem-Firmware.UpdateSettings Is there a way to workaround this for now?

> `fwupdmgr modify-config VerboseDomains *` ``` fwupdmgr modify-config VerboseDomains * Invalid arguments: KEY VALUE expected ``` ``` fwupdmgr modify-config VerboseDomains modem_manager Restart the daemon to make the change effective? [Y|n]:...

OK, I sudo to root and set the domain modem_manager to verbose without the error. However, nothing interesting from the journal after doing the get-devices. ``` Jun 16 07:59:37 systemd[1]:...

> Oh darn, I forgot that doesn't work with snap because of something funny snap does in argument handling. There is a config file in `/root/snap/fwupd/` somewhere called daemon.conf. You...

Hi...sorry for the impatience, but while this is being fixed and release, is there a work around I can use in the meantime to either ignore this check or force...

Where can I update that file on my snap install? I did this, but the only file with that name is on a read-only file-system: ``` sudo find /snap -name...

@superm1 - Do I need to recreate the full path (quirks.d etc.)?