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

[Madd Hatter]

Failed on start right after login

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 10 01:19:41 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-04-07 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7efc46a3d326: mov (%rax),%rsi
 PC (0x7efc46a3d326) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2
 fwupd_device_from_variant () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2
 () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-software crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-04-10 (0 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:
 fwupd_device_from_key_value (value=0x55bebd5de000, key=0x7efc50011050 "Guid", device=0x55beba285530) at ../libfwupd/fwupd-device.c:979
 fwupd_device_set_from_variant_iter (device=device@entry=0x55beba285530, iter=0x7efc387d5230) at ../libfwupd/fwupd-device.c:1353
 fwupd_device_from_variant (data=data@entry=0x55bebd6666a0) at ../libfwupd/fwupd-device.c:1384
 fwupd_client_signal_cb (proxy=<optimized out>, sender_name=0x55bebe856620 ":1.146", signal_name=0x55bebe443d10 "DeviceRemoved", parameters=0x55bebd6666a0, client=0x55beba1b4b60) at ../libfwupd/fwupd-client.c:183
 ffi_call_unix64 () at ../src/x86/unix64.S:76

[Richard Hughes (richard-hughes)]

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?

[Mario Limonciello (superm1)]

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

[Sebastien Bacher (seb128)]

The new version is bionic-updates now
https://launchpad.net/ubuntu/+source/fwupd/1.0.9-0ubuntu2