Red Hat Bugzilla – Bug 1460429
[abrt] fwupd: g_variant_valist_get_leaf(): fwupd killed by signal 11
Last modified: 2017-06-23 13:30:39 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (6 frames)
#0 g_variant_valist_get_leaf at gvariant.c:5074
#1 g_variant_valist_get at gvariant.c:5211
#3 g_variant_get_va at gvariant.c:5473
#4 g_variant_get at gvariant.c:5420
#5 fu_main_daemon_method_call at ../src/fu-main.c:2050
#6 call_in_idle_cb at gdbusconnection.c:4850
Created attachment 1286633 [details]
Created attachment 1286634 [details]
Created attachment 1286635 [details]
Created attachment 1286636 [details]
Created attachment 1286637 [details]
Created attachment 1286638 [details]
Created attachment 1286639 [details]
Created attachment 1286640 [details]
Created attachment 1286641 [details]
Created attachment 1286642 [details]
Created attachment 1286643 [details]
Created attachment 1286644 [details]
Does this crash reliably if you do "fwupdmgr refresh"?
I also have this crash and yes, doing fwupdmgr refresh cases fwupd crash both on fedora 25 and fedora26.
Oleg, can you tell me a bit more about your system? e.g. is it something like arm64 or with some other nonstandard bits installed? Thanks.
It's a regular del latitude 7350, nothing nonstandard about it, x86_64.
It has a touchscreen (2-in-1 system).
I was under full impression that abrt would upload the crash data somewhere ,but alas, apparently not? at least I don't see it referenced anywhere.
I can reproduce this at will with 'fwupdmgr refresh' on x86-64 (Skylake XPS, with all the capsule updates). This is the D-Bus message which kills it:
method call time=1497346827.621771 sender=:1.270 -> destination=org.freedesktop.fwupd serial=8 path=/; interface=org.freedesktop.fwupd; member=UpdateMetadataWithId
Oddly, running fwupd itself under valgrind (whether under systemd or directly) makes the fwupdmgr call succeed, and doesn't show any memory errors, but a bunch of invalid FDs being passed to close() from the child processes, specifically always 1024..1030.
Grab me here on IRC if I can help debug any.
commit b38a4fdfd631a800d4171a4eb3e519075755f430 (origin/master)
Author: Richard Hughes <email@example.com>
Date: Tue Jun 13 15:23:58 2017 +0100
Fix a crash when refreshing metadata
When processing the file handles it seems g_variant_get() actually wants to
write the fd integer. This bug does not happen every time, and seems to vanish
every time under valgrind.
:100644 100644 f1fdd68... f9b1973... M src/fu-main.c
*** Bug 1461568 has been marked as a duplicate of this bug. ***
fwupd-0.9.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-31eb1fad8f
fwupd-0.9.4-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-31eb1fad8f
fwupd-0.9.4-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1464536 has been marked as a duplicate of this bug. ***