Created attachment 1949246 [details] journal Description of problem: Click "Restart&Update" button to update the firmwares,but found the firmwares is not updated when login to the rebooted system.As shown in the attached screencast,I also try with clicking the "Update" button and clicking "restart" button of the pop up dialog,doesn't work either. Version-Release number of selected component (if applicable): gnome-software-44~rc-1.fc38.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1949247 [details] screencast
Proposed as a Blocker for 38-final by Fedora user lnie using the blocker tracking app because: violates this: For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test
Thanks for a bug report. I do not see anything usable in the journal, not talking it contains a lot of unrelated things (from different days and different software versions). A much better and more targeted log is: gnome-software --quit; gnome-software --verbose &>log.txt The fwupd shows in your journal few things: > Mar 09 02:42:34 localhost fwupd[2938]: 07:42:34.349 FuBiosSettings KERNEL BUG: 'type' attribute not exported: (failed to load type: Failed to open file "/sys/class/firmware-attributes/thinklmi/attributes/SecureBoot/type": No such file or directory) > Mar 09 02:42:34 localhost fwupd[2938]: 07:42:34.436 FuEngine no GUIDs for device TPM [dfb1a4db3787a1799167fb68010ef732c71041f9] > .... > Mar 09 02:42:35 localhost fwupd[2938]: 07:42:35.846 FuPluginIntelMe failed to get public key using /fpf/OemCred: generic failure [0xb] > .... > Mar 09 02:42:37 localhost fwupd[2938]: 07:42:37.121 FuEngine failed to add device /sys/devices/pnp0/00:08/tpm/tpm0: failed to initialize TPM > Mar 09 02:42:37 localhost systemd[1]: Started fwupd.service - Firmware update daemon. I've no idea whether these are related or not. Once you've the verbose log this may or may not be moved to the fwupd, it depends what the verbose log will sow.
> I've no idea whether these are related or not. These are all fine. Does the firmware get updated by "fwupdmgr update" -- if not we should move this to the fwupd component as I don't think it's gnome-software specific. It's also not a F38 blocker, we've seen this before and 9/10 it's a firmware or config issue.
I reinstalled the system for other bug report before saw your comments,and I tried to reproduce this bug after update gnome-software,but this time it works ,the Firmwares are updated,so closing,thanks for your attention.
Ah,actually,if you produce the crash mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=2172059 before update gnome-software,you will see this bug.
Created attachment 1949394 [details] fwupdmgr update output