cragw
cragw
Do you have `gcab` installed on your system? if not, please install it first.
Does this help to remove the message? ``` $ sudo mv /var/lib/fwupd/pending.db /tmp/ $ fwupdmgr refresh --force ```
> Yes, if I remove that file the message goes away on the next `sudo fwupdmgr refresh --force`. Good to know it did help. > Here is the file https://app.box.com/s/1tg80axqibxcipbixc8uu2ufablbx7ms...
> That points to a firmware bug with delayed activation. [@CragW](https://github.com/CragW) does it help with investigation perhaps? hmm.. that sounds like something around disconnect update. Will check.
> > FYI, `fwupd` 2.0.7 released on Arch as of today. > > I can tell. This allowed me to upgrade the dock What is your thunderbolt version before and...
> Can up please attach an emulation with all devices tagged? The other components are gtype devices enumerated within ec that cannot be tagged (i.e.: lack of `can tag for...
> on the assumption you've tested this with actual hardware on that branch, LGTM, thanks. A second please, after stressing on plenty cycles there is a timing issue. Debugging.
> A second please, after stressing on plenty cycles there is a timing issue. Debugging. With this PR we are ready for 1.9.31.
@tjanez Can you contact Dell support for further analysis on this isuse? This might be firmware issue instead fwupd's fault.
What does `lsusb` tell? ``` $ lsusb ``` Can you attach the txt file, please? ``` $ sudo fwupdtool get-devices -vv 2>&1 | tee /tmp/wd19.txt ```