Bug 1830790 - Getting fwupd issues when restarting, saying failed to update software
Summary: Getting fwupd issues when restarting, saying failed to update software
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupdate
Version: 32
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-03 21:32 UTC by Timothy Rogers
Modified: 2021-05-25 17:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:55:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Timothy Rogers 2020-05-03 21:32:32 UTC
Description of problem:
fwupd complaining about missing ID, and causing gnome-software to complain that updates couldn't complete successfully

Version-Release number of selected component (if applicable):
Fedora 32

How reproducible:
Reboot after installing updates with WD drives listed


Steps to Reproduce:
1. Install updates via gnome-software or dnf
2. Restart system
3. Look at system notification about failed update

Actual results:
https://paste.centos.org/view/123da599

Expected results:
Successful update

Additional info:
-- Reboot --
Apr 28 22:02:11 localhost.localdomain systemd[1]: Starting Firmware update daemon...
Apr 28 22:02:11 localhost.localdomain fwupd[3237]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a)
Apr 28 22:02:12 localhost.localdomain fwupd[3237]: 02:02:12:0154 FuEngine             device 9afcd7db8643d511ee389321038ae4c56c7a45f3 [WDC WD10EZEX-08WN4A0] does not define a vendor-id!
Apr 28 22:02:12 localhost.localdomain fwupd[3237]: 02:02:12:0162 FuEngine             device 2502f36ad540c1b9dd2b97690615b10d8a27797f [WDC WDS500G2B0A-00SM50] does not define a vendor-id!
Apr 28 22:02:12 localhost.localdomain fwupd[3237]: 02:02:12:0170 FuEngine             device 185b59feeff9d1bfb0713198bf1a495f5db119ab [WDC WDS500G2B0B-00YS70] does not define a vendor-id!
Apr 28 22:02:12 localhost.localdomain systemd[1]: Started Firmware update daemon.
Apr 28 22:02:30 localhost.localdomain systemd[1]: Stopping Firmware update daemon...
Apr 28 22:02:30 localhost.localdomain systemd[1]: fwupd.service: Succeeded.
Apr 28 22:02:30 localhost.localdomain systemd[1]: Stopped Firmware update daemon.

Comment 1 Fedora Program Management 2021-04-29 17:10:09 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 17:55:58 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.