The new version is bionic-updates now
https://launchpad.net/ubuntu/+source/fwupd/1.0.9-0ubuntu2
** Changed in: fwupd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: fwupd (Ubuntu Xenial)
Status: Fix Committed => Won't Fix
** No longer affects: fwupd (Ubuntu Xenial)
** Also affects: fwupd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: f
Just to connect the dots, this particular fix is:
https://github.com/hughsie/fwupd/commit/86fdd975adbb725965d8a015994f023469e697d8
#diff-22684cccbec07d4328eaef43086e6f47
It's in the 1.0.9 release that will be SRUed by
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999
** Changed in: fwu
I've just fixed this upstream (i.e. don't crash the client if the server
sends the wrong thing) -- but I'd really like to know why the daemon is
sending the wrong thing in the first place. Are there any critical
warnings from the fwupd process in the journal perhaps?
--
You received this bug noti
** Summary changed:
- gnome-software crashed with SIGSEGV in fwupd_device_from_key_value()
+ gnome-software crashed with SIGSEGV in fwupd_device_from_key_value →
fwupd_device_set_from_variant_iter → fwupd_device_from_variant →
fwupd_client_signal_cb
--
You received this bug notification becaus
