Unfortunately this stack trace is client side, but we don't know what actually happened on the daemon during this situation to get to the bottom of the problem.
Can you reproduce this again? If so, it would be really useful if you could run the daemon under debug (or possibly valgrind) to figure out what that side was doing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1756695 Title: gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1756695/+subscriptions -- desktop-bugs mailing list firstname.lastname@example.org https://lists.ubuntu.com/mailman/listinfo/desktop-bugs