Backport upstream crash fix (when dbus isn't immediately available on startup).
sudo dnf upgrade --refresh --advisory=FEDORA-2020-7699a31d2aPlease login to add feedback.
| 0 | 1 | Test Case desktop update graphical |
| 0 | 0 | Test Case desktop update graphical/it |
| 0 | 0 | Test Case desktop update notification |
| 0 | 0 | Test Case desktop update notification/it |
| 0 | 1 | Test Case package install remove |
This update has been submitted for testing by rdieter.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted PackageKit-1.2.2-1.fc33, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi.
Did not crash yet.
openQA tests on Rawhide suggest this may have broken update check on first login, so I don't think we should push it stable till that is investigated.
This update has been unpushed.
This update has been submitted for testing by adamwill.
Yup, breakage, offline updates are broken for me too.
Offline updates seem to work fine for me, but I don't seem to get notifications about available updates.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Revoking update, no immediate movement or ETA to fix outstanding issues
This update has been unpushed.
What should i do now? "dnf downgrade PackageKit*" ?
Yes. alternatively can wait until the next updates push/sync, and do : dnf distro-sync
@rdieter the "immediate movement" has been happening in https://github.com/hughsie/PackageKit/pull/437 . We did some more digging and it seems much less clear that issues with update notification have anything to do with this update, see the tests I ran tonight. Can you check that things reliably work for you with 1.2.2-1 and reliably don't work with 1.2.2-2? I can't say that's the case for me, it seems to be less obvious than that.
Since the openQA tests issue does not seem to be caused by this PackageKit update, would it be possible to push this update to stable?
This update has been submitted for testing by adamwill.
I was hoping to hear back from @rdieter , but if we don't soon, we can do that, yeah.
Can folks who seem to be affected by issues with update notification try downgrading fwupd to 1.4.6? See https://bugzilla.redhat.com/show_bug.cgi?id=1896540#c6 .
This update has been pushed to testing.
This update has been submitted for stable by adamwill.
I'll verify, but the reason why I didn't want this pushed as-is was because it breaks offline updates using plasma-discover.
Good thing I checked, looks like plasma-discover offline updates worked this time.
This update has been pushed to stable.