I had to select activitmanager inorder to submit the bug.
dnf -y upgrade on system this AM (158 updates)
Screensaver /lock kicked in and produces an error message.
rebooted system to attempt to login unable to login into Kdesktop.
switched to VT(F2) and loged in as root
dnf -y upgrade --refresh
>> reports 20 packages skipped due to broken dependencies
Attempted to revert the update
>dnf history undo 115
No package kdepimlibs-kxmlrpcclient-0:4.14.10-15.fc24.x86_64 available.
Error: An operation cannot be undone.
I can provide DNF log if needed.
Created attachment 1261006 [details]
broken dependency list
I believe I am also experiencing this issue on Fedora 24, and it seems to be broader than just kde-plasma-activitymanager. I've attached the output of dnf showing a list of broken dependencies.
I'm adding Rex to CC, in case we need to change the component of this bug to be more general to KDE.
kdepim-16.12.2-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-81bed9e1d4
kdepim4-4.14.10-27.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-daa782e4a0
Looks like todays updates did the trick, at least for me as of 15 min ago.
@Randy Barlow (see comment #1): this problem is definitely broader than the pkg to which James Crawford refers (kde-plasma-activitymanager) ... the latter is not installed here (some month ago I installed the KDE spin of Fedora 24).
After my 1st attempt to upgrade on March 6 (lots and lots of "kde" pkgs), my gui failed in part. One day later dnf reported more "kde" packages. After installing those, my gui problem had disappeared. However I ended up with the same list of "skipped pkgs because of broken dependencies" as you did.
Btw, the upgrade on March 6 was NOT the first one after installing Fedora 24; I regularly upgrade my system (every other day) ...
After studying the output of "dnf -b upgrade <pkg>" for each of the skipped pkgs, I decided to carry out the two following upgrades:
1. dnf -b --allowerasing upgrade gpgme
2. dnf -b --allowerasing upgrade knotes-libs
The 1st one upgraded 18 of the skipped packages (removing kdepim-common, kdepim-libs, knode and knode-libs ... and installing 10 others).
The 2nd one "upgraded" the last of the skipped pkgs (however in reality, it reinstalled knotes-libs and knotes - sigh).
After that "dnf check-update" was silent (no skipped pkgs).
To me, upgrading (using dnf) is turning into "magic" this way ...
There should really be nothing magic here, it's just that the previous kdepim-16.12.2 related update missed 2 packages (sorry). Those 2 packages are now submitted as updates themselves, see comment #3 and comment #4 (each of which are currently available in updates-testing). Once they land in stable updates, everything should 'just work', normal update mechanisms will pick them up, and dependency issues should be resolved.
(In reply to Henri from comment #7)
> After studying the output of "dnf -b upgrade <pkg>" for each of the skipped
> pkgs, I decided to carry out the two following upgrades:
> 1. dnf -b --allowerasing upgrade gpgme
> 2. dnf -b --allowerasing upgrade knotes-libs
> The 1st one upgraded 18 of the skipped packages (removing kdepim-common,
> kdepim-libs, knode and knode-libs ... and installing 10 others).
> The 2nd one "upgraded" the last of the skipped pkgs (however in reality, it
> reinstalled knotes-libs and knotes - sigh).
> After that "dnf check-update" was silent (no skipped pkgs).
> To me, upgrading (using dnf) is turning into "magic" this way ...
Correcting myself: knotes-libs was upgraded, knotes was installed.
@Rex Dieter: Thank you for clarifying what is going on. Obviously, the whole "string of events" is no magic to you, but it is to me -- as I wrote (I am just a regular user, not an expert -- and I could not make head or tail of what had gone wrong with my upgrade).
Hi Rex, and thank you for fixing this. I notice that the issue didn't seem to arise for F25. Does this mean that updates are (presumably automatically) tested against F25, but maybe not F24?
kdepim-16.12.2-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
kdepim4-4.14.10-27.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
I've just sudo dnf upgraded F24. There were no broken dependencies this time and everything works!