Unresolved dependencies are present:
package python2-langtable-0.0.41-2.fc30.noarch requires langtable = 0.0.41-2.fc30,
but none of the providers can be installed
Works
Works good
SELinux is preventing haveged from write access on the file write_wakeup_threshold.
Unresolved dependencies regarding qt5-qtbase
update now exist:
package qt5ct-0.38-1.fc30.x86_64 requires qt5-qtbase(x86-64) = 5.11.3,
but none of the providers can be installed
*Nothing personal here. It's just often not easy for ordinary users to figure out what exactly requires correction and how.
Yes, it's really good that things about systemd scripting no longer at an impasse.
To clarify a bit about attribution of issues to a specific updates. I think, that it would be more productive to take care about informing other maintainers when their packages need upgrade too. Otherwise all the work done makes no sense.
- nothing provides python2-m2crypto needed by oz-0.17.0-1.fc30.noarch
package wpebackend-fdo-1.0.0-2.fc30.x86_64 requires libwpe-0.2.so.1()(64bit),
but none of the providers can be installed
Thanks for future investigation. I understand that preventing systemd-resolved more related to selinux issues, but somehow even so related 'cause appearing after this update :)
SELinux is preventing systemd-resolve from sendto access on the unix_dgram_socket
/run/systemd/journal/socket.
systemd
always enables previously manually disabled systemd-resolved and systemd-networkd services.- package pptp-1.10.0-6.fc30.x86_64 requires /sbin/ip, but none of the providers can be installed
sddm-0.18.0-6 still shows BLACK SCREEN only with a cursor. And after logging through GDM, in general, we get a pretty working environment... except for a pair of broken widgets
Upgrading to Qt5-5.12.1 downgrades sddm to 0.18.0-3
Still is not upgradable due to many unresolved issues. And after forced installation SDDM (currently 0.18.0-5) shows only ENTIRE black screen
dnf skipping upgrade due to lack of python3-qt5-webengine
package in this build.
Upgrading with --best --allowerasing leads to SDDM black screen
Correctly installed and now in use