Plasma 5.17.4 release, https://kde.org/announcements/plasma-5.17.4.php
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-2019-46ba155852Please login to add feedback.
This update has been submitted for testing by rdieter.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
rdieter edited this update.
This update has been pushed to testing.
Error: Problem: problem with installed package kcm_systemd-1.2.1-14.fc31.x86_64 - package plasma-systemsettings-5.17.3-1.fc31.x86_64 conflicts with kcm_systemd < 1.2.1-15 provided by kcm_systemd-1.2.1-14.fc31.x86_64 - cannot install the best update candidate for package plasma-systemsettings-5.16.5-1.fc31.x86_64
Don't work Alt+F2 and Task Manager widget.
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.
Same problem. Pressing Alt+F2 crashes plasma.
Also systemsettings5 crash https://paste.centos.org/view/2e2ab347
LGTM on fresh system.
After upgrading to kf 5.64.1 https://bodhi.fedoraproject.org/updates/FEDORA-2019-8468f362c4 1. Task manager widget work. 2. systemsettings5 work. 3. Alt+F2 NOT work until I manually assigned this shortcut with krunner.
Since 5.17.4 was release yesterday (https://kde.org/announcements/plasma-5.17.3-5.17.4-changelog.php), maybe it's better to test it instead of 5.17.3? I'm not saying it fairs better, given no fixes for mentioned issues, but it has other fixes that we'll probably encounter.
It's been working well so far, after installing with kcm_systemd for fc32:
cd $(mktemp -d) && koji download-build --arch=x86_64 kcm_systemd-1.2.1-15.fc32 && dnf upgrade * --enablerepo=*testing.I'll add karma later.
@vascom Alt+Space also stopped working, but Meta+Space is the new default, it's probably more convenient than Alt+F2.
@cowboysmall --allowerasing flag should work in your case, I just had the same. If not, also use --best flag as suggested.
Had to add
--best --allowerasingflags for the upgrade to fully install (ends up removing kcm_systemd) but things seem to be working so far.When trying to login to plasma from sddm userid and password not accepted. Am able to login fine to GNOME. By process of elimination found that kscreenlocker was causing the issue. Had to downgrade kscreenlocker to be able to login.
Can you verify if you have kde frameworks 5.64 too or not? https://bodhi.fedoraproject.org/updates/FEDORA-2019-8468f362c4
(hint: you do need this)
Yes, I believe that was installed 20 days ago and I left positive karma. The problem I mentioned above occurred with this update and I backed out. I did notice however that the following failed (as others mentioned above):
Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): plasma-systemsettings i686 5.17.3-1.fc31 updates-testing 359 k plasma-systemsettings x86_64 5.17.3-1.fc31 updates-testing 349 k Skipping packages with broken dependencies: plasma-desktop x86_64 5.17.3-1.fc31 updates-testing 5.3 M
I didn't force their upgrade by --best --allowerasing. I thought it best to wait until the issue was corrected.
rdieter edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by rdieter.
How does one disable Meta+Space now? I don't see it's assigned in hotkeys.
This update has been pushed to testing.
@agurenko, you need to edit config https://bugs.kde.org/show_bug.cgi?id=413542
Good now.
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
Fixes #1766806, so far so good.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works for me now.
5.17.3 worked fine after removing kcm_systemd to allow upgrade (later re-installed it (kcm_systemd) when new build was available). 5.17.4 upgraded no issues, everything seems to work fine.
5.17.3 worked well, after upgrade with --best --allowerasing. 5.17.4 running really well with no regression spotted so far
https://bugzilla.redhat.com/show_bug.cgi?id=1781054 this is grave ... I'm using it all the time, now I was forced to go to K-menu for app (= other than switch off button) after a year or so ...
WFM.
5.17.4 appears to be working well for me so far.
This update has been submitted for stable by rdieter.
This update has been pushed to stable.