Plasma 5.4 works good in my F22.
Just two notes:
1) I manually downloaded the package sddm-breeze because was not installed automatically. I discovered that when tried to modify the login screen settings.
2) plasma-pa was not automatically installed. I guess it was intentional (maybe some user of ALSA?), but I put it in the notes as well.
I'm using the sddm-breeze theme and after applying this update was unable to login due to a white screen. Apparently the sddm-breeze theme I had on my system was erased. I then found the sddm-breeze rpm and installed it. People aren't going to realize this and won't be able to login. You need to also install the sddm-breeze rpm if you're deleting the existing files.
This update rendered Plasma completely unusable on my system. The plasmashell component consistently segfaults during the login process. I've reported this upstream as https://bugs.kde.org/show_bug.cgi?id=352294.
(That aside, in terms of the update process, in my case, I had to separately manually pull in the latest khelpcenter and kscreen updates, as they weren't recognized and pulled over in the bulk update for some reason. And as @valeriodean and @gbcox note, it was also necessary to manually pull in sddm-breeze.)
As a follow-up to my previous feedback, the issue was that I didn't have the KDE Frameworks 5.13 updates installed first. (One might call this simple user error, but I don't follow why the Plasma packages wouldn't have the updated Frameworks as a noted dependency. dnf let me install a newer Plasma without warning or pulling in other dependencies from Frameworks that are necessary for the newer Plasma to actually function properly.) So it seems like there are multiple packaging issues here...
a dnf bug? i cannot even install the update as it spits out heap of conflicts , dnf should pull in the deps, my guess is to people, try the yum-deprecated package, dnf sucks
The bug I opened upstream with KDE (https://bugs.kde.org/show_bug.cgi?id=352294) is resolved, though I don't think the fix is necessary to pull in here. As long as a user has KDE Frameworks updated to 5.13 first, they won't encounter the issue.
This update has been submitted for testing by dvratil.
This update has been pushed to testing
dvratil edited this update. New build(s): kf5-baloo-5.13.0-1.fc22.
======================================================================================================================================================================== Balíček Arch Verze Repozitář Vel. ======================================================================================================================================================================== Skipping packages with broken dependencies: plasma-desktop x86_64 5.4.0-1.fc22 updates-testing 5.7 M plasma-workspace x86_64 5.4.0-5.fc22 updates-testing 8.6 M
dvratil edited this update. New build(s): kio-extras-15.08.0-1.fc22.
dvratil edited this update. New build(s): plasma-desktop-5.4.0-2.fc22, plasma-workspace-5.4.0-6.fc22. Removed build(s): plasma-desktop-5.4.0-1.fc22, plasma-workspace-5.4.0-5.fc22.
rdieter edited this update. New build(s): plasma-workspace-5.4.0-6.fc22.1. Removed build(s): plasma-workspace-5.4.0-6.fc22.
rdieter edited this update. New build(s): kwin-5.4.0-4.fc22. Removed build(s): kwin-5.4.0-1.fc22.
This update has been submitted for testing by rdieter.
This update has been pushed to testing
Plasma 5.4 works good in my F22. Just two notes: 1) I manually downloaded the package sddm-breeze because was not installed automatically. I discovered that when tried to modify the login screen settings. 2) plasma-pa was not automatically installed. I guess it was intentional (maybe some user of ALSA?), but I put it in the notes as well.
I'm using the sddm-breeze theme and after applying this update was unable to login due to a white screen. Apparently the sddm-breeze theme I had on my system was erased. I then found the sddm-breeze rpm and installed it. People aren't going to realize this and won't be able to login. You need to also install the sddm-breeze rpm if you're deleting the existing files.
This update rendered Plasma completely unusable on my system. The plasmashell component consistently segfaults during the login process. I've reported this upstream as https://bugs.kde.org/show_bug.cgi?id=352294.
(That aside, in terms of the update process, in my case, I had to separately manually pull in the latest khelpcenter and kscreen updates, as they weren't recognized and pulled over in the bulk update for some reason. And as @valeriodean and @gbcox note, it was also necessary to manually pull in sddm-breeze.)
Error: nothing provides libKF5Baloo.so.5()(64bit) needed by plasma-desktop-5.4.0-2.fc22.x86_64.
Same problem as gbcox - white screen which was fixed by manually installing sddm-breeze theme.
Multiple kde 15.04 updates needed to be pulled in manually.
As a follow-up to my previous feedback, the issue was that I didn't have the KDE Frameworks 5.13 updates installed first. (One might call this simple user error, but I don't follow why the Plasma packages wouldn't have the updated Frameworks as a noted dependency. dnf let me install a newer Plasma without warning or pulling in other dependencies from Frameworks that are necessary for the newer Plasma to actually function properly.) So it seems like there are multiple packaging issues here...
This update has been obsoleted.
a dnf bug? i cannot even install the update as it spits out heap of conflicts , dnf should pull in the deps, my guess is to people, try the yum-deprecated package, dnf sucks
kkofler edited this update.
This update has been submitted for testing by kkofler.
I disabled the autokarma nonsense and resent the update to testing.
I filed bug #1261034 for the dnf failure to pull in sddm-breeze on upgrades. For me, this works well.
This update has been pushed to testing.
Sorry, baloo stuff I saw was entirely user error. Installs fine for me, though I did not get sddm-breeze.
The bug I opened upstream with KDE (https://bugs.kde.org/show_bug.cgi?id=352294) is resolved, though I don't think the fix is necessary to pull in here. As long as a user has KDE Frameworks updated to 5.13 first, they won't encounter the issue.
fyi, the previous comment about kde bug 352294, should be resolved by mesa update, https://bodhi.fedoraproject.org/updates/FEDORA-2015-15543
This update has been unpushed.
This update (plasma-5.4.0) has been superceded by plasma-5.4.1, https://bodhi.fedoraproject.org/updates/FEDORA-2015-15687