KDE Plasma 5.22.1 release. See https://kde.org/announcements/plasma/5/5.22.1/ for more information.
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-2021-dcc1ce9423Please login to add feedback.
This update has been submitted for testing by jgrulich.
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 plasma-workspace-5.21.5-4.fc34, 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.
I ran sudo dnf offline-upgrade download in a Fedora 34 KDE Plasma installation with updates-testing enabled. dnf errors happened with Plasma 5.22.1 due to its kf5 >= 5.83.0 requirement. F34 has KF 5.82.0. I reported these errors at https://bugzilla.redhat.com/show_bug.cgi?id=1972982
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.
Update broken. No Kwin and windows decoration, keyboard doesn't work. Some packages not updated:
Broken. No KF5 update.
This update has been obsoleted.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update has been submitted for testing by jgrulich.
The dnf errors in https://bugzilla.redhat.com/show_bug.cgi?id=1972982 were fixed by the addition of KF 5.83.0 after I downloaded this update with bodhi updates download --updateid=FEDORA-2021-dcc1ce9423 A dnf error libksysguard-5.22.1-1.fc34.x86_64 conflicts with ksysguard-backend < 5.21.90 provided by ksysguard-backend-5.21.5-1.fc34.x86_64 occurred when I tried to update https://bugzilla.redhat.com/show_bug.cgi?id=1973378 The changes in https://src.fedoraproject.org/rpms/ksysguard/c/b3df63abc1e2cc692e16344b13db4fcf5c000080?branch=f34 look like they put the obsoletes and provides lines in the %description section of ksysguard.spec. ksysguard-5.22.0-2.fc34 doesn't obsolete ksysguard-backend < 5.21.90-2 and provide ksysguard-backend = %{version}-%{release} as a result https://koji.fedoraproject.org/koji/rpminfo?rpmID=26567885 I could update working around that error by adding --best --allowerasing which removed ksysguard-backend. Plasma 5.21.1 seems to be running alright after that.
rdieter edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Still having broken dependencies here and conlficts, but I think the mirror here didnt synched by now... Will wait until tomorrow (part of the broken/conflict messagens at DNF): Ignorando pacotes com conflitos: (adicionar --best --allowerasing' a linha de comando para forçar sua atualização): kdesu x86_64 1:5.21.3-1.fc34 fedora 233 k kdesu x86_64 1:5.22.1-1.fc34 updates-testing 231 k kwin-libs x86_64 5.22.1-1.fc34 updates-testing 1.6 M libksysguard x86_64 5.22.1-1.fc34 updates-testing 1.1 M libkworkspace5 x86_64 5.21.3-1.fc34 fedora 114 k libkworkspace5 x86_64 5.21.5-3.fc34 updates 114 k libkworkspace5 x86_64 5.22.1-1.fc34 updates-testing 113 k plasma-workspace-common x86_64 5.21.3-1.fc34 fedora 30 k plasma-workspace-common x86_64 5.21.5-3.fc34 updates 30 k plasma-workspace-common x86_64 5.22.1-1.fc34 updates-testing 30 k plasma-workspace-libs x86_64 5.22.1-1.fc34 updates-testing 2.0 M Ignorando pacotes com dependências quebradas: kde-cli-tools x86_64 5.21.3-1.fc34 fedora 966 k kde-cli-tools x86_64 5.22.1-1.fc34 updates-testing 808 k ksystemstats x86_64 5.22.1-1.fc34 updates-testing 211 k kwin x86_64 5.22.1-1.fc34 updates-testing 12 k kwin-common x86_64 5.22.1-1.fc34 updates-testing 2.6 M kwin-wayland x86_64 5.22.1-1.fc34 updates-testing 474 k kwin-x11 x86_64 5.22.1-1.fc34 updates-testing 148 k plasma-desktop x86_64 5.22.1-1.fc34 updates-testing 12 M plasma-integration x86_64 5.22.1-1.fc34 updates-testing 180 k plasma-lookandfeel-fedora noarch 5.22.1-1.fc34 updates-testing 1.2 M plasma-systemsettings x86_64 5.22.1-1.fc34 updates-testing 391 k plasma-workspace i686 5.21.3-1.fc34 fedora 7.2 M plasma-workspace x86_64 5.21.3-1.fc34 fedora 7.1 M plasma-workspace i686 5.21.5-3.fc34 updates 7.2 M plasma-workspace x86_64 5.21.5-3.
This update has been pushed to testing.
It is the first version of plasma-wayland that I am able to use here. :-)
This update can be pushed to stable now if the maintainer wishes
rdieter edited this update.
Works for me!
Updated today and it worked all fine, no more errors.
rdieter edited this update.
Works fine, no regressions spotted so far
It's OK overall but some minor issues like some stats from applet disappeared.
WFM
I have problems with mounting USB drives. Automounting USB was disabled but drive always automounted after connection with this update. I enabled Automounting and disabled it. After that USB drive shown in connected devices once after login. New connected USB drives never shown in connected devices.
rdieter edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by rdieter.
rdieter edited this update.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
The openQA failures on this update seem to be because a single click does not launch the "Install to Hard Drive" anaconda launcher on the live environment desktop. It needs a double-click to launch. This is not the case for other F34 tests without this update, and it's also not the case for Rawhide tests, even though Rawhide should have the same or newer package versions. Not sure what's going on there, or if it's intentional.
double click behavior is intentional, I believe, https://pagure.io/fedora-kde/SIG/issue/17
sorry for any fallout.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
LGTM
This update has been submitted for stable by bodhi.
General usage works. My SSH keys are added to the agent on login again, which was the most annoying pain point for me.
LGTM
This update has been pushed to stable.