fwupd crashed with SIGSEGV in FU_IS_DEVICE()

[Николай Кузьмин]

just rebooted ubuntu artful

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: fwupd 0.9.7-2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 12 20:36:03 2017
ExecutablePath: /usr/lib/fwupd/fwupd
InstallationDate: Installed on 2017-04-10 (158 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
ProcCmdline: /usr/lib/fwupd/fwupd
SegvAnalysis:
 Segfault happened at: 0x55e632d68c7f <fu_plugin_device_add+79>: cmp (%rdx),%rax
 PC (0x55e632d68c7f) ok
 source "(%rdx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fwupd
StacktraceTop:
 fu_plugin_device_add ()
 ()
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: fwupd crashed with SIGSEGV in fu_plugin_device_add()
UpgradeStatus: Upgraded to artful on 2017-09-10 (5 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 FU_IS_DEVICE (ptr=0x55e63330a790) at ../src/fu-device.h:31
 fu_plugin_device_add (plugin=0x55e6332e2280, device=0x55e63330a790) at ../src/fu-plugin.c:317
 fu_plugin_device_add_delay_cb (user_data=0x55e633313260, user_data@entry=<error reading variable: value has been optimized out>) at ../src/fu-plugin.c:374
 g_timeout_dispatch (source=source@entry=0x55e633313290, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633
 g_main_dispatch (context=0x55e6332a98a0) at ../../../../glib/gmain.c:3148

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Richard Hughes (richard-hughes)]

Looks like https://github.com/hughsie/fwupd/commit/0dec274e56c23c4afdda75bb42d5b6c9928cb1b6

[Mario Limonciello (superm1)]

@bigon had confirmed that 1.0.0 did fix it, which is now in master. According to github #259 the patch linked in comment #7 on top of 0.9.x didn't fix it however, so it could have been a combination of other items in master that had actually fixed the issue.