New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SuperIO Offline Updates get "stuck" #2830
Labels
Comments
@superm1 makes sense to me; spot any logic problems? I guess we also need to check the boot time to avoid clearing it on idle quit. |
When does superio update get installed? It's only in a clean rebooted session right? Yes, I think checking for a changed boot is a good enough criteria to mark any pending updates like that. |
hughsie
added a commit
that referenced
this issue
Jan 30, 2021
If any update is scheduled for SuperIO, and something changes (such as entering S3, disconnecting the charger) before the update is installed, then the update will get stuck. Fixes #2830
4 tasks
Does #2835 work? |
I have not been able to fault it :) |
hughsie
added a commit
that referenced
this issue
Feb 3, 2021
If any update is scheduled for SuperIO, and something changes (such as entering S3, disconnecting the charger) before the update is installed, then the update will get stuck. Fixes #2830
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If any update is scheduled for SuperIO, and something changes (such as entering S3, disconnecting the charger) before the update is installed, then the update will get "stuck".
The update then no longer appears in GNOME Software, and trying
fwupdmgr update
will show:It requires running
sudo fwupdmgr clear-offline
followed by afwupdmgr update
to get it to install.I say this only knowing about the 3 plugins we use but would it not make sense to clear the pending updates each time the fwupd.service starts?
The text was updated successfully, but these errors were encountered: