FEDORA-2019-350a369113 created by rhughes 2 months ago for Fedora 31
stable

New upstream release - Actually write the new device path if different than before - Add a SynapticsMSTBoardID for a few Lenovo docks - Add support for tpm2-tools 4.X - Add the counterpart GUID for the DW5821e - Allow specifying a firmware GUID to check any version exists - Be more accepting when trying to recover a failed database migration - Do not ask the user to upload a report if ReportURI is not set - Do not segfault when trying to quit the downgrade selection - Fix a crash when stopping the fwupd service - Never show AppStream markup on the console - Relax the certificate time checks in the self tests for the legacy cert - Remove replug flag after the device comes back from reboot - Update device_modified in sql database during updates - Work properly with ICL thunderbolt controller

How to install

sudo dnf upgrade --advisory=FEDORA-2019-350a369113
This update has been submitted for testing by rhughes. 2 months ago
This update's test gating status has been changed to 'waiting'. 2 months ago
This update's test gating status has been changed to 'ignored'. 2 months ago
This update has been pushed to testing. 2 months ago
User Icon pwalter commented & provided feedback 2 months ago
karma

Works

User Icon agarwalvarshit commented & provided feedback 2 months ago
karma

Expected Result

This update can be pushed to stable now if the maintainer wishes 2 months ago
User Icon nathan95 commented & provided feedback 2 months ago
karma

Ok works for me

This update has been submitted for stable by bodhi. 2 months ago
This update has been pushed to stable. 2 months ago
User Icon adamwill commented & provided feedback a month ago
karma

I think this broke on new installs, in fact. GNOME Software update tests in openQA are failing consistently with an fwupd-related error since this landed in stable:

https://openqa.fedoraproject.org/tests/461074#step/desktop_update_graphical/30

the system logs show fwupd.service failing to start:

Oct 01 04:39:34 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1991]: fwupd.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/cache/fwupd: No such file or directory
Oct 01 04:39:34 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1991]: fwupd.service: Failed at step NAMESPACE spawning /usr/libexec/fwupd/fwupd: No such file or directory
Oct 01 04:39:34 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1]: fwupd.service: Main process exited, code=exited, status=226/NAMESPACE
Oct 01 04:39:34 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com systemd[1]: fwupd.service: Failed with result 'exit-code'.

We had an identical issue in iwd recently. The problem here is probably that the fwupd service file refers to /var/cache/fwupd but the package does not create it. This will cause problems until it is created manually.

User Icon chrismurphy commented & provided feedback a month ago
karma

I'm running into the same problem Adam is, on clean installs: https://bugzilla.redhat.com/show_bug.cgi?id=1731758#c4


Please login to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
2 months ago
in testing
2 months ago
in stable
2 months ago

Automated Test Results