Created attachment 1849459 [details] fwupd core dump Description of problem: fwupd repeatedly dumps core Version-Release number of selected component (if applicable): 1.7.3 How reproducible: Always Steps to Reproduce: 1. happens at startup and whenever I click refresh in Gnome Software Additional info:
After the core dump there are also selinux messages abrt-notification[3186]: [🡕] Process 18302 (fwupd) crashed in fu_plugin_tpm_coldplug() setroubleshoot[2707]: SELinux is preventing gdb from read access on the file /var/cache/fwupd/metadata.xmlb. For complete SELinux messages run: sealert -l 1bea873b-bfd2-4815-a4fe-897bd94e3e99 setroubleshoot[2707]: AnalyzeThread.run(): Set alarm timeout to 10 setroubleshoot[2707]: SELinux is preventing gdb from read access on the file /var/cache/fwupd/metadata.xmlb. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the metadata.xmlb file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'gdb' --raw | audit2allow -M my-gdb # semodule -X 300 -i my-gdb.pp setroubleshoot[2707]: AnalyzeThread.run(): Cancel pending alarm setroubleshoot[2707]: failed to retrieve rpm info for /var/cache/fwupd/quirks.xmlb setroubleshoot[2707]: SELinux is preventing gdb from read access on the file /var/cache/fwupd/quirks.xmlb. For complete SELinux messages run: sealert -l 1bea873b-bfd2-4815-a4fe-897bd94e3e99 setroubleshoot[2707]: SELinux is preventing gdb from read access on the file /var/cache/fwupd/quirks.xmlb. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the quirks.xmlb file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'gdb' --raw | audit2allow -M my-gdb # semodule -X 300 -i my-gdb.pp
It looks like it's failing to get a response from the TPM. What hardware is this? Is the TPM enabled in the BIOS? Does /sys/kernel/security/tpm0/binary_bios_measurements exist for you? If so, can you attach it to this bug please?
Created attachment 1850076 [details] binary_bios_measurements
It's a Librem 15v3 laptop. The TPM is enabled. The file exists, attaching it
Ooops. [hughsie@fedora build (main %)]$ ./plugins/tpm/fwupdtpmevlog /home/hughsie/Downloads/bbm -v ** (fwupdtpmevlog:142976): DEBUG: 14:19:23.368: Event Data: 01 00 00 00 14 00 00 00 ee 23 1f 8f 2a 42 57 d3 f4 40 43 b8 43 6d ad 7c b5 5b 49 75 ** (fwupdtpmevlog:142976): DEBUG: 14:19:23.368: Event Data: 53 74 61 72 74 20 4f 70 74 69 6f 6e 20 52 4f 4d 20 53 63 61 6e ** (fwupdtpmevlog:142976): DEBUG: 14:19:23.368: Event Data: 07 00 00 00 18 00 00 00 00 00 00 00 15 a6 15 e4 12 fa 28 ca 94 52 30 c1 9d 72 05 bc 4a f2 bb 61 ** (fwupdtpmevlog:142976): DEBUG: 14:19:23.368: Event Data: 43 61 6c 6c 69 6e 67 20 49 4e 54 20 31 39 68 (fwupdtpmevlog:142976): FuCommon-CRITICAL **: 14:19:23.368: fu_memcpy_safe: assertion 'dst != NULL' failed Segmentation fault (core dumped)
Fixed in https://github.com/fwupd/fwupd/pull/4164