libdnf:
dnf-plugins-extras:
PackageKit:
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2020-02ee4b1a1cPlease login to add feedback.
This update has been submitted for testing by amatej.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
adamwill edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by adamwill.
This update has obsoleted dnf-plugins-extras-4.0.8-3.fc30, and has inherited its bugs and notes.
adamwill edited this update.
This update has been pushed to testing.
openQA upgrade tests are succeeding with this, so gonna +1 it.
uprgaded baremetal T580 and worked fine
This update can be pushed to stable now if the maintainer wishes
adamwill edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by adamwill.
sgallagh edited this update.
sgallagh edited this update.
New build(s):
Removed build(s):
Karma has been reset.
Seems to fix all issues, modules are reset on upgrade, but not during a regular reboot.
This update has been pushed to testing.
I trust adamw
This update can be pushed to stable now if the maintainer wishes
but I didn't write or submit or even test the latest fix yet :P do you trust sgallagh and kparal? that's the question...
I tested this update, the modular installs survive reboots on Fedora 30 and the system can be upgraded to F32 without any issues.
This update has been submitted for stable by bodhi.
Okay, I trust sgallagh and kparal.
This update has been pushed to stable.
systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: failed (Result: core-dump) since Fri 2020-04-24 07:57:16 CEST; 4h 1min ago Process: 1619 ExecStart=/usr/libexec/packagekitd (code=dumped, signal=SEGV) Main PID: 1619 (code=dumped, signal=SEGV)
Apr 24 07:54:39 fedora PackageKit[1619]: resolve transaction /3024_aceeacec from uid 1000 finished with success after 14ms Apr 24 07:54:40 fedora PackageKit[1619]: resolve transaction /3025_ccdedbde from uid 1000 finished with success after 347ms Apr 24 07:54:40 fedora PackageKit[1619]: resolve transaction /3026_bdeddabb from uid 1000 finished with success after 5ms Apr 24 07:54:46 fedora PackageKit[1619]: get-updates transaction /3027_eebdeedc from uid 1000 finished with success after 5023ms Apr 24 07:55:45 fedora PackageKit[1619]: upgrade-system transaction /3028_dececcae from uid 1000 finished with success after 58056ms Apr 24 07:55:48 fedora PackageKit[1619]: resolve transaction /3029_bbaeeacb from uid 1000 finished with cancelled after 2088ms Apr 24 07:57:16 fedora packagekitd[1619]: instance of invalid non-instantiatable type '(null)' Apr 24 07:57:16 fedora packagekitd[1619]: g_signal_emit_valist: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Apr 24 07:57:16 fedora systemd[1]: packagekit.service: Main process exited, code=dumped, status=11/SEGV Apr 24 07:57:16 fedora systemd[1]: packagekit.service: Failed with result 'core-dump'.
@boycottsystemd1 This update has been stable for over a month. Submitting errors logs like this isn't helpful at all. Please file a new bug in bugzilla and link it here, only if you believe it has been caused by this very update (i.e. the problem didn't exist before). Otherwise just submit a bug. Use ABRT to submit a proper crash report. Thanks.