Version-Release number of selected component: fwupd-0.9.3-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/fwupd/fwupd crash_function: g_variant_valist_get_leaf executable: /usr/libexec/fwupd/fwupd journald_cursor: s=03644d8dfa4242d8832935fe06d1d411;i=c21f;b=ca0e3dc248124b2994e7e7dc2745bc3a;m=2547a6da;t=55197472276b3;x=c0b46a16e0caa791 kernel: 4.11.4-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: 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] File: backtrace
Created attachment 1286634 [details] File: cgroup
Created attachment 1286635 [details] File: core_backtrace
Created attachment 1286636 [details] File: cpuinfo
Created attachment 1286637 [details] File: dso_list
Created attachment 1286638 [details] File: environ
Created attachment 1286639 [details] File: exploitable
Created attachment 1286640 [details] File: limits
Created attachment 1286641 [details] File: maps
Created attachment 1286642 [details] File: open_fds
Created attachment 1286643 [details] File: proc_pid_status
Created attachment 1286644 [details] File: var_log_messages
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 string "lvfs" file descriptor file descriptor 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 <richard> 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. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1460429 :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. ***