Comment 4 for bug 1591868

There's a few duplicates of this so far, but not a clear set of steps to reproduce this yet.

Can someone affected please do the following:
1) First confirm that you are on the latest version of fwupd in Ubuntu. This is version 0.7.0-0ubuntu4.2 for xenial.
2) Install the relevant debug symbols as mentioned by @hughsie.
For 64 bit:
http://ddebs.ubuntu.com/ubuntu/pool/main/f/fwupd/fwupd-dbgsym_0.7.0-0ubuntu4.2_amd64.ddeb
http://ddebs.ubuntu.com/ubuntu/pool/main/f/fwupd/libdfu1-dbgsym_0.7.0-0ubuntu4.2_amd64.ddeb
http://ddebs.ubuntu.com/ubuntu/pool/main/f/fwupd/libfwupd1-dbgsym_0.7.0-0ubuntu4.2_amd64.ddeb
http://ddebs.ubuntu.com/ubuntu/pool/main/a/appstream-glib/libappstream-glib8-dbgsym_0.5.13-1_amd64.ddeb
# sudo apt install libyaml-0-2-dbg

3) # sudo killall fwupd
4) # sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v
5) In a separate terminal: # fwupdmgr get-devices
6) In a separate terminal: # fwupdmgr monitor
5) Reproduce the issue

Hopefully the terminal output from (4, 5, 6) will be useful. If it's not, then when this is happening attaching to the process using gdb (details available https://wiki.ubuntu.com/Backtrace#Already_running_programs) and provide the backtrace.

The backtrace in this bug didn't have debug symbols installed, so it wasn't useful to figure out what was actually happening.